https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255872
--- Comment #5 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=26c3e7a1ecb375de071786a07bdd68f867acdb3c
commit 26c3e7a1ecb375de071786a07bdd68f867acdb3c
Author:
On 6/8/21 9:16 AM, Alex Dupre wrote:
Just to be sure, have you recompiled the kernel module with the same
sources as the new debug kernel?
Sure!
If so, probably the best location to open a bug report might be here:
https://github.com/kostikbel/rere/issues
Done!
bye & Thanks
av.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #15
> I've got a 12.2/amd64 desktop pc with the following on the motherboard:
> > re0: port
> > 0xe000-0xe0ff mem 0xf7404000-0xf7404fff,0xf740-0xf7403fff irq 33 at
> > device 0.0 on pci4
X-CMAE-Envelope:
MS4xfI3JetPKe+rXxs5wSzrdeBuaH0KZ79U/puwYX+seY/Buje1azNZvOEG3Z0BVGiFjZltB7DNnh/U0zPILHHa2NXU
Andrea Venturoli wrote:
> Yesterday I compiled a kernel with all debug features in order to
> analyze some (probably unrelated) deadlock. Alas, with such features
> enabled, the machine panics at boot with:
>> _mtx_lock_sleep: recursed on non-recursive mutex re0 0 if_re.c:7085
>
> I don't have ful
