Hi Henrique! Sorry for the delay, I was busy with real life... On Mon, 22 Oct 2007 19:00:21 +0200, Henrique de Moraes Holschuh wrote: > On Mon, 22 Oct 2007, Luca Capello wrote: > 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. It seems that the oops is no more thinkpad-acpi's fault, since yesterday and today I got the oops with ACPI's video only (read below). > 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. The oops removing ACPI's video module occurred both in 2.6.23.1 (with thinkpad-acpi-0.18) or today's git pull for linux-acpi-2.6. The machine booted with both video and thinkpad-acpi, then I removed them, enabled the ACPI debug and inserted video. To be sure that the oops wasn't video-related, I removed the video module and I got the oops (attached). I think I don't need 2.6.23.1 anymore, right? Now, since on Monday I'll bring my laptop to the IBM repairing center and since they told me that to repair the broken SD card reader they'll change the whole motherboard, I guess that they'll return me the laptop with the BIOS upgraded. So, if any urgent test is needed, I can perform it during the week-end. Thx, bye, Gismo / Luca
Attachment:
dmesg-2.6.24-rc1_linux-acpi-2.6_video-oops_gismo-20071102.log.gz
Description: removing video oops on linux-acpi-2.6_2.6.24-rc1
