Summary: | [945GM] lock up and corruption on macbook | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Paul Brossier <piem> | ||||||||||||
Component: | Driver/intel | Assignee: | Wang Zhenyu <zhenyu.z.wang> | ||||||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||
Severity: | critical | ||||||||||||||
Priority: | medium | CC: | mateusz.pastewski, michael.fu, piem | ||||||||||||
Version: | 7.4 (2008.09) | ||||||||||||||
Hardware: | x86 (IA32) | ||||||||||||||
OS: | Linux (All) | ||||||||||||||
Whiteboard: | |||||||||||||||
i915 platform: | i915 features: | ||||||||||||||
Attachments: |
|
Description
Paul Brossier
2009-09-03 06:34:47 UTC
Will you please add the modedebug option in xorg.conf and attach the Xorg.0.log? > option "modedebug" "true" Will you please confirm whether the box can be accessed by using ssh after it hangs? If it can be accessed, please attach the output of dmesg, /proc/cpuinfo, /proc/meminfo, intel_gpu_dump, intel_register_dump? I have a macbook in my hand. But unfortunately I can't reproduce this issue. thanks. I attache here the dumps requested by yakui zhao, including the Xorg.0.log with modedebug true. i confirm the box can be accessed via ssh after x hangs. i used intel_reg_dumper, from the xserver-xorg-video-intel-dbg package, as i couldn't find intel_register_dump. HTH, cheers, piem Created attachment 29207 [details]
gpu and reg dump, dmesg, cpuinfo, meminfo, Xorg.0.log
(In reply to comment #3) > Created an attachment (id=29207) [details] > gpu and reg dump, dmesg, cpuinfo, meminfo, Xorg.0.log After the issue happens, will you please kill the X and restart it again to see whether it can work? From the attached log I have no idea about this bug. thanks. > (In reply to comment #4) > (In reply to comment #3) > > Created an attachment (id=29207) [details] [details] > > gpu and reg dump, dmesg, cpuinfo, meminfo, Xorg.0.log > After the issue happens, will you please kill the X and restart it again to see > whether it can work? > > From the attached log I have no idea about this bug. > thanks. > > > I have the same problems with this card. I tried with all configures of /etc/X11/xorg.conf, but there's the same bug! I don't attach anything because it will be very similar to attachments from first post. (In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > Created an attachment (id=29207) [details] [details] [details] > > > gpu and reg dump, dmesg, cpuinfo, meminfo, Xorg.0.log > > After the issue happens, will you please kill the X and restart it again to see > > whether it can work? > > > > From the attached log I have no idea about this bug. > > thanks. > > > > > > > I have the same problems with this card. I tried with all configures of > /etc/X11/xorg.conf, but there's the same bug! > > I don't attach anything because it will be very similar to attachments from > first post. > I made same test - I install xserver in versions given in file x-version. In connection with /etc/X11/xorg.conf (given too), everything works great. When I upgrade xserver to versions given in file x-version-new and it doesn't work (with the same config file). Regards, daimyo Created attachment 29623 [details]
xorg.conf
Created attachment 29624 [details]
working xserver
Created attachment 29625 [details]
doestn't work
Until yesterday, I had the same problem under linux kernel 2.6.30-1 and xserver-xorg-video-intel 2.8.1-2 as distributed by debian testing. However, the problem has gone away after I upgraded linux kernel to latest stable version 2.6.31 by compiling vanilla kernel source. As an end user, I have no idea about what was the source of the problem. Anyway by now, My X window system works flawlessly with quite good performance. Regards, Dohyun Kim yeah, new kernel has more stable fixes from Eric and Chris. So good to know that fixed your problem. |
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.