Re: 10-BETA{3,4} - Consistent Kernel Panics (pf_ioctl.c:1289)

From: Gleb Smirnoff <glebius_at_FreeBSD.org>
Date: Wed, 4 Dec 2013 09:50:20 +0400
On Wed, Dec 04, 2013 at 10:19:49AM +0800, Wilkinson, Alex wrote:
W> 10.0-BETA4 FreeBSD 10.0-BETA4 #0 r258860
W> 
W> KERNCONF:
W> 
W>  	include GENERIC
W>  	
W>  	options DDB
W>  	options ALT_BREAK_TO_DEBUGGER
W>  	
W>  	options ROUTETABLES=6
W>  	options VIMAGE
W>  	
W>  	makeoptions DEBUG=-g
W>  	
W>  	device pf
W>  	device pflog
W>  	device pfsync
W>  	device carp
W> 
W> 
W> Backtrace:
W> 
W> 	(kgdb) bt
W> 	#0  doadump (textdump=1) at pcpu.h:219
W> 	#1  0xffffffff808c0005 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:447
W> 	#2  0xffffffff808c03e4 in panic (fmt=<value optimized out>) at /usr/src/sys/kern/kern_shutdown.c:754
W> 	#3  0xffffffff80346077 in db_panic (addr=<value optimized out>, have_addr=<value optimized out>, count=<value optimized out>, modif=<value optimized out>) at /usr/src/sys/ddb/db_command.c:482
W> 	#4  0xffffffff80345c8d in db_command (cmd_table=<value optimized out>) at /usr/src/sys/ddb/db_command.c:449
W> 	#5  0xffffffff80345a04 in db_command_loop () at /usr/src/sys/ddb/db_command.c:502
W> 	#6  0xffffffff80348370 in db_trap (type=<value optimized out>, code=0) at /usr/src/sys/ddb/db_main.c:231
W> 	#7  0xffffffff808f9563 in kdb_trap (type=12, code=0, tf=<value optimized out>) at /usr/src/sys/kern/subr_kdb.c:656
W> 	#8  0xffffffff80cf0612 in trap_fatal (frame=0xfffffe085bdeba60, eva=<value optimized out>) at /usr/src/sys/amd64/amd64/trap.c:877
W> 	#9  0xffffffff80cf0929 in trap_pfault (frame=0xfffffe085bdeba60, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:699
W> 	#10 0xffffffff80cf00b6 in trap (frame=0xfffffe085bdeba60) at /usr/src/sys/amd64/amd64/trap.c:463
W> 	#11 0xffffffff80cd6e52 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:232
W> 	#12 0xffffffff80aca5e3 in pfioctl (dev=0x2, cmd=<value optimized out>, addr=0xfffff803ec438000 "", flags=<value optimized out>, td=<value optimized out>) at /usr/src/sys/netpfil/pf/pf_ioctl.c:1289
W> 	#13 0xffffffff807b9d5f in devfs_ioctl_f (fp=0xfffff80014d474b0, com=3417850886, data=0xfffff803ec438000, cred=<value optimized out>, td=0xfffff80014e50920) at /usr/src/sys/fs/devfs/devfs_vnops.c:757
W> 	#14 0xffffffff80910a1e in kern_ioctl (td=0xfffff80014e50920, fd=<value optimized out>, com=2) at file.h:319
W> 	#15 0xffffffff8091079f in sys_ioctl (td=0xfffff80014e50920, uap=0xfffffe085bdeca40) at /usr/src/sys/kern/sys_generic.c:702
W> 	#16 0xffffffff80cf0f47 in amd64_syscall (td=0xfffff80014e50920, traced=0) at subr_syscall.c:134
W> 	#17 0xffffffff80cd713b in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:391
W> 	#18 0x0000000800dbac2a in ?? ()
W> 	Previous frame inner to this frame (corrupt stack?)
W> 	Current language:  auto; currently minimal
W> 	(kgdb)
W> 
W> Let me know if anyone needs more debug output.

Does the panic go away if you remove VIMAGE from kernel config?

-- 
Totus tuus, Glebius.
Received on Wed Dec 04 2013 - 04:50:23 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:45 UTC