Date: Fri, 10 Sep 2021 14:05:59 +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-IXFkMA1VxP@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 #42 from Cy Schubert <cy@FreeBSD.org> --- (In reply to Michel Marcon from comment #41) Actually, it is not erratic at all. But your tests have confirmed why I hav= en't committed it yet. There is something lacking and I haven't discovered it ye= t. Here are two scenarios: Your test: 1. halt -p. 2. Machine powers off. 3. WOL wakes the machine. 4. halt -p. 5. Machine appears to reboot. It doesn't reboot, actually. It powers off but a second later it powers bac= k on again. You can tell by the sound of the CPU fan. The second scenario: 1. halt -p 2. Machine powers off. 3. WOL wakes the machine. 4. Reboot (like after an installkernel or other reason). 5. halt -p. 6. WOL wakes the macihne. 7. halt -p. 8. Machine powers off. 9. WOL will work. The difference is the reboot in the second scenario. This suggests that something is missing from the patch to reset a bit in a bge(4) hardware register to not wake it a second time. This could also be an ACPI issue. (HP and Acer ACPI rely on WMI.) This is the reason the patch hasn't been committed yet. If you remember to = do a scheduled reboot sometime after a WOL it will appear fine. I will commit this patch when this last bug has been resolved. --=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-IXFkMA1VxP>