On Sun, 21 Oct 2007, Luca Capello wrote: > BTW, I needed to play a bit with module loading/unloading, since the > first time I removed the thinkpad_acpi module the oops wasn't > triggered. Hmm, am I going crazy, or did the OOPS happen with an instance of thinkpad-acpi *not* loaded with debug=0xffff? Can you try that again making sure it always gets the debug=0xfffff parameter? Apparently, it was active only the first time you tried to load the module, and I wanted to see the exit path debug messages of the instance that gets an OOPS... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
