[Bug 284457] periodic pf panic on busy jailhost

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

--- Comment #7 from Thomas Steen Rasmussen / Tykling <[email protected]> ---
Another panic yesterday:

Feb 21 13:27:25 hash1 syslogd: last message repeated 1 times
Feb 21 13:27:25 hash1 kernel: Fatal trap 12: page fault while in kernel mode
Feb 21 13:27:25 hash1 kernel: cpuid = 0; apic id = 00
Feb 21 13:27:25 hash1 kernel: fault virtual address     = 0x0
Feb 21 13:27:25 hash1 kernel: fault code                = supervisor write
data, page not present
Feb 21 13:27:25 hash1 kernel: instruction pointer       =
0x20:0xffffffff82f30ffa
Feb 21 13:27:25 hash1 kernel: stack pointer             =
0x28:0xfffffe01ad3d6e00
Feb 21 13:27:25 hash1 kernel: frame pointer             =
0x28:0xfffffe01ad3d6e30
Feb 21 13:27:25 hash1 kernel: code segment              = base 0x0, limit
0xfffff, type 0x1b
Feb 21 13:27:25 hash1 kernel:                   = DPL 0, pres 1, long 1, def32
0, gran 1
Feb 21 13:27:25 hash1 kernel: processor eflags  = interrupt enabled, resume,
IOPL = 0
Feb 21 13:27:25 hash1 kernel: current process           = 95978 (pf purge)
Feb 21 13:27:25 hash1 kernel: trap number               = 12
Feb 21 13:27:25 hash1 kernel: panic: page fault
Feb 21 13:27:25 hash1 kernel: cpuid = 0
Feb 21 13:27:25 hash1 kernel: time = 1740144120
Feb 21 13:27:25 hash1 kernel: KDB: stack backtrace:
Feb 21 13:27:25 hash1 kernel: #0 0xffffffff80c42835 at kdb_backtrace+0x65
Feb 21 13:27:25 hash1 kernel: #1 0xffffffff80bf6182 at vpanic+0x182
Feb 21 13:27:25 hash1 kernel: #2 0xffffffff80bf5ff3 at panic+0x43
Feb 21 13:27:25 hash1 kernel: #3 0xffffffff810b3169 at trap_fatal+0x389
Feb 21 13:27:25 hash1 kernel: #4 0xffffffff810b31b6 at trap_pfault+0x46
Feb 21 13:27:25 hash1 kernel: #5 0xffffffff8108a968 at calltrap+0x8
Feb 21 13:27:25 hash1 kernel: #6 0xffffffff82f324f5 at pf_unlink_state+0x265
Feb 21 13:27:25 hash1 kernel: #7 0xffffffff82f31bcd at
pf_purge_expired_states+0x14d
Feb 21 13:27:25 hash1 kernel: #8 0xffffffff82f31a2b at pf_purge_thread+0x13b
Feb 21 13:27:25 hash1 kernel: #9 0xffffffff80bb159f at fork_exit+0x7f
Feb 21 13:27:25 hash1 kernel: #10 0xffffffff8108b9de at fork_trampoline+0xe
Feb 21 13:27:25 hash1 kernel: Timeout initializing vt_vga
Feb 21 13:27:25 hash1 kernel: Uptime: 7d6h51m26s
Feb 21 13:27:25 hash1 kernel: Dumping 9010 out of 65410
MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%---<<BOOT>>---

No core:

[tykling@hash1 ~]$ sudo savecore -v
unable to open bounds file, using 0
checking for kernel dump on device /dev/nvd0p2
mediasize = 10737418240 bytes
sectorsize = 512 bytes
magic mismatch on last dump header on /dev/nvd0p2
unable to open bounds file, using 0
checking for kernel dump on device /dev/nvd1p2
mediasize = 10737418240 bytes
sectorsize = 512 bytes
magic mismatch on last dump header on /dev/nvd1p2
[tykling@hash1 ~]$ man savecore
[tykling@hash1 ~]$ sudo savecore -Cv
checking for kernel dump on device /dev/nvd0p2
mediasize = 10737418240 bytes
sectorsize = 512 bytes
magic mismatch on last dump header on /dev/nvd0p2
checking for kernel dump on device /dev/nvd1p2
mediasize = 10737418240 bytes
sectorsize = 512 bytes
magic mismatch on last dump header on /dev/nvd1p2
No dump exists
[tykling@hash1 ~]$

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