Comment 19 for bug 719620

Hi Herton,

It took me a while to report back. I checked the latest kernel you sent (b3) only to find that it's bad as well (no video after resume). Since you mentioned it seemed odd, I went back and retested our original known-good kernel (2.6.38-2) and found, to my dismay, that it is also bad; this means my original testing was flawed. I apologize for this, I'm really sorry I made this mistake.

Since we installed Lucid on the A11 for some testing, I checked the kernel included and found that one to work correctly (i.e. everything comes back fine after suspend/resume). That being a 2.6.32 kernel, it seemed quite far back in time, but at least it's a known good starting point.

I went back to the mainline kernel archive and did some poor man's bisecting with the compiled kernels, and found the last known good kernel (on which suspend/resume works fine on the A11) is 2.6.34rc1, from 9-Mar-2010. The next one, 2.6.34.1 from Maverick, dated 6-Jul-2010, exhibits the problem we've been tracking here. During the process I also tested a number of 2.6.35 kernels, all of which have the same problem. So it looks like the interval between 2.6.34rc1 and 2.6.34-1 is where the problem was introduced.

How do these mainline kernels map to Ubuntu ones? is there anywhere I can get Ubuntu kernels to download and test like I did the mainlines? I also git cloned ubuntu-natty and ubuntu-maverick kernel trees to see if I could do the bisect process but I'm not sure, based on the known good and bad mainline kernels, how to pick the initial good and bad commits.

I hope this is useful, and again, my sincerest apologies for screwing up on the initial good/bad kernel assessment. I was more thorough this time.

Thanks for all your help!