I agree that the temproary fix shohuld be safe. It was a good idea. I've
been trying to debug the issue myself, and though I have not been
sucessful, can still share with you what I have done - it may be of some
use.
I don't have a Toshiba Satellite Pro but have tried to repro on a Lenovo
T60P, which has the same INTEL 82573L. On the T60P, I don't see the
problem you report, so will continue hunting for a Toshiba.
Here is what I see, using the same eeprom settings as you have, on my
T60P.
1) shutdown -h now
2) As long as there is any active WOL setting (there is in your eeprom image,
and that's the setting that you disabled using the ethtool command), the link
"bounces" down and then up as the driver unloads. At the connected equipment, I
can see that the link is back to 1Gb for a few seconds, and the system
continues its shutdown. If there is no WOL setting, the link does not come
back, and this is becuase the driver requests that the NIC phy powers down.
3) If there is still power to the NIC (ie there was some type of WOL active as
indicated in ethtool eth0), AND the BIOS is configured for wol enabled, AND the
system is either docked or powered by power cord, the link is then
reestablished at 100Mbps while the system is otherwise powered down. If the NIC
was already powered down, OR the system is on battery power, OR the BIOS was
configured with WOL disabled, there is no link.
I looked at the e1000e differences between the 2.6.27.9 and 2.6.27.11
builds, and there's very little changed: nothing that I thin could
account for your problem. So its likely something in the kernel changes,
interracting with the Toshiba BIOS. Once I get a Toshiba, I should be
able to go a llittle further. Could you provide the BIOS version number
on your Toshiba, it might help me align my testing with yours when I get
hold of one.
Its interesting that you have shown that you can temporarily resolve the
issue using "ethtool -s eth0 wol d", and it makes sense too, as this
allows the driver to request that the NIC powers down before the main
kernel shuts-down. Because the initial WOL settings are loaded from the
EEPROM, we could also disable them in the EEPROM instead, so you
wouldn't need to use a script to run "ethtool -s eth0 wol d", and it
should be a workable solution until we figure out the kernel/BIOS
interaction. If you do this, of course there will be no Wake On Lan
capability unless you later restore the EEPROM settings, and we don't
want to keep changing the EEPROM settings to dynamically control the
feature.
If you do want to do this, you can disable WOL in the eeprom by:
ethtool -E eth0 magic 0x109a8086 offset 0x49 value 0x49
--
2.6.27-11 Intel Ethernet e100e Remains active after shutdown
https://bugs.launchpad.net/bugs/323256
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
