Summary: | [845] Crash when starting compiz | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Oxmosys <oxmosys> | ||||||||||||||||||||
Component: | Driver/intel | Assignee: | Default DRI bug account <dri-devel> | ||||||||||||||||||||
Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||||||||||
Severity: | critical | ||||||||||||||||||||||
Priority: | medium | CC: | ahph1uxsb8rae, brian, caominhtuvn, jlaukkanen, tgrundlesr | ||||||||||||||||||||
Version: | 7.3 (2007.09) | ||||||||||||||||||||||
Hardware: | Other | ||||||||||||||||||||||
OS: | All | ||||||||||||||||||||||
Whiteboard: | |||||||||||||||||||||||
i915 platform: | i915 features: | ||||||||||||||||||||||
Attachments: |
|
Description
Oxmosys
2008-12-13 01:37:45 UTC
Created attachment 21119 [details]
lspci log
Created attachment 21120 [details]
What changed in a9449fff4be8e6b3cc82914376420e3a66b960f5 commit
this bug even miss xorg.log.. pls refer to http://intellinuxgraphics.org/how_to_report_bug.html. thanks. Also, please check if the work-around in bug# 17713 or bug# 18270 works for you...thanks. Created attachment 21165 [details]
Xorg.0.log with ModeDebug
Created attachment 21166 [details]
uname -a
Created attachment 21167 [details]
xrandr --verbose
Created attachment 21168 [details]
dmesg log
Created attachment 21169 [details]
xorg.conf
Workaround in bug# 17713 "Option "NoAccel"" make it impossible to start compiz. Chipset : 82845G System architecture : i386 Packages : libdrm2 2.3.1-0build1 xserver-xorg 1:7.4~5ubuntu3 xserver-xorg-video-intel 2:2.4.1-1ubuntu10 libgl1-mesa-dri 7.2-1ubuntu2 Linux distribution : Linux Ubuntu 8.10 Machine model : Dell Optiplex GX160 Display Connector : VGA Thanks! Would it be useful to have a gdm backtrace? If yes, I can try it. Created attachment 21187 [details]
Xorg.0.log with ModeDebug when crashing during a VT Switch
I reproduced another crash in other circumstances with this graphic card. I'm writing the informations in case there is some link : when switching between multiple X sessions or when I logout from one of the active X session, X sometime fall into a black screen and it isn't possible to restart it. Text consoles still works but X is completely down. Compiz is not involved in this bug and it gives a lot of interesting outputs in Xorg.0.log.
Could you try Option "EXANoComposite" "true"? Is it working with xf86-video-intel 2.3.2? How about 2.4.3? I tried EXANoComposite workaround with 2.4.1 and the bug is still reproducible. The first time that I tried it, I got a different behavior : The screen showed "No signal detected" three times. The driver does not survive to a console switch in 2.5.1 so I can't provide more information about 2.5.1 at the moment. Let me know if you need more information. Created attachment 21380 [details]
Xorg.0.log from 2.5.1
More details about 2.5.1 driver issues :
I attached a Xorg.0.log from ubuntu 9.04 alpha 2 which includes 2.5.1 intel driver. Now the driver have many issues even without compiz. When X starts, some elements are missing or disappears from the screen (like icons in the menu), some texts are grey while they should be black, black artifacts in text and other weird effects. If I only click on GNOME menu, it generally take around 5 seconds before X freeze definitively. Maybe that metacity now use some kind of rendering by default?
Adjusting severity: crashes & hangs should be marked critical. Does this still occur with master of the 2D driver and 2.6.29 or 2.6.30 of the kernel, using UXA? It should avoid some problems that could have crashed non-UXA compiz. Eric, fwiw, according to a reporter on the downstream bug (https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/285250), this issue still occurs with Karmic Alpha-2, which is the 2.6.30-5 kernel and a git snapshot of the -intel driver up to ec2fde7c (plus some cherrypicks). https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/285250 Possible fix for hangs with compiz: commit a1e6abb5ca89d699144d10fdc4309b3b78f2f7a9 Author: Eric Anholt <eric@anholt.net> Date: Wed Jul 15 14:15:10 2009 -0700 Use batch_start_atomic to fix batchbuffer wrapping problems with 8xx render. Bug #22483. Could you try xf86-video-intel git master branch, which includes Eric's fix? (or wait for a couple of days for 2.8.0 release) I'm going to try this with next ubuntu karmic alpha release (july 23th). (In reply to comment #18) > Possible fix for hangs with compiz: > > commit a1e6abb5ca89d699144d10fdc4309b3b78f2f7a9 > Author: Eric Anholt <eric@anholt.net> > Date: Wed Jul 15 14:15:10 2009 -0700 > > Use batch_start_atomic to fix batchbuffer wrapping problems with 8xx > render. > > Bug #22483. > Atleast for me (845G, Gentoo, Xorg 1.6.2, and xf86-video-intel driver 2.7.99.902 (with batch_start_atomic fix) still freezes X when DRI is enabled. Well I hope this gets resolved by the end of year. :) I also confirm that the bug is not fixed, karmic alpha 3 has xserver-xorg-video-intel 2.8.0 and starting compiz still cause Xorg to freeze. I can move the mouse but nothing happens on the screen, and it's not possible to switch to TTY1-6. Xorg is just freeze. (clearing NEEDINFO) I guess Alpha-5 is still affected. Some months ago I tested Alpha-2 on another (now fixed) bug and my chipset (i830M) was blacklisted by ubuntu and disabled compiz. Yesterday I reinstalled Alpha-5 for further testing and have the same error. GDM boots up, login works but the UI crashes after some time. Keyboard and mouse are frozen, reboot by SysRq is possible, switching to another console is not. Hardware is here: https://bugs.freedesktop.org/show_bug.cgi?id=22287#c1 Still there on Alpha-6. I forwarded another bug report to Launchpad. https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/427337 I am not very experienced in debugging a desktop. Is there a way to enable debugging on GDM and GNOME to see what they do while initializing? Best case would be writing to logfiles. This is very much likely a dup of the CPU/GPU coherency issue clearly demonstrated by bug 26345. This issue is affecting a hardware component which is not being actively worked on anymore. Moving the assignee to the dri-devel list as contact, to give this issue a better coverage. *** This bug has been marked as a duplicate of bug 26345 *** |
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.