e1000e: repeated eth0: Error reading PHY register

e1000e: repeated eth0: Error reading PHY register

[Andy Isaacson]

On my Thinkpad X201s running 3.3-rc1 I'm seeing bursts of these:

[ 1270.207370] e1000e 0000:00:19.0: eth0: Error reading PHY register
[ 1271.003042] e1000e 0000:00:19.0: eth0: Error reading PHY register
[ 1271.798896] e1000e 0000:00:19.0: eth0: Error reading PHY register
[ 1272.595324] e1000e 0000:00:19.0: eth0: Error reading PHY register

I've been seeing these messages for a few kernel versions, but
unfortunately due to a hardware failure I don't have kernels further
back than 3.0.  I'm pretty sure this didn't happen on 2.6.38.

There are nearly always exactly 12 messages (I have one log sequence
where there are only 5, out of 110 occurrences), and they come every 300
seconds during some period, then they go away for a long time, then come
back with no clear cause.

% dmesg | grep PHY | uniq -w4 -c
 25 [    1.253783] e1000e 0000:00:19.0: eth0: MAC: 9, PHY: 10, PBA No: A002FF-0FF
 12 [  370.314165] e1000e 0000:00:19.0: eth0: Error reading PHY register
 12 [  670.201544] e1000e 0000:00:19.0: eth0: Error reading PHY register
 12 [  970.045374] e1000e 0000:00:19.0: eth0: Error reading PHY register
 12 [ 1270.207370] e1000e 0000:00:19.0: eth0: Error reading PHY register
 12 [ 1570.031407] e1000e 0000:00:19.0: eth0: Error reading PHY register

(the clock is currently at 3636.)

The machine is on and off of AC power, and suspended with "sudo
pm-suspend" then resumed, on a regular basis; there doesn't seem to be
any clear correlation.

There's nothing plugged into the ethernet jack when this happens.  (I
don't use wired ethernet often enough to be sure if it happens when the
wire is connected; there doesn't seem to be any impact on
functionality on the rare occasion I do use it.)

% sudo ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: Unknown!
        Duplex: Unknown! (255)
        Port: Twisted Pair
        PHYAD: 2
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000001 (1)
                               drv
        Link detected: no

% sudo lspci -vvvs 0:19
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 06)
        Subsystem: Lenovo Device 2153
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 40
        Region 0: Memory at f2500000 (32-bit, non-prefetchable) [size=128K]
        Region 1: Memory at f2525000 (32-bit, non-prefetchable) [size=4K]
        Region 2: I/O ports at 1820 [size=32]
        Capabilities: [c8] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
                Address: 00000000fee0f00c  Data: 4149
        Capabilities: [e0] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-
        Kernel driver in use: e1000e


Full dmesg at http://web.hexapodia.org/~adi/snow/dmesg-3.3.0-rc1

Thanks,
-andy

RE: e1000e: repeated eth0: Error reading PHY register

[Allan, Bruce W]

>-----Original Message-----
>From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
>owner@vger.kernel.org] On Behalf Of Andy Isaacson
>Sent: Wednesday, January 25, 2012 1:21 AM
>To: linux-kernel@vger.kernel.org; netdev@vger.kernel.org; e1000-
>devel@lists.sourceforge.net
>Subject: e1000e: repeated eth0: Error reading PHY register
>
>On my Thinkpad X201s running 3.3-rc1 I'm seeing bursts of these:
>
>[ 1270.207370] e1000e 0000:00:19.0: eth0: Error reading PHY register
>[ 1271.003042] e1000e 0000:00:19.0: eth0: Error reading PHY register
>[ 1271.798896] e1000e 0000:00:19.0: eth0: Error reading PHY register
>[ 1272.595324] e1000e 0000:00:19.0: eth0: Error reading PHY register
>
>I've been seeing these messages for a few kernel versions, but
>unfortunately due to a hardware failure I don't have kernels further
>back than 3.0.  I'm pretty sure this didn't happen on 2.6.38.
>
>There are nearly always exactly 12 messages (I have one log sequence
>where there are only 5, out of 110 occurrences), and they come every 300
>seconds during some period, then they go away for a long time, then come
>back with no clear cause.
>
>% dmesg | grep PHY | uniq -w4 -c
> 25 [    1.253783] e1000e 0000:00:19.0: eth0: MAC: 9, PHY: 10, PBA No: A002FF-
>0FF
> 12 [  370.314165] e1000e 0000:00:19.0: eth0: Error reading PHY register
> 12 [  670.201544] e1000e 0000:00:19.0: eth0: Error reading PHY register
> 12 [  970.045374] e1000e 0000:00:19.0: eth0: Error reading PHY register
> 12 [ 1270.207370] e1000e 0000:00:19.0: eth0: Error reading PHY register
> 12 [ 1570.031407] e1000e 0000:00:19.0: eth0: Error reading PHY register
>
>(the clock is currently at 3636.)
>
>The machine is on and off of AC power, and suspended with "sudo
>pm-suspend" then resumed, on a regular basis; there doesn't seem to be
>any clear correlation.
>
>There's nothing plugged into the ethernet jack when this happens.  (I
>don't use wired ethernet often enough to be sure if it happens when the
>wire is connected; there doesn't seem to be any impact on
>functionality on the rare occasion I do use it.)
>
>% sudo ethtool eth0
>Settings for eth0:
>        Supported ports: [ TP ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Full
>        Supported pause frame use: No
>        Supports auto-negotiation: Yes
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Full
>        Advertised pause frame use: No
>        Advertised auto-negotiation: Yes
>        Speed: Unknown!
>        Duplex: Unknown! (255)
>        Port: Twisted Pair
>        PHYAD: 2
>        Transceiver: internal
>        Auto-negotiation: on
>        MDI-X: Unknown
>        Supports Wake-on: pumbg
>        Wake-on: d
>        Current message level: 0x00000001 (1)
>                               drv
>        Link detected: no
>
>% sudo lspci -vvvs 0:19
>00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network
>Connection (rev 06)
>        Subsystem: Lenovo Device 2153
>        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>Stepping- SERR+ FastB2B- DisINTx+
>        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
><MAbort- >SERR- <PERR- INTx-
>        Latency: 0
>        Interrupt: pin A routed to IRQ 40
>        Region 0: Memory at f2500000 (32-bit, non-prefetchable) [size=128K]
>        Region 1: Memory at f2525000 (32-bit, non-prefetchable) [size=4K]
>        Region 2: I/O ports at 1820 [size=32]
>        Capabilities: [c8] Power Management version 2
>                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-
>,D3hot+,D3cold+)
>                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
>        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
>                Address: 00000000fee0f00c  Data: 4149
>        Capabilities: [e0] PCI Advanced Features
>                AFCap: TP+ FLR+
>                AFCtrl: FLR-
>                AFStatus: TP-
>        Kernel driver in use: e1000e
>
>
>Full dmesg at http://web.hexapodia.org/~adi/snow/dmesg-3.3.0-rc1
>
>Thanks,
>-andy

Please file a bug with this information at
http://sourceforge.net/tracker/?group_id=42302&atid=447449

Re: e1000e: repeated eth0: Error reading PHY register

[Andy Isaacson]

On Wed, Jan 25, 2012 at 05:00:29PM +0000, Allan, Bruce W wrote:
> >On my Thinkpad X201s running 3.3-rc1 I'm seeing bursts of these:
> >
> >[ 1270.207370] e1000e 0000:00:19.0: eth0: Error reading PHY register
> 
> Please file a bug with this information at
> http://sourceforge.net/tracker/?group_id=42302&atid=447449

Man sourceforge sure has jumped the shark; their signup form requires
"job title" and "company size".  I wonder how many other CEOs of 20,000+
employee companies bother to report ethernet driver bugs.

And we don't have "bugs", we have "artifacts".  Sigh.

Anyways, here you go:
https://sourceforge.net/tracker/?func=detail&aid=3479714&group_id=42302&atid=447449

-andy

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired

Re: e1000e: repeated eth0: Error reading PHY register

[Andy Isaacson]

On Wed, Jan 25, 2012 at 11:16:16AM -0800, Andy Isaacson wrote:
> On Wed, Jan 25, 2012 at 05:00:29PM +0000, Allan, Bruce W wrote:
> > >On my Thinkpad X201s running 3.3-rc1 I'm seeing bursts of these:
> > >
> > >[ 1270.207370] e1000e 0000:00:19.0: eth0: Error reading PHY register
> > 
> > Please file a bug with this information at
> > http://sourceforge.net/tracker/?group_id=42302&atid=447449
> 
> Man sourceforge sure has jumped the shark; their signup form requires
> "job title" and "company size".  I wonder how many other CEOs of 20,000+
> employee companies bother to report ethernet driver bugs.
> 
> And we don't have "bugs", we have "artifacts".  Sigh.
> 
> Anyways, here you go:
> https://sourceforge.net/tracker/?func=detail&aid=3479714&group_id=42302&atid=447449

Hi Bruce,

Please stop requiring us to use the sourceforge issue tracker.

1. It requires answers to irrelevant and annoying questions to create an
account (which is required to report or comment on bugs).

2. It doesn't properly handle whitespace-aligned text, making the bug
history very annoying to read.  And the font it chooses doesn't
distinguish between l, I, and 1.

3. the email it sends me shows my text with ^M (yes, two bytes, caret M,
in a text/plain, charset=UTF-8, quoted-printable message body) at the
lineendings.  I don't even want to speculate how they managed to fuck
that up.

4. the email it sends contains the entire bug:

[1000 lines of Description text]
[newest comment]
[previous comment]
...
[oldest comment]

So you have to navigate to the middle of the email to find the new text.

5. It does not support comment-via-email.

Not related to the issue tracker per se, but also annoying:

6. Your engineers want me to triage using some out-of-tree driver with
some vendor-specific custom install process.  I am happy to test git
trees or apply patches, but I don't have time or inclination to deal
with vendor build+install scripts.

Thanks,
-andy

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired

Re: e1000e: repeated eth0: Error reading PHY register

[Andy Isaacson]

On Thu, Jan 26, 2012 at 03:19:13PM -0800, Andy Isaacson wrote:
> On Wed, Jan 25, 2012 at 11:16:16AM -0800, Andy Isaacson wrote:
> > On Wed, Jan 25, 2012 at 05:00:29PM +0000, Allan, Bruce W wrote:
> > > >On my Thinkpad X201s running 3.3-rc1 I'm seeing bursts of these:
> > > >
> > > >[ 1270.207370] e1000e 0000:00:19.0: eth0: Error reading PHY register
> > > 
[snip]
> > https://sourceforge.net/tracker/?func=detail&aid=3479714&group_id=42302&atid=447449

FWIW, this log message is not showing up in 3.3-rc4.

... Which is very surprising since there are changes AFAICS, but it's
definitely not there...

-andy