Bug 22982 - [i830 KMS] xorg hang on 2.8.0 [regression]
Summary: [i830 KMS] xorg hang on 2.8.0 [regression]
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86 (IA32) Linux (All)
: high critical
Assignee: Carl Worth
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: NEEDINFO, regression
Depends on:
Blocks:
 
Reported: 2009-07-27 18:34 UTC by Bryce Harrington
Modified: 2009-10-09 14:23 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
xsession-errors.modedebug (1.23 KB, text/plain)
2009-07-27 18:36 UTC, Bryce Harrington
no flags Details
syslog after hang (296.49 KB, text/plain)
2009-07-27 18:36 UTC, Bryce Harrington
no flags Details
Xorg.0.log.0722 (64.12 KB, text/plain)
2009-07-27 18:37 UTC, Bryce Harrington
no flags Details
intel batchbuffer dump (250.09 KB, application/octet-stream)
2009-07-30 12:28 UTC, Jerry Amos
no flags Details

Description Bryce Harrington 2009-07-27 18:34:46 UTC
Forwarding this bug from Ubuntu reporter jerrylamos:
http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/403037

[Problem]
Hangs after login with brown screen and cursor.  Regression with the 2.8.0 driver.

[Original Description]
karmic 2.6.31-3 with intel driver 2.8.0  on IBM Thinkpad R31 i830 video graphics.   Hangs after login with brown screen and cursor.  Keyboard not responsive except power off.

Karmic was running O.K. fresh install of daily build 20090217.  Then did apt-get update, dist-upgrade on 20090722 which included intel driver 2.8.0.  

Dual booted Intrepid (distinctly better video response!) to get .xsession-errors, Xorg.0.log, syslog, lspci -vvnn which will be attached following.  

Alpha3 booted on my i845 by passing the "nomodeset" parameter and booting "vesa" driver.  But this doesn't work on the i830 since booting with driver vesa doesn't work on jaunty or intrepid on the i830 either.
Comment 1 Bryce Harrington 2009-07-27 18:36:18 UTC
Created attachment 28066 [details]
xsession-errors.modedebug
Comment 2 Bryce Harrington 2009-07-27 18:36:42 UTC
Created attachment 28067 [details]
syslog after hang
Comment 3 Bryce Harrington 2009-07-27 18:37:04 UTC
Created attachment 28068 [details]
Xorg.0.log.0722
Comment 4 Gordon Jin 2009-07-27 20:24:18 UTC
How about "nomodeset" with intel 2.8.0 driver?
Comment 5 Jerry Amos 2009-07-30 12:28:08 UTC
Created attachment 28204 [details]
intel batchbuffer dump

Attached is the batchbuffer dump as requested taken after the hang using ssh.

It's a bit of a bear to ssh since as hung, the mouse pointer has to be moved after every keystroke or copy in order to get any response.

Let me know if there's a problem with the dump and it needs to be re-done.

Thanks, Jerry
Comment 6 Carl Worth 2009-07-31 09:19:44 UTC
(In reply to comment #5)
> Created an attachment (id=28204) [details]
> intel batchbuffer dump
> 
> Attached is the batchbuffer dump as requested taken after the hang using ssh.
> 
> It's a bit of a bear to ssh since as hung, the mouse pointer has to be moved
> after every keystroke or copy in order to get any response.

Thanks for your bug report Jerry. The symptom of needing to move the mouse pointer to get a keystroke response via ssh is certainly an interesting one. I'm not aware of having heard that before.

I'll try getting an i830 booting recent Ubuntu here to see if I can replicate the bug.

-Carl
Comment 7 Carl Worth 2009-09-11 13:55:25 UTC
Eric Anholt posted a kernel patch yesterday that fixes several hangs for
pre-9xx chipsets:

http://lists.freedesktop.org/archives/intel-gfx/2009-September/004122.html

Jerry, it would be very useful if you could test with that patch and report
here whether or not it fixes your bug.

Thanks,

-Carl
Comment 8 Carl Worth 2009-09-17 11:44:28 UTC
(In reply to comment #6) 
> Thanks for your bug report Jerry. The symptom of needing to move the mouse
> pointer to get a keystroke response via ssh is certainly an interesting one.
> I'm not aware of having heard that before.

By the way, I later found out that this was a kernel bug that has also been
fixed since. So hopefully a newer kernel will fix all your problems. :-)

-Carl
Comment 9 Eric Anholt 2009-10-09 14:23:15 UTC
Feedback timeout.  If you later find that the bug isn't fixed by that patch, please re-open.


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.