LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Adam Kropelin" <akropel1@rochester.rr.com>
To: "Auke Kok" <auke-jan.h.kok@intel.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 19:26:26 -0500	[thread overview]
Message-ID: <011101c73c29$9f6f5db0$84163e05@kroptech.com> (raw)
In-Reply-To: <45B1562C.8070503@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]

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.

> More importantly, I suspect that *again* the issue is caused by
> interrupts not arriving or getting lost.

Smells that way to me, too.

> Can you try running with MSI disabled in your kernel config?

That fixes it! The link comes up and tx/rx works well. I get about 300 
Mbps using default iperf settings with a nearby windows box.

> FYI the driver gives an interrupt to signal to the driver that link
> is up. no interrupt == no link detected. So that explains the symptom.

Yep, makes sense. I've worked with a number of PHYs like that.

--Adam

[-- Attachment #2: ethtool-eth1 --]
[-- Type: application/octet-stream, Size: 642 bytes --]

Settings for eth1:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supports auto-negotiation: Yes
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised auto-negotiation: Yes
	Speed: Unknown! (65535)
	Duplex: Unknown! (255)
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: internal
	Auto-negotiation: on
	Supports Wake-on: umbg
	Wake-on: d
	Current message level: 0x00000007 (7)
	Link detected: no

[-- Attachment #3: ethtool-d-eth1 --]
[-- Type: application/octet-stream, Size: 2441 bytes --]

MAC Registers
-------------
0x00000: CTRL (Device control register)  0x000C0241
      Duplex:                            full
      Endian mode (buffers):             little
      Link reset:                        normal
      Set link up:                       1
      Invert Loss-Of-Signal:             no
      Receive flow control:              disabled
      Transmit flow control:             disabled
      VLAN mode:                         disabled
      Auto speed detect:                 disabled
      Speed select:                      1000Mb/s
      Force speed:                       no
      Force duplex:                      no
0x00008: STATUS (Device status register) 0x00080383
      Duplex:                            full
      Link up:                           link config
      TBI mode:                          disabled
      Link speed:                        1000Mb/s
      Bus type:                          PCI
      Bus speed:                         33MHz
      Bus width:                         32-bit
0x00100: RCTL (Receive control register) 0x00008002
      Receiver:                          enabled
      Store bad packets:                 disabled
      Unicast promiscuous:               disabled
      Multicast promiscuous:             disabled
      Long packet:                       disabled
      Descriptor minimum threshold size: 1/2
      Broadcast accept mode:             accept
      VLAN filter:                       disabled
      Cononical form indicator:          disabled
      Discard pause frames:              filtered
      Pass MAC control frames:           don't pass
      Receive buffer size:               2048
0x02808: RDLEN (Receive desc length)     0x00001000
0x02810: RDH   (Receive desc head)       0x00000041
0x02818: RDT   (Receive desc tail)       0x000000FE
0x02820: RDTR  (Receive delay timer)     0x00000000
0x00400: TCTL (Transmit ctrl register)   0x310000F8
      Transmitter:                       disabled
      Pad short packets:                 enabled
      Software XOFF Transmission:        disabled
      Re-transmit on late collision:     enabled
0x03808: TDLEN (Transmit desc length)    0x00001000
0x03810: TDH   (Transmit desc head)      0x00000000
0x03818: TDT   (Transmit desc tail)      0x00000000
0x03820: TIDV  (Transmit delay timer)    0x00000008
PHY type:                                IGP

  reply	other threads:[~2007-01-20  0:26 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 [this message]
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
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='011101c73c29$9f6f5db0$84163e05@kroptech.com' \
    --to=akropel1@rochester.rr.com \
    --cc=auke-jan.h.kok@intel.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).