All right if you are game I would like to try chasing down where it starts failing to boot and where it works again, and if we are lucky maybe we can also trace down the bug we are looking for.
so might as well test rc7 and rc8 too rc7 http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.rc7_amd64.deb
rc8 http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.rc8_amd64.deb
next test kernel http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.40_amd64.deb
based on 2f2c779583e9646097b57599f8efeb8eca7bd654
After this the plan is to bisect both sides, between the last good commit - rc1, and rc8 - last bad commit
All right if you are game I would like to try chasing down where it starts failing to boot and where it works again, and if we are lucky maybe we can also trace down the bug we are looking for.
so might as well test rc7 and rc8 too people. canonical. com/~jj/ linux-image- 2.6.39- 2-generic_ 2.6.39- 2.7~lp793437. rc7_amd64. deb
rc7 http://
rc8 http:// people. canonical. com/~jj/ linux-image- 2.6.39- 2-generic_ 2.6.39- 2.7~lp793437. rc8_amd64. deb
next test kernel people. canonical. com/~jj/ linux-image- 2.6.39- 2-generic_ 2.6.39- 2.7~lp793437. 40_amd64. deb
http://
based on 2f2c779583e9646 097b57599f8efeb 8eca7bd654
After this the plan is to bisect both sides, between the last good commit - rc1, and rc8 - last bad commit