https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283450
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059
--- Comment #38 from stee...@energy.wsu.edu ---
(In reply to Aleksandr Fedorov from comment #37)
Could the following linked comment be related to this issue? It seems to be
saying about the same thing.
https://github.com/freebsd/freebsd-s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059
Aleksandr Fedorov changed:
What|Removed |Added
CC||afedo...@freebsd.org
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283426
--- Comment #1 from Robin Haberkorn ---
It cannot have anything to do with the ethernet driver, since I wasn't
connected via ethernet, but via wifi (if_iwm), which is also apparent from the
backtrace. So it might have something to do with t
On Fri, Dec 20, 2024 at 07:48:05AM +, Sad Clouds wrote:
S> > Please take a look at https://reviews.freebsd.org/D48148
S>
S> Thanks for the info. I have some ifdefs in my user space code to handle
S> this FreeBSD bug. Is it possible to tell at this stage in which stable
S> FreeBSD release versi
