(cc: list trimmed and thread moved to linux-pci)
I have a PCI-E e1000 card that does not see interrupts on 2.6.20-rc5
unless CONFIG_PCI_MSI is disabled. An e1000 maintainer indicated that
the PHY state is correct, it's just that the interrupt is not getting
thru to the kernel. Interestingly, on 2.6.19 PHY interrupts get thru ok
with MSI enabled (link status responds appropriately) but packet tx
fails with timeout errors, implying that perhaps MAC interrupts are not
arriving.
I've attached the contents dmesg, 'lspci -vvv', and 'cat
/proc/interrupts' from 2.6.20-rc5.
This is an nForce 430 based chipset on a Dell E521 which has had
interrupt routing issues before. Prior to 2.6.19 it had to be booted
with 'noapic' in order to come up at all. It also had USB lockup
problems until I applied the latest BIOS update (v1.1.4). So a BIOS
interrupt routing bug with MSI is not out of the question.
I'm happy to gather more data or run tests...
--Adam
Adam Kropelin wrote:
> I've attached the contents dmesg, 'lspci -vvv', and 'cat
> /proc/interrupts' from 2.6.20-rc5.
Actually attached this time.
--Adam
On Sat, Jan 20, 2007 at 02:34:37PM -0500, Adam Kropelin wrote:
> (cc: list trimmed and thread moved to linux-pci)
>
> I have a PCI-E e1000 card that does not see interrupts on 2.6.20-rc5
> unless CONFIG_PCI_MSI is disabled. An e1000 maintainer indicated that
> the PHY state is correct, it's just that the interrupt is not getting
> thru to the kernel. Interestingly, on 2.6.19 PHY interrupts get thru ok
> with MSI enabled (link status responds appropriately) but packet tx
> fails with timeout errors, implying that perhaps MAC interrupts are not
> arriving.
>
> I've attached the contents dmesg, 'lspci -vvv', and 'cat
> /proc/interrupts' from 2.6.20-rc5.
>
> This is an nForce 430 based chipset on a Dell E521 which has had
> interrupt routing issues before. Prior to 2.6.19 it had to be booted
> with 'noapic' in order to come up at all. It also had USB lockup
> problems until I applied the latest BIOS update (v1.1.4). So a BIOS
> interrupt routing bug with MSI is not out of the question.
>
> I'm happy to gather more data or run tests...
Was this regression fixed by Eric's patch that is included in -rc7?
> --Adam
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Adrian Bunk wrote:
> On Sat, Jan 20, 2007 at 02:34:37PM -0500, Adam Kropelin wrote:
>> (cc: list trimmed and thread moved to linux-pci)
>>
>> I have a PCI-E e1000 card that does not see interrupts on 2.6.20-rc5
>> unless CONFIG_PCI_MSI is disabled. An e1000 maintainer indicated that
>> the PHY state is correct, it's just that the interrupt is not getting
>> thru to the kernel. Interestingly, on 2.6.19 PHY interrupts get thru ok
>> with MSI enabled (link status responds appropriately) but packet tx
>> fails with timeout errors, implying that perhaps MAC interrupts are not
>> arriving.
>>
>> I've attached the contents dmesg, 'lspci -vvv', and 'cat
>> /proc/interrupts' from 2.6.20-rc5.
>>
>> This is an nForce 430 based chipset on a Dell E521 which has had
>> interrupt routing issues before. Prior to 2.6.19 it had to be booted
>> with 'noapic' in order to come up at all. It also had USB lockup
>> problems until I applied the latest BIOS update (v1.1.4). So a BIOS
>> interrupt routing bug with MSI is not out of the question.
>>
>> I'm happy to gather more data or run tests...
>
> Was this regression fixed by Eric's patch that is included in -rc7?
no, this is a different issue afaics. Eric's patch solves a msi vector leak
where MSI's were no longer recovered after all 256 of them were handed out. The
issue here seems to be a very different regression (no vector at all or vector
not setup correctly to begin with).
I do suggest re-testing the issue with 2.6.20rc7, but it's unlikely it fixes the
problem for Adam.
The same issue was reported 2/3 days ago by another user basically too (no
interrupts at all arriving with MSI enabled).
Cheers,
Auke
On Fri, Feb 02, 2007 at 09:25:38AM -0800, Auke Kok wrote:
> Adrian Bunk wrote:
> > On Sat, Jan 20, 2007 at 02:34:37PM -0500, Adam Kropelin wrote:
> >> (cc: list trimmed and thread moved to linux-pci)
> >>
> >> I have a PCI-E e1000 card that does not see interrupts on 2.6.20-rc5
> >> unless CONFIG_PCI_MSI is disabled. An e1000 maintainer indicated that
> >> the PHY state is correct, it's just that the interrupt is not getting
> >> thru to the kernel. Interestingly, on 2.6.19 PHY interrupts get thru ok
> >> with MSI enabled (link status responds appropriately) but packet tx
> >> fails with timeout errors, implying that perhaps MAC interrupts are not
> >> arriving.
> >>
> >> I've attached the contents dmesg, 'lspci -vvv', and 'cat
> >> /proc/interrupts' from 2.6.20-rc5.
> >>
> >> This is an nForce 430 based chipset on a Dell E521 which has had
> >> interrupt routing issues before. Prior to 2.6.19 it had to be booted
> >> with 'noapic' in order to come up at all. It also had USB lockup
> >> problems until I applied the latest BIOS update (v1.1.4). So a BIOS
> >> interrupt routing bug with MSI is not out of the question.
> >>
> >> I'm happy to gather more data or run tests...
> >
> > Was this regression fixed by Eric's patch that is included in -rc7?
>
> no, this is a different issue afaics. Eric's patch solves a msi vector leak
> where MSI's were no longer recovered after all 256 of them were handed out. The
> issue here seems to be a very different regression (no vector at all or vector
> not setup correctly to begin with).
>
> I do suggest re-testing the issue with 2.6.20rc7, but it's unlikely it fixes the
> problem for Adam.
Your thought is correct: 2.6.20-rc7 still fails.
--Adam