I just tried booting into the newest 3.5 release candidate (dated from June 2nd), and it choked somewhere between starting up my wireless card and reaching a login screen. While installing the mainline kernel, dpkg actually printed an error about not being able to build the nvidia module against the kernel, but I guess not even the VESA driver worked. Do you want me to try a bisect on different kernel versions, or would I need different hardware for a proper test?
I've gone ahead and attached the 3.5 kernel dmesg log. I'm not sure if you wanted me to remove the 'needs-upstream-testing' tag and change to confirmed because I was unable to test the bug specifically. If you don't consider the tags mutually exclusive, I can add back the incomplete status and upstream testing tag. I also have to report that it turns out suspend doesn't work perfectly even with the GPU. I was able to unlock the computer fine, but the fan just started running full blast, and when I tried logging out of the session, my monitor just turned off. The following restart didn't reboot the GPU so I'm back onto the VESA driver. Since it happens both with and without the GPU though, I guess the suspend issue is separate, and I think I already saw a similar bug report. ** Attachment added: "Dmesg log for the 3.5.0 kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1009312/+attachment/3177746/+files/dmesg3.5.log ** Tags removed: needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1009312 Title: GPU loads unreliably, possible kernel timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1009312/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
