http://bugzilla.kernel.org/show_bug.cgi?id=12873


Len Brown <len.br...@intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEEDINFO
            Summary|ACPI SCI does not interrupt |irq 9: nobody cared -
                   |- Toshiba Satellite         |Toshiba Satellite
                   |P305D-S8828                 |P305D-S8828




--- Comment #25 from Len Brown <len.br...@intel.com>  2009-04-21 03:26:41 ---
As the ACPI SCI worked properly in 2.6.24 in its default mode (level, low),
and the latest kernel uses the same mode, I don't think that any combination
of "acpi_sci=" is going to fix the issue with the latest kernel.

What seems to have changed is that there are now a rash of
ACPI SCI interrupts provoked, acpi_irq() does not claim them and
so the kernel shuts down IRQ9 as a screaming interrupt.

("irqpoll" will work around this symptom when IRQ 9 gets shut off.
However, it will work only to the extent that there are other
interrupts going on in the system to kick off the polling)

comment #13 shows that there were 999 invocations of the acpi_sci
and that all 999 were GPE's, and all 999 were GPE 03:

gpe03:     999    enabled
...
gpe_all:     999
sci:     999

Was this grep taken after "irq 9: nobody cared"?
What did "grep acpi /proc/interrupts" show?

Unfortunately, /sys/firmware/acpi/interrupts is showing
handled interrupts only, and not counting all calls to acpi_irq --
I'll send a debug patch to add that shortly...

In the mean time, it may be useful to try to isolate this issue
in two ways.

1. disable all features possible and see if your interrupt
still works.  eg. with CONFIG_ACPI=y, disable all the optional
acpi drivers (eg. battery, ac etc.) and see if irq9 still gets
disabled.  If no, add them back, say, starting with "button"
until you see which driver provokes the breakage.

2. git bisect drivers/acpi/ec.c between the working and failing kernels
   to see if it was an EC specific change that provoked the issue.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to