Red Hat Bugzilla – Bug 227472
Message "sky2 eth0: phy read timeout" on console / in log
Last modified: 2007-11-30 17:07:41 EST
Description of problem:
Message "sky2 eth0: phy read timeout" appears in /var/log/messages after loading driver sky2
and before "enabling interface"; also on shutdown, console is flooded with this message.
Second appearance: on standard installation from RHEL5 DVD (from iso image) after
graphical installation screen has started, same message floods console #4.
Version-Release number of selected component (if applicable):
kernel: Linux version 2.6.18-1.2747.el5 (firstname.lastname@example.org) (gcc version
4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Thu Nov 9 18:55:30 EST 2006
kernel: sky2 v1.5 addr 0xf0100000 irq 169 Yukon-EC Ultra (0xb4) rev 2
any time on boot/shutdown OR any time on installation
Steps to Reproduce:
1. Boot installed RHEL5 / Shutdown installed RHEL5 on notebook
message "sky2 eth0: phy read timeout" appears in log/messages or floods console
no such message
Hardware: Fujitsu Siemens Lifebook E8210 (ATI)
(Marvell 88E8055 PCI-E Gigabit Eth controller Rev 12)
On http://jmaurer.awardspace.info/e8210/ (Linux from Scratch on the same hardware)
J.Maurer describes the same error and provides a bugfix: http://jmaurer.awardspace.info/e8210/
Hello, Stephan. Does this problem still exist with the RHEL5.1 beta kernel?
I ask because the latest kernel already contains the bug fix cited above,
although I don't know which RHEL5 kernel version first incorporated the fix.
it existed in the Beta before the initial release of RHEL5, but _not_ in the current released
version (with kernel 2.6.18-8.1.8.el5); i'm not using the Beta of RHEL5.1, so i cannot tell you.
And, for this issue, i was not sure, if a fix in the released RHEL should/would close a
bug message in the Beta area ...
Thanks for taking care
Don, I couldn't find the patch tracking file associated with this fix,
so I'm just setting this to CLOSED/CURRENTRELEASE (5.0). Feel free to
change the disposition (especially if you can find a dup).
I believe this have been fixed for 5.1. Re-opening and moving to MODIFIED.
Nevermind, re-read comment #2. Closing again.