Hi ACPI folks, Bjorn Helgaas wrote: > On Tue, Jan 10, 2012 at 9:59 AM, Josh Boyer <jwboyer@xxxxxxxxxx> wrote: >> We've had a report [1] from a user that the 3.1.6 kernel panics if they >> plug or unplug their machine. The oops seems to come from an issue >> somewhere in the acpi notification stack. The relevant backtrace >> functions are (transcribed from a jpeg): >> >> acpi_ac_notify >> acpi_device_notify >> acpi_ev_notify_dispatch >> acpi_os_execute_deferred > > Images 1 & 2 from the bugzilla also show kobject_uevent(), so my guess > is the problem is in the ACPI ac driver, e.g., maybe > ac->charger.dev->kobj isn't being initialized correctly, so we blow up > when acpi_ac_notify() calls kobject_uevent(). Added cc: for recent ac > changes. [...] >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=772730 More reports: https://bugzilla.kernel.org/show_bug.cgi?id=38782 (includes DSDT fix) http://bugs.debian.org/661995 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/414541 Dell doesn't take emailed reports re the Inspiron 1090 BIOS so Giovanni Biscuolo (cc-ed) reported it to http://en.community.dell.com/support-forums/laptop/f/3518/t/19439525.aspx I wonder: - could Linux diagnose the duplicate ACAD in a more helpful way? - is it possible to work around, for example by letting the last AC adaptor win on the Inspiron 1090? - what does Windows do? Hope that helps, Jonathan -- 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