[i915GM] Random laptop lockup after upgrade to 9.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Ubuntu Release 9.04 - Jaunty Jackalope
Laptop - Acer TravelMate 4102WLMi, Intel Centrino 1.73GHz, 768MB DDR-333 RAM, i915 onboard Intel video card, Intel 2200BG wireless card
I upgraded my 8.10 install to 9.04 using 'update-manager' last week and since then have been experiencing lockups in Ubuntu every day or so. The entire system freezes, no response on the keyboard, only the mouse pointer is active - set to whatever it was right at the freeze (for eg. if a new application was loading then the mouse pointer remains as a "busy" pointer). The screen stays the same and I can't seem to get it to do anything; the only option is to power-down manually by keeping the power button pressed.
I checked the logs but cannot seem to find any error messages in there, I tried turning on my bluetooth module using the kill switch on the laptop and sure enough there was an entry in /var/log/messages indicating that the system was still very much active and writing log messages in the background.
Could it be a problem with the i915 module?
-- Output of $(lspci -nn| grep VGA) --
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03)
summary: |
- Random laptop lockup after upgrade to 9.04 + [915GM] Random laptop lockup after upgrade to 9.04 |
summary: |
- [915GM] Random laptop lockup after upgrade to 9.04 + [i915GM] Random laptop lockup after upgrade to 9.04 |
tags: | added: freeze |
tags: | added: jaunty |
@mutew, can you paste the output of "lspci -nn | grep VGA" and also a copy of your /var/log/Xorg.0.log please. PS. If it turns out that you have a 965 chipset, then just sit tight because it's a known bug that is being worked hard on.
Now, in case you're on a non-965 chipset... If you have access to two computers can you please install ssh on the buggy machine and then the next time the freeze happens you'll do these things (please note that step 3 requires you to install a new kernel right away even before the freeze happens because only the new 2.6.30 kernels have this new kind of freeze debugging capability):
1) Try to run "apport-collect 368642" /edge.launchpad .net/~ubuntu- x-swat/ +archive/ x-freeze- test
2) If for some arcane reason you're unable to run this command, please sabes copies of xorg.log and xorg.log.old (please do this even if you have previously attached another copy of xorg.log because right after the time freeze has happened there might be special information available in xorg.log or in xorg.log.old that helps us understand the freeze).
3) This is a big one, but please collect a batch buffer dump. This dump is very useful for determining _why_ your machine is freezing. This is the one thing that gives upstream developer a decent chance to fix your bug. Detailed instructions on how to do this is available here: https:/