From: Andy Isaacson <adi@hexapodia.org>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
e1000-devel@lists.sourceforge.net
Subject: e1000e: repeated eth0: Error reading PHY register
Date: Wed, 25 Jan 2012 01:21:01 -0800 [thread overview]
Message-ID: <20120125092101.GA10626@hexapodia.org> (raw)
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
next reply other threads:[~2012-01-25 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 9:21 Andy Isaacson [this message]
2012-01-25 17:00 ` e1000e: repeated eth0: Error reading PHY register Allan, Bruce W
2012-01-25 19:16 ` Andy Isaacson
2012-01-26 23:19 ` Andy Isaacson
2012-03-06 18:49 ` Andy Isaacson
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=20120125092101.GA10626@hexapodia.org \
--to=adi@hexapodia.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 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).