https://bugzilla.kernel.org/show_bug.cgi?id=53071
Summary: Problems with gpe13 interrupt storm.
Product: ACPI
Version: 2.5
Kernel Version: 3.7.4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: BIOS
AssignedTo: acpi_b...@kernel-bugs.osdl.org
ReportedBy: james.dut...@gmail.com
Regression: No
Created an attachment (id=91841)
--> (https://bugzilla.kernel.org/attachment.cgi?id=91841)
acpidump -b
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?
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?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
