Date: Tue, 02 Apr 2024 16:02:16 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 218579] bge(4): Wake on Lan (WoL) does not work Message-ID: <bug-218579-7501-AUbQ5nUE2X@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218579-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-218579-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218579 --- Comment #60 from Cy Schubert <cy@FreeBSD.org> --- (In reply to Keve Nagy from comment #59) And when the machines are powered off following an earlier WOL, do they pow= er off? Or do they reboot? My Acer laptop will momentarily power off, then pow= er itself back on again if WOL was previously received and no intervening rebo= ot performed. This could be an Acer ACPI problem -- there are other Acer ACPI problems which are either resolved or worsened by successive ACPI imports. If the ifconfig wol keyword doesn't work, that's a problem. It works proper= ly here on 15-CURRENT and did on 14-CURRENT. The two main things I need to understand from people testing this patch are: 1. Does power off still work if the system was woken using WOL and no intervening reboot performed? (This is busted on my Acer laptop.) 2. Does ifconfig wol do anything? This works here. One caveat. ifconfig wol will not work if bge(4) is a member of lagg(4). Th= is is a lagg(4) problem. Anyone testing this patch must not use lagg(4) or they must implement a lagg(4) in rc.shutdown or rc.final. lagg(4) disables WOL. lagg(4) masks any function supported by underlying interfaces unless that s= ame function has been implemented in lagg(4). Can you please answer the two questions above? Thanks. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218579-7501-AUbQ5nUE2X>