© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
The dmesg doesn't have anything unusual so far. As another thing to try, I pulled changes from drm-intel-next and built/uploaded on same url a new kernel, please test that. May be a fix is already there.
If the situation doesn't change, I'm out of new things to try. In this case if you can, something to try would be a git bisect between the working kernel (2.6.38-rc3) and failing kernel (2.6.38-rc4). If you don't know how to do, I can provide testing kernels for each bisect step, you will need to test ~3 kernels, by the commit count on i915 between rc3/rc4.