On Tue, 2008-08-12 at 16:47 -0700, Martin Bligh wrote:
quoted text
> >> please try tip/master, or wait a while after linus pull fix from tip x86 fix.
> >
> > The fix is in the mainline already.
> 
> 
> Still looks broken to me (rc2-git5)
> 
> http://test.kernel.org/results/IBM/188946/debug/console
> 
> It got in since yesterday?

quoted text
>From the dmesg of 2.6.16 there exists the following info.
    >ACPI: PCI Interrupt 0000:2b:01.0[A] -> GSI 240 (level, low) -> IRQ
66
    ACPI: PCI Interrupt 0000:2b:01.1[B] -> GSI 244 (level, low) -> IRQ
74
   The GSI number for 0000:2b.01.0 pci device is 240.
   The GSI number for 0000:2b.01.1 pci device is 244.   

   In the function of add_pin_to_irq (in io_apic_64.c) there exists the
following checks.
         > BUG_ON(irq >= NR_IRQS);
   
   On the 2.6.16 kernel OS will map a GSI number to a different IRQ
below NR_IRQS(this macro definition is 224). So there is no problem.
  
But on the x86_64 platform of 2.6.26 kernel OS will treat the GSI number
as the IRQ number. As the GSI number for 00:2b.01.0 pci device is above
224, it will print the kernel panic info. 
   
   From the test log it seems that this issue is related with the GSI
mapping mechanism. Maybe it will be OK to use the same GSI mapping
mechanism as x86_32 platform. 

Thanks.
   Yakui

quoted text
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/