What driver was this for?
If you're not Paul (p-f-j-geraedts); please file a separate bug report
for your issue.
In particular, it's not up to NetworkManager to shut down the
interfaces, but up to the kernel to properly clean up on shutdown so
that wake on lan can work.
Reassigning to 'linux'.
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/576110
Title:
Wake-on-lan not working because wired interface not deconfigured when
NetworkManager is stopped
Status in “linux” package in Ubuntu:
New
Bug description:
Binary package hint: network-manager
1) The release of Ubuntu you are using:
Problem occurs in two different laptops; one running Ubuntu 9.10 and the
other Ubuntu 10.04.
2) The version of the package you are using:
Ubuntu 9.10: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1,
Ubuntu 10.04: network-manager 0.8-0ubuntu3.
3) What you expected to happen:
When network-manager is stopped (e.g. when I shutdown Ubuntu) I expect both
my eth0 (LAN) and eth1 (WLAN) interface to be properly brought down during the
process. To be more precise, I expect syslog reporting something like:
May 5 02:14:31 pentium NetworkManager: <WARN> nm_signal_handler():
Caught signal 15, shutting down normally.
May 5 02:14:31 pentium NetworkManager: <info> (eth0): cleaning up...
May 5 02:14:31 pentium NetworkManager: <info> (eth0): taking down
device.
May 5 02:14:32 pentium kernel: [ 711.888429] tg3 0000:01:00.0: PME#
enabled
May 5 02:14:32 pentium NetworkManager: <info> (eth1): taking down
device.
May 5 02:14:32 pentium NetworkManager: <info> exiting (success)
4) What happened instead.
The above syslog is only reported when I had deactivated eth0 manually before
stopping network-manager (by means of bringing network-manager to sleep,
disconnecting the active eth0 connection or by physically removing the ethernet
cable). If I leave the eth0 connection activate during stopping
network-manager, it is not brought down properly:
May 5 02:17:15 pentium NetworkManager: <WARN> nm_signal_handler():
Caught signal 15, shutting down normally.
May 5 02:17:15 pentium NetworkManager: <info> (eth1): taking down
device.
May 5 02:17:15 pentium NetworkManager: <info> exiting (success)
5) Why should this be fixed?
Not bringing the eth0 interface down properly, effectively leaves it in an
undefined state. This disallows me to use the WOL(wake-on-lan) functionality of
the ethernet chipset. Currently I have to disable the network-manager
completely as work-around, because I typically have no physical access to the
machine (it is part of an unreachable measurement setup).
WOL essentially is a simple and reliable system that can be very
useful. Enabling it in BIOS and in the OS (e.g. 'ethtool -s eth0 wol
g') should do the trick. As little things like this one really
complicate matters, I think solving it makes many lifes a lot easier.
: )
Thanks in advance anyway!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/576110/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
