I worked with shankao through private emails to bisect to the first commit that causes issues for him. Here's the output of the bisection (note that the tree is the ubuntu-lucid git tree hosted at kernel.ubuntu.com):
1369d982cea341524032a248b1f31832bb8c3eb6 is first bad commit commit 1369d982cea341524032a248b1f31832bb8c3eb6 Author: Alex Deucher <[email protected]> Date: Thu Dec 3 16:18:19 2009 -0500 drm/radeon/kms: fix vram setup on rs600 commit 722f29434e72188b2d20f9b41f4b5952073ed568 upstream. also fix up rs690 mem width. should fix fdo bug 25408 Signed-off-by: Alex Deucher <[email protected]> Signed-off-by: Dave Airlie <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Andy Whitcroft <[email protected]> :040000 040000 9bf615ab33dfcdcbd7aff53c51389705be954ba7 0f1789164ca98d79a64a7afbbbe843fa5803f02d M drivers -- At first inspection, this commit does modify the driver for the graphics card present in shankao's system, so the bisection does seem to have found the culprit. However, this change comes from the -stable tree upstream. Thus, it is odd that the 2.6.32.2 mainline kernel booted, but not our 2.6.32-10 kernel. The most likely scenario is some odd interaction between one of our patches and this change. I am going to do some further investigating to try to figure out where to go from here. -- Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12 https://bugs.launchpad.net/bugs/505808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
