Red Hat Bugzilla – Bug 199546
Can't ether-wake after shutting down from 2.6.17
Last modified: 2007-11-30 17:11:38 EST
Description of problem:
If I shutdown while running 2.6.17 my network card powers off completely and
ether-wake cannot wake the box. If I shutdown from 2.6.16 the card remains
powered up and ether-wake works fine.
Version-Release number of selected component (if applicable):
kernel-smp-2.6.17-1.2139_FC5, kernel-smp-2.6.17-1.2145_FC5 and
kernel-smp-2.6.17-1.2157_FC5 all fail. kernel-smp-2.6.16-1.2122_FC5 and
kernel-smp-2.6.16-1.2133_FC5 both work.
Steps to Reproduce:
1. Boot a 2.6.17 kernel.
2. Shut down the box (from within GNOME or whatever)
3. Watch the link light on the switch.
The link light goes out at around the time the "shutting down interface eth0"
message is displayed. ether-wake cannot wake the box.
With 2.6.16 the link light remains on throughout the shutdown process. It goes
out when the disks and fans power off, but comes back on after maybe a second.
ether-wake wakes the box as expected.
It's a Dell Precision 380 with a 3.4GHz Pentium D running an i686 kernel.
dmesg says the network card is "Tigon3 [partno(BCM5751PKFBG) rev 4001 PHY(5750)]
(PCI Express) 10/100/1000"
Would you mind trying the fedora-netdev kernels in order to ensure that this
problem is still pending upstream?
Please give them a try and post the results here...thanks!
kernel-smp-2.6.17-1.2145.2.4_FC5.netdev.6 has the problem.
Did you do ethtool -s eth0 wol g? The tg3 driver in 2.6.17 was changed to
honor the ethtool WoL setting and override the NVRAM's setting. If that
works, you can set it up automatically in the ifcfg-eth0 script with
Cool, that works (2.6.17-1.2174_FC5smp).