Wake-on-LAN stopped working with 4.15.0-24 kernel

Bug #1779899 reported by Bill Miller
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Wake-on-LAN had been working fine since Bionic installed. When kernel 4.15.0-24 was pushed out and installed, it quit working. Set system to boot from 4.15.0-23, and it works again.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-24-generic 4.15.0-24.26
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: bill 1741 F.... pulseaudio
 /dev/snd/controlC0: bill 1741 F.... pulseaudio
CurrentDesktop: LXDE
Date: Tue Jul 3 11:14:09 2018
HibernationDevice: RESUME=UUID=adc97911-6d93-4094-8ec4-15cab05377e7
InstallationDate: Installed on 2018-04-27 (66 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
 lo no wireless extensions.

 enp4s0 no wireless extensions.
MachineType: ASUSTeK COMPUTER INC. M11AD
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=0ca22edb-e6b0-412b-ad6e-00b2126b37c7 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-24-generic N/A
 linux-backports-modules-4.15.0-24-generic N/A
 linux-firmware 1.173.1
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0302
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M11AD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: Desktop
dmi.product.name: M11AD
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Bill Miller (wbmilleriii) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Bill Miller (wbmilleriii) wrote :

I was able to work around this by re-enabling WoL in the card: sudo ethtool -s [card] wol g

Other computers on the LAN did not stop waking up and did not require the work around.

Revision history for this message
Bill Miller (wbmilleriii) wrote :

Disregard the 2nd sentence in comment #3. I cannot confirm that this is true.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

This is because the fix of LP: #1752772 has one commit [1] that disables WoL by default.
Set WoL explicitly should solve your issue.

[1] https://github.com/torvalds/linux/commit/7edf6d314cd061e1d0a1b7bc0b511d64322c3f72

Revision history for this message
Bill Miller (wbmilleriii) wrote :

Thank you for the confirmation!

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

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'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc3

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Bill Miller (wbmilleriii) wrote :

@jsalisbury as explained by @kaihengfeng this change was advertent so this is probably not really a bug at all.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.