On Fri, 19 Oct 2007, Luca Capello wrote: > On Fri, 19 Oct 2007 01:03:34 +0200, Henrique de Moraes Holschuh wrote: > > On Thu, 18 Oct 2007, Luca Capello wrote: > >> Since I experienced the oops after having changed the LCD > >> brightness, I pressed several times the brightness up/down Fn keys, > >> then removed only the thinkpad_acpi module and voila, I got the > >> oops again. > [...] > > > > Hmm, I will see if I can reproduce it. > > Thank you.
Unfortunately, I can't reproduce it. Might be a 32/64 bit issue, since I can only test x86-32, or I could not duplicate exactly what is causing the problem, but... Please compile thinkpad-acpi and ACPI with the debug modes enabled, and load thinkpad-acpi with the debug=0xffff parameter. Then reproduce the oops, and send me the entire kernel output since driver load until the oops. You could also try turning on some of the ACPI debug bits, one of them (sorry, I don't know which) will tell you exactly which device's notify handler it is calling. -- "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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
