Hi Henrique! On Sat, 20 Oct 2007 02:27:20 +0200, Henrique de Moraes Holschuh wrote: > On Fri, 19 Oct 2007, Luca Capello wrote: >> On Fri, 19 Oct 2007 01:03:34 +0200, Henrique de Moraes Holschuh wrote: >>> Hmm, I will see if I can reproduce it. >> >> Thank you. > > Unfortunately, I can't reproduce it. [...] > 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. Done (and dmesg attached). Disabling CONFIG_THINKPAD_ACPI_HOTKEY_POLL doesn't change anything (and the dmesg attached is with that option enabled). 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. Please let me know if you want my .config as well. > 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. Well, I think I've all the ACPI debug options already on, since CONFIG_ACPI_DEBUG=y and CONFIG_ACPI_DEBUG_FUNC_TRACE=y, as well as CONFIG_PM_DEBUG=y (and CONFIG_THINKPAD_ACPI_DEBUG=y, obviously). Thx, bye, Gismo / Luca
Attachment:
dmesg-2.6.23.1_thinkpad-acpi-0.18-oops_gismo-20071021.log.gz
Description: 2.6.23.1 kernel and thinkpad_acpi-0.18 oops
