All of lore.kernel.org
 help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: Allen Parker <parker@isohunt.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression)
Date: Tue, 16 Jan 2007 08:48:59 -0800	[thread overview]
Message-ID: <45AD01FB.3050304@intel.com> (raw)
In-Reply-To: <45ACFA96.4040902@isohunt.com>

Allen Parker 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.
>>
>> Due to changes between 2.6.19.2 and 2.6.20, Intel driver 7.3.20 will 
>> not compile for 2.6.20, nor will the 2.6.19.2 in-tree driver.
>>
> <snip, worthless>
> Affected chipset:
>> lspci -nn output (quad port):
>> 09:00.0 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit 
>> Ethernet Controller [8086:10a4] (rev 06)
>> lspci -nn output (dual port):
>> 07:00.0 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit 
>> Ethernet Controller [8086:105e] (rev 06)
> <snip, readability>
> 
>>  From what I've been able to gather, other Intel Pro/1000 chipsets 
>> work fine in 2.6.20-rc5. If the e1000 guys need any assistance 
>> testing, I'll be more than happy to volunteer myself as a guinea pig 
>> for patches.
> 
> I wasn't aware that I was supposed to post this as a regression, so 
> changed the subject, hoping that someone will pick this up and run with 
> it. Primary issue being that link is not seen on this chipset under 
> 2.6.20-rc5 via in-tree e1000 driver, despite multiple cycles of ifconfig 
> $eth up && ethtool $eth | grep link && ifconfig $eth down. Tested on 2 
> machines with identical hardware.

I asked Allen to report this here. I'm working on the issue as we speak but for now I'll 
treat the link issue as a known regression once I confirm it. If others have seen it 
then I'd like to know ASAP of course ;)

Cheers,

Auke

  reply	other threads:[~2007-01-16 16:57 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 [this message]
2007-01-16 19:18   ` Jesse Brandeburg
2007-01-16 20:02     ` Brandeburg, Jesse
  -- strict thread matches above, loose matches on Subject: below --
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=45AD01FB.3050304@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=parker@isohunt.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.