Maverick screen freeze with "shadow" intel driver

Can you get a dmesg from after the screen freezes? You might have to ssh in from another computer to do it.

Brian,

here's a dmesg from a "GPU hung" on 9/1 with the "shadow". I've been running a Beta lately but I can switch to the Alpha3 with "shadow" on in xorg.conf to see if I get another.

Jerry

Brian, I'm back from holiday. Running with "shadow" screen froze after about 10 minutes. Also, there was a crash on booting, and another crash 10 minutes later at about the time of the freeze.

I had an ssh running just in case and used it to create a dump.tar including dmesg, i915_error_state, Xorg.0.log, uname -a, intel driver version, xsession-errors. I also saved the two crash reports one on booting and one when the screen froze and can provide them if they are of interest.

Booting now with "shadow" commented out.

I could try the "Shadow" fix on Beta if anyone thinks it is applicable and would be of interest. Do note that on my i845G and my i830 Beta is running default intel driver with KMS on specifying only "quiet".

Jerry

Hey jerrylamos,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.