lspci reports my video card as
00:02.0 VGA compatible controller: Intel Corporation Cantiga Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Cantiga Integrated Graphics Controller (rev 07)
When X11 starts the screen turns black and the computer becomes unresponsive (I need to hold down the power button and force the power to shut off). This is with the 2.4.2 driver I downloaded and built from intellinuxgraphics.org (although to be honest I'm not 100% confident that Xorg was using the one in /usr/local rather than the one shipping with the Ubuntu alpha). I also noticed the problem with a patched 2.4.1 intel driver shipping with the current Ubuntu alpha (which they claim is the same as 2.4.2 but w/o the new version string) *and* I noticed the problem with Fedora Rawhide which I think is also on the latest version of the driver. So I think it's safe to say that there is definitely a bug in the upstream code, i.e. not just in the one Ubuntu is shipping.
I tried to build the driver in git but didn't have a new enough libdrm, but I can spend more time and try that out too if someone thinks it will help.
I wasn't really able to get any diagnostics because the Xorg log in /var/log is always empty after I hard reset.
Please help me -- I'm stuck on the vesa driver for the time being!
Xorg log will be definitely helpful, and I don't understand why yours is empty...
When it "freeze", does keyboard or network alive?
Created attachment 18811 [details]
Xorg.0.log from crash
Log from after a freeze.
(In reply to comment #1)
> When it "freeze", does keyboard or network alive?
When it freezes the network becomes unresponsive (can't ping the laptop). Also, I can't force the kernel to restart using the Magic SysRq sequences (e.g. Alt-SysRq-b doesn't restart the system).
Created attachment 18812 [details]
Xorg log from hard lock
I can "me too" this (with same software versions but on Debian Experimental) and also add that at least one other person is having the same problem (on Ubuntu Intrepid):
I have attached the log from one of the "hard lock" events. It appears to hard lock the machine when probing EDID but I have no way of proving that because, as the reporter mention, the system is completely dead--not even a kernel panic.
I can add some details, also. I have tried 2.6.25, 2.6.26 and 2.6.27-rc5 and -rc6. I have tried disabling the acpi-video module to work around the potential for a ACPI bug in this laptop. I've tried disabling a number of power saving features suggested by lesswatts.org in case one of them is responsible.
It "hard locks" in this way 80% of the time. If I reboot the machine between 3-10 times, it will eventually let me in to Xorg.
I don't know if this is related but there are many other issues with GM45. If I manage to get in to X, DPMS Off events kill the graphics (but the machines is still up), xrandr reports SVDO and LVDS are both active (with the wrong resolutions). I have nothing plugged in to the DVI port so this is additionally wrong (and possibly the source of any EDID probing issue?).
This is extremely frustrating. I bought this laptop after I heard Keith Package at IDF say how proud the Intel team was for getting the GM45 driver out a month before the hardware was available. At the moment, I have a laptop that takes 5-20 minutes to bring online.
Jason D. Clinton
Gnome Games Module Maintainer
I could add my ditto to Jason's comment. I am "eeejay" on the lenovo forum thread. This is happening on a Lenovo T400 with switchable graphics (disabled in BIOS). I am getting the same DPMS bug too, if it is related.
We're also seeing X start lockup issue on one of GM45 board here. It looks relate to C4 or render standby setting in bios. Chance is to see if your bios has those setting, and trys to disable it as a workaround until we find what really goes wrong. Although my debian sid (2.6.26) with current X master bits work fine on it.
Please attach X log with ModeDebug on.
Through some subtle property of Murphey's Law, 20 attempts to get a crash with ModeDebug on have resulted in booting perfectly each time; I haven't changed anything except for that one xorg variable... it just suddenly won't crash with it on. I'll try it again tomorrow morning connected to my dock; perhaps that will coax it to do my bidding. Race condition, perhaps?
And sorry about the name, Keith Packard. Not sure how I typo'd that.
(In reply to comment #7)
> Through some subtle property of Murphey's Law, 20 attempts to get a crash with
> ModeDebug on have resulted in booting perfectly each time; I haven't changed
> anything except for that one xorg variable...
Also works for me with ModeDebug... sounds an awful lot like a nasty race condition if you ask me.
Created attachment 18814 [details]
crash with ModeDebug turned on
(In reply to comment #8)
> Also works for me with ModeDebug... sounds an awful lot like a nasty race
> condition if you ask me.
I take this back -- what actually happens for me with ModeDebug is the X server crashes (but doesn't lock the kernel) and Ubuntu automatically switches to the vesa driver (which is why I thought it was working). I just attached the Xorg log from a crash with ModeDebug turned on.
Could you help me to verify if bios has 'C4 state' or 'Render Standby' options available and setting?
Evan, what's your laptop model?
(In reply to comment #11)
> Could you help me to verify if bios has 'C4 state' or 'Render Standby' options
> available and setting?
> Evan, what's your laptop model?
This is on a Thinkpad T500.
I've pushed a patch which might fix this to master and 2.4 branch, please try it.
Created attachment 18823 [details]
Xorg log after patch
I applied the patch.
The X server starts, this doesn't really mean anything in itself since I was able to briefly use X also last time when i just recompiled the driver.
The oddest thing is that glxinfo segfaults. I'll attach the output of glxinfo (just before it crashes) in the next comment. I'll need to rebuild mesa-utils since the stack trace I have now has no debugging signals.
Anyway, the Xorg log attached here might give a clue..
Created attachment 18824 [details]
Created attachment 18830 [details]
crash with ModeDebug and more output
It took about 20 crashes but I got a crash log with some actually useful information. This log that is attached happened to have an ext3 commit at the moment right before the xserver locked the machine--so the log is very late in the initialization process.
I haven't tried the patch to the 2.4 branch yet.
Specifically which commit SHA1 is the one you're talking about?
BTW, my laptop is a T400 and it does _not_ have the C4 or Standby options.
commit 86f82c429f5d7067c52d3b783988917869e13d1d on 2.4 branch.
Jason, please try it, I've seen from log render standby on Evan's T500 is on and disabled by driver.
I have tried the new driver: so far, so good. No crashes. But I'll have to report after using it a little more extensively since it's not 100% guaranteed to crash every time.
As for Eitan's OpenGL problems: I believe that issue may be related the 2.4 trunk now requiring libdrm 2.4. I'm using Intel driver 2.4 trunk with libdrm 2.3.1 + some git cherry picks (as found in Debian experimental) and everything OpenGL-wise is working perfectly. Perhaps Eitan is using libdrm 2.3.1 w/o the git cherry picks.
(In reply to comment #19)
> As for Eitan's OpenGL problems: I believe that issue may be related the 2.4
> trunk now requiring libdrm 2.4. I'm using Intel driver 2.4 trunk with libdrm
> 2.3.1 + some git cherry picks (as found in Debian experimental) and everything
> OpenGL-wise is working perfectly. Perhaps Eitan is using libdrm 2.3.1 w/o the
> git cherry picks.
I didn't use 2.4 trunk, I just created a patch for "HEAD~1" and added it to the debian package collection. But that might not be a bad idea, maybe I should just use 2.4 trunk...
Ok, I used 2.4 trunk, and libdrm from debian experimental, I still get a segfault with glxinfo.
(In reply to comment #18)
> commit 86f82c429f5d7067c52d3b783988917869e13d1d on 2.4 branch.
> Jason, please try it, I've seen from log render standby on Evan's T500 is on
> and disabled by driver.
Wang, I will try out your changes tomorrow night... I spent a few minutes tonight (was able to build the driver with your commit), but gave up for now after running into issues with dlopen in X11 not being able to find the new libdrm_intel.so.1.
To the others in this thread -- did you install your module into /usr/local? What was the magic you needed to get it to work? I added /usr/local/lib/xorg/modules to my ModulePath and exported /usr/local/lib in LD_LIBRARY_PATH but still no luck
I used ./autogen.sh --prefix=/usr
I tried /usr/local with no luck and didn't care to go poking around in xorg internals to modify the driver search path.
(In reply to comment #22)
> Wang, I will try out your changes tomorrow night... I spent a few minutes
> tonight (was able to build the driver with your commit), but gave up for now
> after running into issues with dlopen in X11 not being able to find the new
When I booted up my laptop this morning my Xorg.conf was still set to use the intel driver from last night, and now it's working (and I can see that it's loading the driver I built from git).
I can also run glxinfo and see that direct rendering is on. glxinfo isn't crashing for me, either.
As far as I can tell this bug is fixed :-)
Good. So I'm closing this bug.
If any of you find further problems (like Eitan's glxinfo segfault), please open a separate bug for tracking.
Created attachment 18955 [details]
Xorg.0.log crash when on battery
I am using the intel driver from the latest git repo, and I am seeing a similar crash again.
This only happens when my laptop (thinkpad x200) is on battery but goes away when it is on AC. Would this be relevant to this bug or there are some other configs I messed up?
The crash log is attached.
This bug definitely isn't fixed. I just built the head of the git tree, and my X200 suffers the same blank screen problem as with plain 2.4.2.
I can say with 100% certainty that it did fix the problem for me on a T400 w/ GM45 graphics. Also resolved DPMS off issues.
How 'bout some details. What do you mean "blank screen problem"? What OS, kernel, Xorg, libdrm?
Sorry, the missing point here is that the patch is on both git master and 2.4-branch, but not included in 2.4.2 release. (I don't know if we'd plan to release 2.4.3, as 2.5.0 is very close to be out.) So please try to pull current xf86-video-intel-2.4-branch.
(In reply to comment #28)
> This bug definitely isn't fixed. I just built the head of the git tree, and my
> X200 suffers the same blank screen problem as with plain 2.4.2.
We would close the bug if the original reporter says his problem resolved. Yours may be different issue (though with similar sympton). So please file a new bug instead of reopening this, according to http://www.intellinuxgraphics.org/how_to_report_bug.html. Thanks.
Reopened as http://bugs.freedesktop.org/show_bug.cgi?id=17507