On Mon, 22 Oct 2007, Luca Capello wrote:
> Sorry, my fault.  It should be OK now.

I was afraid of that, the OOPs happens entirely after the thinkpad-acpi
module unloaded.

And we *did* unregister all notification functions in thinkpad-acpi, so it
might well be a problem in the ACPI core, and not thinkpad-acpi.

Please try again, this time do this beforehand (warning: will generate a lot
of debug output):

echo 0x4 > /proc/acpi/debug_layer
echo 0xfffffff > /proc/acpi/debug_level

Maybe we will be lucky and give us more info on what the ACPI layer is
calling that causes the oops.

You could also try adding a sleep() call of a second or so in
thinkpad-acpi's thinkpad_acpi_module_exit function, after the loop that
calls ibm_exit.  It is one of those ibm_exit calls that unregister the
notify handler for hotkey (the only one active in your thinkpad-acpi
install).  If it is a race, that might eliminate it and give us further
information.

-- 
  "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

Reply via email to