Eth0 Error Reading Phy Register
Contents |
instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be possible with some types e1000_phy_read_status error reading phy register of ads) More information about our ad policies X You seem to
Eth1 Error Reading Phy Register
have CSS turned off. Please don't fill out this field. You seem to have CSS turned off. Please don't fill out this field. Briefly describe the problem (required): Upload screenshot of ad (required): Select a file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse Intel Ethernet Drivers and Utilities Mailing Lists Intel Ethernet Drivers and Utilities Brought to you by: aabodun, ahduyck, asinghai, atbrady, and 20 others Summary Files Reviews Support Wiki Mailing Lists Tickets ▾ Bugs Patches Feature Requests News e1000-devel e1000-eedc e1000-rdma Re: [E1000-devel] e1000e: repeated eth0: Error reading PHY register Re: [E1000-devel] e1000e: repeated eth0: Error reading PHY register From: Andy Isaacson
Post #1 of 5 (870 views) Permalink 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 https://sourceforge.net/p/e1000/mailman/message/28940676/ 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 http://www.gossamer-threads.com/lists/linux/kernel/1482542 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 100bas
registerOn Wed, Jan 25, 2012 at 11:16:16AM -0800, Andy Isaacson wrote:> On Wed, Jan 25, 2012 at 05:00:29PM +0000, Allan, https://lkml.org/lkml/2012/1/26/455 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 error reading 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=447449Hi Bruce,Please stop requiring us to use the sourceforge issue tracker.1. It requires answers to irrelevant and annoying error reading phy questions to create anaccount (which is required to report or comment on bugs).2. It doesn't properly handle whitespace-aligned text, making the bughistory very annoying to read. And the font it chooses doesn'tdistinguish 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 thelineendings. I don't even want to speculate how they managed to fuckthat 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 withsome vendor-specific custom install process. I am happy to test gittrees or apply patches, but I don't have time or inclination to dealwith vendor build+install scripts.Thanks,-andy La