Forwarding this bug from Ubuntu reporter jerrylamos:
Hangs after login with brown screen and cursor. Regression with the 2.8.0 driver.
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.
Created attachment 28066 [details]
Created attachment 28067 [details]
syslog after hang
Created attachment 28068 [details]
How about "nomodeset" with intel 2.8.0 driver?
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.
(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.
Eric Anholt posted a kernel patch yesterday that fixes several hangs for
Jerry, it would be very useful if you could test with that patch and report
here whether or not it fixes your bug.
(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. :-)
Feedback timeout. If you later find that the bug isn't fixed by that patch, please re-open.