Actually the list of modules Jakub is running is visible in his procModules.txt attachment here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/784484/+attachment/2134277/+files/ProcModules.txt Jakub, the ene_ir module is a handler for infrared receivers, so if you're not using your systems' infrared capabilities, one workaround for this problem is to blacklist the ene_ir module: - Open a terminal - type: sudo pico /etc/modprobe.d/blacklist.conf - At the very end of that file, add: blacklist ene_ir - Save the file by pressing ctrl-x - Reboot the system to apply these changes. After having done this, the problem should no longer appear, this would confirm the bisection's findings that the faulty code is in that module. In a short while I'll be adding links to two test kernels, one compiled with the faulty code and one without, just to test that the code does indeed trigger this problem. Of course ,for the test to be valid, you'll need to remove the blacklist line we added previously, so the troublesome module gets loaded and we can observe (or not) the bad behavior. Thanks so much for your patience and thorough testing through this long process! --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad -- 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
