Still Broken: "After lid-close reopening; wifi hangs; fixed by netif restart" in 15-CURRENT

[sgharms]

Folks,

Happy New Year! Year 2 of FreeBSD as home machine

Last year I reported that after lid close I had to do service netif restart to restore service. T-Daemon identified a bug predicting that behavior and cracauer@ confirmed it was impacting more than me. T-Daemon also suggested that it was fixed in (then) 15.0-CURRENT and my hope was that this would magically go away once I upgraded. Well, I'm upgraded to 15.0-RELEASE, and it's still with me.

Based on the bug tracking references (like the library of Name of the Rose...), I came to this note https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286059 that suggests that the fix is believed to be in main.

So I'm looking for "I"m still broken too" signals OR "You dolt, you've misread the bug tracker; it wasn't fixed" or "You dolt, it was fixed and you forgot to run magic-command hardware-reify - p!" Any takers?

 

[SirDice]

15-CURRENT doesn't exist any more.

FreeBSD 15.0-RELEASE Announcement

FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.

www.freebsd.org

 

[sgharms]

15-CURRENT doesn't exist any more.

FreeBSD 15.0-RELEASE Announcement

FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.

www.freebsd.org

I've clarified that it was the then-15.0-CURRENT, which I believe became 15.0-RELEASE at the time you noted in December. Tag naming correctness aside, is that likely to explain the persistence of the bug?

 

[SirDice]

If the bug fix was commited to 15-CURRENT then, it's included with 15.0-RELEASE.

 

[sgharms]

If the bug fix was commited to 15-CURRENT then, it's included with 15.0-RELEASE.

Okey dokey, so it validates my report in this thread. In 15.0-RELEASE this behavior persists.

 

[SirDice]

You can see the commit history:

src - FreeBSD source tree

cgit.freebsd.org

The PR you referenced is the commit done on 2025-05-28.

Could still be a bunch of bugs in it though, after stable/15 got branched off and main moved to 16-CURRENT there's been quite a lot more work done on that specific driver.

src - FreeBSD source tree

cgit.freebsd.org

If you still have problems with 15.0-RELEASE you should probably open a PR for it. Maybe some of the fixes from main can be MFC'ed to stable/15 (which will then end up in 15.1-RELEASE).

 

[sgharms]

You can see the commit history:

src - FreeBSD source tree

cgit.freebsd.org

The PR you referenced is the commit done on 2025-05-28.

Could still be a bunch of bugs in it though, after stable/15 got branched off and main moved to 16-CURRENT there's been quite a lot more work done on that specific driver.

src - FreeBSD source tree

cgit.freebsd.org

If you still have problems with 15.0-RELEASE you should probably open a PR for it. Maybe some of the fixes from main can be MFC'ed to stable/15 (which will then end up in 15.1-RELEASE).

Thanks for the tips. I've opened https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292249 accordingly.