Summary: | [gem-classic] running ut2004/celestia/torcs for a few mins hangs X with waiting for fence error | ||
---|---|---|---|
Product: | Mesa | Reporter: | lin, jiewen <jiewen.lin> |
Component: | Drivers/DRI/i965 | Assignee: | haihao <haihao.xiang> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | ||
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 17596 | ||
Attachments: |
xorg conf file
xorg.0,log |
Description
lin, jiewen
2008-10-21 02:26:05 UTC
Created attachment 19779 [details]
xorg conf file
Created attachment 19780 [details]
xorg.0,log
This bug also happened when ran celestia with starting the desktop.The failure message is"intel_bufmgr_fake.c:392: Error waiting for fence: Device or resource busy.Aborting" . But it work well with nude X.(steps: xinit& ; celestia) This happens on all of machines we tested: G45, GM45, GM965, Q965, 945GM. It seems running with nude X may delay the triggered time. This works fine with mesa_7_2_branch. Seems it works fine if setting EXANoComposite to true in xorg.conf. (In reply to comment #6) > Seems it works fine if setting EXANoComposite to true in xorg.conf. > Yes, Haien have tried this, it worked well. But , with gem, setting EXANoComposite to true in xorg.conf just make the game run further ,it hangs X at last.(about 40 minutes) (In reply to comment #8) > But , with gem, setting EXANoComposite to true in xorg.conf just make the game > run further ,it hangs X at last.(about 40 minutes) Jiewen, please file a separate bug for GEM, since the logs and components are different. With gem, the are a new bug https://bugs.freedesktop.org/show_bug.cgi?id=18145 which is "games hang X" issue. With gem, the are a new bug https://bugs.freedesktop.org/show_bug.cgi?id=18380 which is "games hang X" issue. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.