Wake On Lan doesn't react

Bug #714417 reported by Samuel Bancal on 2011-02-07
52
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: network-manager

In the shutdown process, my network card doesn't seems to be in a valid state ... which leads to no answer to WakeOnLan magic packets.

My tests :
- shutdown from Ubuntu10.04 & Network-Manager : WOL failed
- shutdown from other OS : WOL worked
both several times ...
- shutdown from Ubuntu10.04 & Network-Manager ... un-plug power supply for 10 seconds, re-plug it (which triggers some automatic BIOS initialisation) : WOL worked

My problem resolution was to purge network-manager network-manager-gnome and configure the network the old fashion in /etc/network/interfaces .

My System ...
Description: Ubuntu 10.04.2 LTS
Release: 10.04
package versions :
network-manager 0.8-0ubuntu3
network-manager-gnome 0.8-0ubuntu3

sudo lspci -k | grep -A 2 Ethernet
08:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit Ethernet PCI Express (rev 02)
 Kernel driver in use: tg3
 Kernel modules: tg3

So when you remove network-manager WOL works properly after shutdown?

Changed in network-manager (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Samuel Bancal (samuel-bancal) wrote :

That's correct.

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Natty Narwhal. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Samuel Bancal (samuel-bancal) wrote :

I tested this with the Ubuntu 11.04 alpha-2 live (on USB stick).
The problem is still present.

Well, in all likelihood this is actually a driver issue in how the tg3 driver gets shutdown, so reassigning to the 'linux' package.

affects: network-manager (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
Samuel Bancal (samuel-bancal) wrote :

But the tg3 driver is also used in my actual config :
- no NetworkManager
- configuration set in /etc/network/interfaces
And with this, my card seems to be shutdown correctly (WOL packets can wake my computer up).

Jeremy Foshee (jeremyfoshee) wrote :

Hi Samuel,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 714417

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete

Removing needs-upstream-testing because the Natty CD has been tested (even if it was for an alpha release in February...

Samuel, could you provide the logs in /var/log/syslog to include as much as possible what happens before shutdown, then after the system is brought up manually? I think that should include all the information we need.

Furthermore, please confirm how exactly you do the Wake-On-Lan process. Seems like here, my system only reports supporting WOL by Magic Packet. It's possible there's something special happening to the device (like it not being fully turned off when NM is running because NM would be shut down late, maybe?) which could affect WOL. That kind of thing could transpire from the logs.

tags: removed: needs-upstream-testing
Samuel Bancal (samuel-bancal) wrote :

Mathieu,

I installed Ubuntu 11.04 daily (28 mar) on an other partition and did the test.

Here are my steps :
- Boot & login
- NetworkManager say when I click on it (in grey) : "Wired Network<br>device not managed"
- Configured anyway the network
- check connectivity with ifconfig and ping : ok
- Shutown
- WakeOnLan from another PC : worked!
- Boot & login (Gnome crashed)
- Reboot & login
- copied /var/log/syslog (here attached)

How I do the WakeOnLan :
From an other PC on the same subnet (same switch). With Ubuntu 9.10 (I know I'll have to change this) with /usr/bin/wakeonlan (from package wakeonlan).

My question :
At first glance, It seems that the problem is solved. But the "device not managed" let me think that the NetworkManager didn't manage that interface. If so, we're falling in the same case as I am now (NetworkManager removed) which makes it work for me.

Indeed, if NM says not managed, then you likely have config in /etc/network/interfaces and then it doesn't touch the interfaces configured there.

Samuel Bancal (samuel-bancal) wrote :

Ok.
So this test didn't help.

I tried to update this morning, but NM still says "Not managed".

Samuel Bancal (samuel-bancal) wrote :

Hello,

I just did the test again this morning with Natty beta1.
- Fresh new install
- Boot
- configured network (this time NM did not said "not managed")
- shutdown
- WOL ... didn't work!

Attached the /var/log/syslog

Nerdknight (nerdknight) wrote :

I can't neither WOL after shutting down from updated Ubuntu 11.04. It worked with Ubuntu 10.10.

lspci -k | grep -A 2 Ethernet:
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
 Subsystem: Intel Corporation Device d608
 Kernel driver in use: r8169

zeckenleger (gho-nexgo) wrote :

Last comment I can confirm. Same here, have the same controller. I have tested it with two Live-CDs (10.04 & 11.04).
I have set paramater NETDOWN to no in /etc/init.d/halt in both live sessions before shutting down.

With natty there is no waking up.

I have the same problem (WOL doesn't work in 11.04)

My Ethernet device:

lspci -k | grep -A 2 Ethernet
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
 Subsystem: ASUSTeK Computer Inc. P5B
 Kernel driver in use: r8169

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Ken (meel2mi) wrote :

I have also the same problem. OS is Ubuntu 10.04.3

Network manager needs to be completly removed for WOL to work. As I also have wlan on my laptop, this is not an option.
If network manager is not started during startup, and eth0 is configured manually, WoL also works, but wlan is affected.
If network manager is started, wlan works, WoL doesn't and it gives me shutdown problems.

08:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
 Kernel driver in use: tg3
 Kernel modules: tg3

Julien (julien-guilpin) wrote :

I have exactly the same issue with a Dell optiplex 330 PC with Broadcom Corporation NetLink BCM5787 and ubuntu 11.04.

My tests with network manager:
- Unplug and plug power cable: wol ok
- Start then shutdown ubuntu: wol failed.

Even if network manager not managed the network (static IP in command line), wol doesn't work.

I had to remove network-manager to be able to woks wake on lan...

Samuel Bancal, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

tags: added: lucid needs-upstream-testing
tags: added: natty
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Samuel Bancal (samuel-bancal) wrote :

Christopher M. Penalver,

Sorry for answering that late...
I installed 12.04.1 ... and the problem is fixed.
Same hardware and using the NetworkManager.

Regards,
Samuel

Changed in linux (Ubuntu):
status: Expired → Fix Released
Milind (m-kinge) wrote :

NetworkManager have problem for WakeUp Lan services on Dell 330 desktop i to faced same problem and resolved by removing NetworkManager.

Tx Gyus for help

Rx
MK

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers