Hi Dima,
Thanks for looking into this.
On 20/10/2026 09:55, Ruinskiy, Dima wrote:
> I think I can fix it in the driver, but to double-check that the problem
> is indeed this, and not something else in the wake-from-shutdown path,
> could you try to reproduce with a different link partner (switch or
> back-to-back) that is known to support 10Mbps link speed?
I can't easily swap the link partner. The PC is connected directly to an
ASUS RT-AX88U Pro router, on its 2.5G LAN port, and I have no other
switch to put in between. The cables are clamped down tightly along the
furniture with no slack to reach another port, so trying a different
port would mean moving the furniture and re-running the cables. Since
this is mostly an annoyance and does not break anything, I would rather
not do that at this point. It is also unclear whether it would help:
ASUS labels the 2.5G port "2.5G/1G LAN" and lists the four other LAN
ports as gigabit, without saying whether any of them supports 10 or
100 Mbps.
Instead, I restricted the I226-V's advertisement while the system was
running and waited 30 seconds each time:
ethtool -s eno1 advertise 0x003 (10baseT only)
no link (Speed: Unknown!, Link detected: no)
ethtool -s eno1 advertise 0x00c (100baseT only)
"NIC Link is Up 100 Mbps Full Duplex" after about 3 seconds,
stable for the whole 30 seconds
After restoring the default advertisement (0x80000000002f), the link came
back at 2500 Mbps Full Duplex both times. So this port supports 100 Mbps
but not 10 Mbps, which matches your explanation.
I also need to correct my report: I cited FreeBSD bug 282140 as the same
problem. Looking at it again, FreeBSD fixed a different bug there (the
wake filters were never armed), and the PHPM change was dropped after
the reporter's switch turned out to support 10 Mbps. So the bits are the
same, but FreeBSD kept the 10 Mbps behavior.
> In recent years, an increasing number of switches stopped supporting
> 10Mbps, so we have been receiving reports of similar problems from time
> to time.
I think this is still worth addressing in the driver, if possible. As
you said, more and more network hardware no longer supports 10 Mbps, and
with such hardware Wake-on-LAN fails even when it would link at
100 Mbps. If I understand the issue correctly, keeping 100 Mbps
available in D3 as well would make it work with this router, and likely
with others like it.
Thanks,
Michael
