LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
To: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>,
"Allen Parker" <parker@isohunt.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
"Kok, Auke-jan H" <auke-jan.h.kok@intel.com>,
<linux-pci@atrey.karlin.mff.cuni.cz>
Subject: RE: intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression)
Date: Tue, 16 Jan 2007 12:02:49 -0800 [thread overview]
Message-ID: <36D9DB17C6DE9E40B059440DB8D95F5201A78A3B@orsmsx418.amr.corp.intel.com> (raw)
In-Reply-To: <4807377b0701161118g7f15f201yea4a4c16c252a864@mail.gmail.com>
added Linux-pci
Jesse Brandeburg wrote:
> On 1/16/07, Allen Parker <parker@isohunt.com> wrote:
>> Allen Parker wrote:
>>> I have a PCI-E pro/1000 MT Quad Port adapter, which works quite well
>>> under 2.6.19.2 but fails to see link under 2.6.20-rc5. Earlier
>>> today I reported this to e1000-devel@lists.sf.net, but thought I
>>> should get the word out in case someone else is testing this kernel
>>> on this nic chipset.
>
> Upon some further investigation with Allen, I got this info, and it
> appears that his system is not freeing MSI irq's correctly.
>
> from our discussion:
>> Allen wrote:
>>> Jesse Brandeburg wrote:
>>> I believe you may have an interrupt delivery problem, due to kernel
>>> changes. When you don't get interrupts delivered correctly, you may
>>> not achieve link up.
>>>
>>> you can try disabling CONFIG_PCI_MSI in the kernel, as another
>>> trouble shooting step. Also, what model motherboard/machine are you
>>> using, and please check to make sure your BIOS is up to date.
>>
>> CONFIG_PCI_MSI seems to fix it as well, however, i'm not sure about
>> possible performance implications with leaving it turned off.
>>
>> Tyan S2927G2NR w/ 2x Opteron 2210 bios rev 1.02 iirc
>
> Also, here is an excerpt of his his proc/interrupts
> Allen Parker wrote:
> CPU0 CPU1 CPU2 CPU3
> 498: 1 8 129 8723 PCI-MSI-edge eth3
> 499: 0 42 122 17135 PCI-MSI-edge eth2
> 500: 0 19 275 1418326 PCI-MSI-edge eth1
> 501: 0 0 0 0 PCI-MSI-edge eth1
> 502: 0 414 26 25227 PCI-MSI-edge eth1
> 503: 0 37 264 1418695 PCI-MSI-edge eth0
> 504: 0 0 0 139 PCI-MSI-edge eth0
> 505: 0 6 714 22806 PCI-MSI-edge eth0
> NMI: 275 207 225 262
> LOC:3531851 3531829 3531805 3531778
> ERR: 0
>
> The disturbing bit is that on this Hypertransport to PCIe system, his
> interrupts appear to be getting registered multiple times on different
> IRQ numbers.
>
> help?
next prev parent reply other threads:[~2007-01-16 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 7:20 82571EB gigabit on e1000 in 2.6.20-rc5 Allen Parker
2007-01-16 16:17 ` intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression) Allen Parker
2007-01-16 16:48 ` Auke Kok
2007-01-16 19:18 ` Jesse Brandeburg
2007-01-16 20:02 ` Brandeburg, Jesse [this message]
2007-01-18 0:04 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
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=36D9DB17C6DE9E40B059440DB8D95F5201A78A3B@orsmsx418.amr.corp.intel.com \
--to=jesse.brandeburg@intel.com \
--cc=auke-jan.h.kok@intel.com \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=netdev@vger.kernel.org \
--cc=parker@isohunt.com \
--subject='RE: 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).