Bug 199546

Summary: Can't ether-wake after shutting down from 2.6.17
Product: [Fedora] Fedora Reporter: Gary Benson <gbenson>
Component: kernelAssignee: John W. Linville <linville>
Status: CLOSED NOTABUG QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: davej, mchan, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-16 18:01:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gary Benson 2006-07-20 09:58:31 UTC
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.

How reproducible:
Always

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.
 
Actual results:
The link light goes out at around the time the "shutting down interface eth0"
message is displayed. ether-wake cannot wake the box.

Expected results:
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.

Additional info:
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"

Comment 1 John W. Linville 2006-07-26 14:03:30 UTC
Would you mind trying the fedora-netdev kernels in order to ensure that this 
problem is still pending upstream?

   http://people.redhat.com/linville/kernels/fedora-netdev/

Please give them a try and post the results here...thanks!

Comment 2 Gary Benson 2006-07-26 14:33:35 UTC
kernel-smp-2.6.17-1.2145.2.4_FC5.netdev.6 has the problem.

Comment 3 Michael Chan 2006-08-08 14:55:50 UTC
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 
ETHTOOL_OPTS.

Comment 4 Gary Benson 2006-08-16 11:48:02 UTC
Cool, that works (2.6.17-1.2174_FC5smp).