Am Montag, den 06.12.2010, 09:28 -0700 schrieb Bjorn Helgaas: > On Saturday, December 04, 2010 08:49:12 am Tobias Karnat wrote: > > Applying the patch from the thread, makes the problem occurring less > > often and dmesg shows acpi-button loads for me on hid PNP0C0C and > > LNXPWRBN. > > > > Maybe commit e2fb9754d27513918a4936e8cbaad50ff56cfd3d > > ACPI: button: remove unnecessary null pointer checks > > has unmasked an underlying problem? > > The oopses from the bugzilla are not the sort I would expect from > a null pointer dereference, but since it's fairly reproducible for > you, it might be worth reverting e2fb9754d27 to see whether it makes > any difference. I was not able to revert it. But it would only mask the problem anyway... I have now reverted bf04a77227db76f163bc2355ef4e176794987be2 ACPI: button: cache hid/name/class pointers and build acpi_button as a module but this makes no difference. > Does Rich's script from https://bugzilla.novell.com/show_bug.cgi?id=647029#c30 > help you reproduce the problem? No, it only crashes on boot (without the printk patch). If it happens the machine is completely dead, SysRq does not work. However it is definitely the acpi_button module, because removing it also fixes this. -Tobias -- 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
