LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Adam Kropelin <akropel1@rochester.rr.com>,
	linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: MSI failure on nForce 430 (WAS: intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression))
Date: Fri, 02 Feb 2007 09:25:38 -0800	[thread overview]
Message-ID: <45C37412.70205@intel.com> (raw)
In-Reply-To: <20070202164726.GH3754@stusta.de>

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

  reply	other threads:[~2007-02-02 17:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18  0:04 intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression) Adam Kropelin
2007-01-17 23:56 ` Auke Kok
2007-01-19 23:15   ` Adam Kropelin
2007-01-19 23:37     ` Auke Kok
2007-01-20  0:26       ` Adam Kropelin
2007-01-20  0:38         ` Auke Kok
2007-01-20 19:34           ` MSI failure on nForce 430 (WAS: intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression)) Adam Kropelin
2007-02-02 16:47             ` Adrian Bunk
2007-02-02 17:25               ` Auke Kok [this message]
2007-02-03  0:26                 ` Adam Kropelin
2007-01-20 19:35 Adam Kropelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45C37412.70205@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=akropel1@rochester.rr.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --subject='Re: MSI failure on nForce 430 (WAS: intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression))' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).