[Bug 209428] if_vtnet(4) panics when doing kldunload if_vtnet

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue May 10 15:14:13 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209428

            Bug ID: 209428
           Summary: if_vtnet(4) panics when doing kldunload if_vtnet
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: novel at FreeBSD.org

When using if_vtnet(4) as a module and unloading it using "kldunload if_vtnet"
it immediately causes a panic:

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x80
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff80cff56d
stack pointer           = 0x28:0xfffffe0096eb28a0
frame pointer           = 0x28:0xfffffe0096eb28d0
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 779 (kldunload)
[ thread pid 779 tid 100058 ]
Stopped at      uma_zone_get_cur+0xd:   movq    0x80(%r14),%rdi
db> bt
Tracing pid 779 tid 100058 td 0xfffff800064219a0
uma_zone_get_cur() at uma_zone_get_cur+0xd/frame 0xfffffe0096eb28d0
vtnet_modevent() at vtnet_modevent+0x51/frame 0xfffffe0096eb2900
module_unload() at module_unload+0x32/frame 0xfffffe0096eb2920
linker_file_unload() at linker_file_unload+0x24b/frame 0xfffffe0096eb2970
kern_kldunload() at kern_kldunload+0xbc/frame 0xfffffe0096eb29a0
amd64_syscall() at amd64_syscall+0x2db/frame 0xfffffe0096eb2ab0
Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe0096eb2ab0
--- syscall (444, FreeBSD ELF64, sys_kldunloadf), rip = 0x80086b15a, rsp =
0x7fffffffe348, rbp = 0x7fffffffebb0 ---
db>

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list