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_
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 correc
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
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
proc-irq-2.6.20-rc5
Description: Binary data
dmesg-2.6.20-rc5
Description: Binary data
lspci-2.6.20-rc5
Description: Binary data
(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, o
5 matches
Mail list logo