On Saturday, January 26, 2013 09:46:24 AM James Courtier-Dutton wrote: > Some more detailed context can be found here: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793 > > Scope (_GPE) > { > Method (_L13, 0, NotSerialized) > { > If (LEqual (PFLV, FDTP)) > { > Return (Zero) > } > > Store (Zero, GPE3) > Or (GL08, 0x10, GL08) > Notify (\_SB.PCI0.SAT0, 0x82) > Return (Zero) > } > } > > This is the DSDT code for GPE13 on a Samsung Series 7 700Z5C laptop. > There error reported by the Linux kernel is: > ev_queue_notify_reques: No notify handler for Notify, ignoring (SAT0, 82) > > Now, my question is: > How do I find out what device is causing the GPE13 interrupt and why? You can look into the ACPI tables, for example. Please file a but at bugzilla.kernel.org against ACPI and assign it to me. Please put the output of acpidump on your system as an attachment to the bug entry. > How do I work out what code (which device register bit to reset) I have to > put in this Notify handler in order to silence the interrupt storm? You need to find out what the cause of the Notify is first. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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
