Vimage Jail kernel crashed

Mikolaj Golub trociny at FreeBSD.org
Sat May 4 12:07:21 UTC 2013


On Sat, May 04, 2013 at 02:52:23PM +0900, KIRIYAMA Kazuhiko wrote:

> May  4 11:19:46 xxxxxx kernel: Fatal trap 12: page fault while in kernel mode
> May  4 11:19:46 xxxxxx kernel: cpuid = 2; apic id = 02
> May  4 11:19:46 xxxxxx kernel: fault virtual address	= 0x7818c3798
> May  4 11:19:46 xxxxxx kernel: fault code		= supervisor write data, page not present
> May  4 11:19:46 xxxxxx kernel: instruction pointer	= 0x20:0xffffffff8162c19e
> May  4 11:19:46 xxxxxx kernel: stack pointer	        = 0x28:0xffffff8121b22860
> May  4 11:19:46 xxxxxx kernel: frame pointer	        = 0x28:0xffffff8121b22870
> May  4 11:19:46 xxxxxx kernel: code segment		= base 0x0, limit 0xfffff, type 0x1b
> May  4 11:19:46 xxxxxx kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
> May  4 11:19:46 xxxxxx kernel: processor eflags	= interrupt enabled, resume, IOPL = 0
> May  4 11:19:46 xxxxxx kernel: current process		= 15360 (ifconfig)
> May  4 11:19:46 xxxxxx kernel: trap number		= 12
> May  4 11:19:46 xxxxxx kernel: panic: page fault
> May  4 11:19:46 xxxxxx kernel: cpuid = 2
> May  4 11:19:46 xxxxxx kernel: KDB: stack backtrace:
> May  4 11:19:46 xxxxxx kernel: #0 0xffffffff80923446 at kdb_backtrace+0x66
> May  4 11:19:46 xxxxxx kernel: #1 0xffffffff808ed0be at panic+0x1ce
> May  4 11:19:46 xxxxxx kernel: #2 0xffffffff80c7e330 at trap_fatal+0x290
> May  4 11:19:46 xxxxxx kernel: #3 0xffffffff80c7e668 at trap_pfault+0x1e8
> May  4 11:19:46 xxxxxx kernel: #4 0xffffffff80c7ec6e at trap+0x3be
> May  4 11:19:46 xxxxxx kernel: #5 0xffffffff80c682ef at calltrap+0x8
> May  4 11:19:46 xxxxxx kernel: #6 0xffffffff8162c76d at pfi_change_group_event+0x4d
> May  4 11:19:46 xxxxxx kernel: #7 0xffffffff809a0d3b at if_delgroup+0x38b
> May  4 11:19:46 xxxxxx kernel: #8 0xffffffff809a7846 at if_clone_destroyif+0x136
> May  4 11:19:46 xxxxxx kernel: #9 0xffffffff809a831a at if_clone_destroy+0x17a
> May  4 11:19:46 xxxxxx kernel: #10 0xffffffff809a5892 at ifioctl+0x482
> May  4 11:19:46 xxxxxx kernel: #11 0xffffffff80934ef6 at kern_ioctl+0x106
> May  4 11:19:46 xxxxxx kernel: #12 0xffffffff8093513d at sys_ioctl+0xfd
> May  4 11:19:46 xxxxxx kernel: #13 0xffffffff80c7dc10 at amd64_syscall+0x540
> May  4 11:19:46 xxxxxx kernel: #14 0xffffffff80c685d7 at Xfast_syscall+0xf7

It looks like it crashed when referring vnet that had already been
destroyed, in pfi_change_group_event hook.

> Is there any suggestions? 

VIMAGE+pf support is fragile. If it works for someone it is rather by
accident. I expect replacing pf with ipfw_nat or natd will give better
results.

If you still prefer pf, you may try destroying epair interface before
destroying vnet, e.g. using prestop rc.d/jail hooks instead of
poststop, if it is possible.

-- 
Mikolaj Golub


More information about the freebsd-stable mailing list