Just to make 150% sure that the code pinpointed by the git bisect process is at fault, here are two test kernels. One is marked "good", the other "bad". The good one should obviously reboot OK, while the bad one is expected to crash on reboot as reported in this bug. The kernels are based on the 2.6.38 final mainline release.
http://people.canonical.com/~roadmr/lp784484/ To test these, please make sure that you're loading the ene_ir module, meaning that the workaround I propose in the earlier comment is *not* implemented. One other way to check is to do: sudo lsmod | grep ene_ir This should output something if the module is loaded, or nothing if the module is not in use. Please report back on whether these two kernels behave as predicted; if so, we will have identified the faulty code and we could potentially file an upstream bug or request the help of someone more knowledgeable about kernel and drivers. As usual, please do this at your leisure, I don't want to impose on your time. Thanks again! --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ** Changed in: linux (Ubuntu Oneiric) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/784484 Title: dramatic kernel panic on Ubuntu 11.04 and derivatives- when rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/784484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
