LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: Allen Parker <parker@isohunt.com>,
	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: Fri, 19 Jan 2007 16:38:41 -0800	[thread overview]
Message-ID: <45B16491.7030207@intel.com> (raw)
In-Reply-To: <011101c73c29$9f6f5db0$84163e05@kroptech.com>

Adam Kropelin wrote:
> Auke Kok wrote:
>> Adam Kropelin wrote:
>>> I haven't been able to test rc5-mm yet because it won't boot on this
>>> box. Applying git-e1000 directly to -rc4 or -rc5 results in a number
>>> of rejects that I'm not sure how to fix. Some are obvious, but the
>>> others I'm unsure of.
>>
>> that won't work. You either need to start with 2.6.20-rc5 (and pull
>> the changes pending merge in netdev-2.6 from Jeff Garzik),
> 
> I thought that's what I was doing when I applied git-e1000 to 
> 2.6.20-rc5, but I guess not.
> 
>> or start
>> with 2.6.20-rc4-mm1 and manually apply that patch I sent out on
>> monday. A different combination of either of these two will not work,
>> as they are completely different drivers.
> 
> I'll try to work something out.
> 
>> can you include `ethtool ethX` output of the link down message and
>> `ethtool -d ethX` as well? I'll need to dig up an 82572 and see
>> what's up with that, I've not seen that problem before.
> 
> ethtool output attached.

that clearly shows that the PHY detected link up status and that all is well as far as 
the driver and NIC is concerned. This bug really needs to be moved to linux-pci where 
the folks who know interrupt handling best can handle it.

Auke

  reply	other threads:[~2007-01-20  0:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2007-02-03  0:26                 ` Adam Kropelin
  -- strict thread matches above, loose matches on Subject: below --
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

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=45B16491.7030207@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=akropel1@rochester.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).