[Bug 256757] net/realtek-re-kmod: kernel panic when running kernel with INVARIANTS

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 21 Jun 2021 20:05:06 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256757

            Bug ID: 256757
           Summary: net/realtek-re-kmod: kernel panic when running kernel
                    with INVARIANTS
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ale_at_FreeBSD.org
          Reporter: niels=freebsd_at_bakker.net
             Flags: maintainer-feedback?(ale_at_FreeBSD.org)
          Assignee: ale_at_FreeBSD.org

...
re0: <Realtek PCIe 2.5GbE Family Controller> port 0xd000-0xd0ff mem
0xf7a10000-0xf7a1ffff,0xf7a20000-0xf7a23fff irq 18 at device 0.0 on pci5
re0: Using Memory Mapping!
re0: Using 1 MSI-X message
re0: version:1.96.04
re0: Ethernet address: 00:e0:4c:xx:xx:xx

This product is covered by one or more of the following patents:            
US6,570,884, US6,115,776, and US6,327,625.
...
re0: link state changed to UP
panic: _mtx_lock_sleep: recursed on non-recursive mutex re0 _at_ if_re.c:7085

cpuid = 1
time = 1623711227
KDB: stack backtrace:
#0 0xffffffff80c3b5c5 at kdb_backtrace+0x65
#1 0xffffffff80bf0fa1 at vpanic+0x181
#2 0xffffffff80bf0d73 at panic+0x43
#3 0xffffffff80bce208 at __mtx_lock_sleep+0x478
#4 0xffffffff80bcdd32 at __mtx_lock_flags+0xa2
#5 0xffffffff828e87eb at re_init+0x2b
#6 0xffffffff828e7fbd at re_ioctl+0x1dd
#7 0xffffffff80d04dc5 at ifhwioctl+0xf65
#8 0xffffffff80d05f5f at ifioctl+0x37f
#9 0xffffffff80c5c8c9 at kern_ioctl+0x289
#10 0xffffffff80c5c58a at sys_ioctl+0x12a
#11 0xffffffff81083ede at amd64_syscall+0x12e
#12 0xffffffff81057e2e at fast_syscall_common+0xf8
Uptime: 17s
Dumping 792 out of 16147 MB:..3%..11%..21%..31%..41%..51%..61%..71%..81%..91%

A panic only occurs with INVARIANTS / INVARIANT_SUPPORT in the kernel config.

-- 
You are receiving this mail because:
You are the assignee for the bug.
Received on Mon Jun 21 2021 - 20:05:06 UTC

Original text of this message