Peter Lewis [2012.01.25 0919 +0000]:
On Monday 23 Jan 2012 21:53:25 Norbert Zeh wrote:
Laptop/intel graphics: Boots/reboots/halts all fine, as long as I don't suspend to RAM. After suspend to RAM, screen backlight is on, but screen remains black until turning the machine off. Apart from the screen issue, the machine seems to behave fine.
I get exactly the same behaviour on my laptop (Core i7, integrated Intel graphics).
Did you figure it out?
It's a time-consuming process. First result I got is that somewhere along the way, a commit changed processor initialization after resuming. It tries to avoid some unnecessary work. The problem is: with the "unnecessary work" (before this commit) it worked; after it, I get a kernel panic. Right now I know a point in the commit sequence where I get a kernel panic and a point where I get the black screen issue. I don't know whether there was a stage in between where there is no panic and no black screen. I have about 300 commits left to bisect, and I'll see whether I can finish bisecting this tonight (recompiling and testing the kernel about log 300 = 9 times). I don't have the expertise to fix this, but I want to know exactly where the bug was introduced, in order to provide useful information in my bug report to the kernel developers. Overall, I have the feeling that the 3.2.X kernel line introduced a number of regressions and is of much lower quality than the 3.1.X line. With 3.1.X, everything worked flawlessly. In addition to my graphics woes with 3.2.1, I also found that my intel wireless card starts misbehaving at times with 3.2.1, which it never did/does with any of the 3.1.X kernels. Cheers, Norbert -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments