Re: [BUG 2.6.5-rc2-bk5 and 2.6.5-rc2-mm3] ACPI seems to be broken

Re: [BUG 2.6.5-rc2-bk5 and 2.6.5-rc2-mm3] ACPI seems to be broken

[Len Brown]

[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]

> > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 22 low level)
> 
> > ACPI: SCI (IRQ22) allocation failed
> >  ACPI-0133: *** Error: Unable to install System Control Interrupt
> Handler, AE_NOT_ACQUIRED
> > ACPI: Unable to start the ACPI Interpreter

> working this issue here:
> http://bugzilla.kernel.org/show_bug.cgi?id=2366

Can somebody with hardware that exhibits this problem
apply the following 1-liner patch to the latest tree
and send me your dmesg and /proc/interrupts,
or attach it to the bug report?
(sorry for the wrap, attachment is non-wrapped).

===== drivers/acpi/bus.c 1.40 vs edited =====
--- 1.40/drivers/acpi/bus.c	Tue Mar 23 01:32:11 2004
+++ edited/drivers/acpi/bus.c	Thu Mar 25 23:50:41 2004
@@ -623,7 +623,8 @@
 		 * now that acpi_fadt is initialized,
 		 * update it with result from INT_SRC_OVR parsing
 		 */
-		acpi_fadt.sci_int = acpi_sci_override_gsi;
+		printk("acpi_fadt.sci_int %d acpi_sci_override_gsi %d\n",
+			acpi_fadt.sci_int, acpi_sci_override_gsi);
 	}
 #endif
 

In this example, this will claim IRQ9 for APIC INITIN 0-22
while traditionally we've called this IRQ22.

This brings up the bigger question of what an IRQ or GSI is...
in PIC mode they are wires on the PIC.
In APIC mode you sort of aggregate all the IOAPICS into
one linear list and call the GSI the logical INITIN number.
So why do we call the timer interrupt IRQ0 in this mode
when it is really connected to INTIN 2?  If we're consistent
with that then we should call the SCI IRQ9 instead of IRQ22...

In MSI mode, the GSI is the vector number on the CPU,
unless it is for one of the legacy IRQs, in which case
/proc/interrupts shows the PIC IRQ#.

confusing.

-Len


[-- Attachment #2: bus.patch --]
[-- Type: text/plain, Size: 443 bytes --]

===== drivers/acpi/bus.c 1.40 vs edited =====
--- 1.40/drivers/acpi/bus.c	Tue Mar 23 01:32:11 2004
+++ edited/drivers/acpi/bus.c	Thu Mar 25 23:50:41 2004
@@ -623,7 +623,8 @@
 		 * now that acpi_fadt is initialized,
 		 * update it with result from INT_SRC_OVR parsing
 		 */
-		acpi_fadt.sci_int = acpi_sci_override_gsi;
+		printk("acpi_fadt.sci_int %d acpi_sci_override_gsi %d\n",
+			acpi_fadt.sci_int, acpi_sci_override_gsi);
 	}
 #endif
 

AE_NOT_ACQUIRED, ACPI: Unable to start the ACPI Interpreter

[Len Brown]

On Fri, 2004-03-26 at 00:26, Len Brown wrote:
> > > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 22 low level)
> > 
> > > ACPI: SCI (IRQ22) allocation failed
> > >  ACPI-0133: *** Error: Unable to install System Control Interrupt
> > Handler, AE_NOT_ACQUIRED
> > > ACPI: Unable to start the ACPI Interpreter

If you encounter this issue on your hardware, can you help me fix it by
testing the latest patch at the URL below?  Either attach your dmesg and
/proc/interrupts to the bug report or send it to me, and let me know if
your power button works?

thanks,
-Len

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