Summary: | OS craching on USB connection. | ||
---|---|---|---|
Product: | Base System | Reporter: | agniaus |
Component: | kern | Assignee: | freebsd-fs (Nobody) <fs> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Only Me | CC: | hselasky, imp, kirk |
Priority: | --- | ||
Version: | 10.2-STABLE | ||
Hardware: | amd64 | ||
OS: | Any |
Description
agniaus
2015-12-09 19:50:55 UTC
From the backtrace this is not an USB issue, but a generic filesystem issue. I put wrong kernel panic log: Dec 8 18:59:33 server kernel: Fatal trap 12: page fault while in kernel mode Dec 8 18:59:33 server kernel: cpuid = 0; apic id = 00 Dec 8 18:59:33 server kernel: fault virtual address = 0x378 Dec 8 18:59:33 server kernel: fault code = supervisor read data, page not present Dec 8 18:59:33 server kernel: instruction pointer = 0x20:0xffffffff80950ceb Dec 8 18:59:33 server kernel: stack pointer = 0x28:0xfffffe00f0f86970 Dec 8 18:59:33 server kernel: frame pointer = 0x28:0xfffffe00f0f86a30 Dec 8 18:59:33 server kernel: code segment = base rx0, limit 0xfffff, type 0x1b Dec 8 18:59:33 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Dec 8 18:59:33 server kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Dec 8 18:59:33 server kernel: current process = 13 (g_event) Dec 8 18:59:33 server kernel: trap number = 12 Dec 8 18:59:33 server kernel: panic: page fault Dec 8 18:59:33 server kernel: cpuid = 0 Dec 8 18:59:33 server kernel: KDB: stack backtrace: Dec 8 18:59:33 server kernel: #0 0xffffffff80984e30 at kdb_backtrace+0x60 Dec 8 18:59:33 server kernel: #1 0xffffffff809489e6 at vpanic+0x126 Dec 8 18:59:33 server kernel: #2 0xffffffff809488b3 at panic+0x43 Dec 8 18:59:33 server kernel: #3 0xffffffff80d4aa8b at trap_fatal+0x36b Dec 8 18:59:33 server kernel: #4 0xffffffff80d4ad8d at trap_pfault+0x2ed Dec 8 18:59:33 server kernel: #5 0xffffffff80d4a42a at trap+0x47a Dec 8 18:59:33 server kernel: #6 0xffffffff80d307a2 at calltrap+0x8 Dec 8 18:59:33 server kernel: #7 0xffffffff809507fd at _sx_xlock+0x5d Dec 8 18:59:33 server kernel: #8 0xffffffff819a2010 at g_mirror_access+0x100 Dec 8 18:59:33 server kernel: #9 0xffffffff808ab74e at g_access+0x14e Dec 8 18:59:33 server kernel: #10 0xffffffff808ad017 at g_vfs_orphan+0xc7 Dec 8 18:59:33 server kernel: #11 0xffffffff808a7c77 at g_run_events+0x237 Dec 8 18:59:33 server kernel: #12 0xffffffff8091244a at fork_exit+0x9a This sure looks weird.... However, it's against a version of FreeBSD that has gone out of support. If this problem can be reproduced on FreeBSD 13 or newer, please file a new bug so our triage processes get it on our radar. |