From owner-freebsd-current@FreeBSD.ORG Wed Jun 23 02:08:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B03BC16A4CE for ; Wed, 23 Jun 2004 02:08:27 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBA8443D5F for ; Wed, 23 Jun 2004 02:08:26 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pandora.afflictions.org (Postfix) with ESMTP id 60F5578C7C for ; Tue, 22 Jun 2004 22:09:34 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 4BFE5170C6; Tue, 22 Jun 2004 22:08:01 -0400 (EDT) Date: Tue, 22 Jun 2004 22:08:01 -0400 From: Damian Gerow To: current@freebsd.org Message-ID: <20040623020801.GA156@afflictions.org> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 5.2-CURRENT on a i386 X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.6i Subject: ipf 3.4.35 woes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 02:08:27 -0000 The upgrade to ipf 3.4.35 is causing me grief. And yes, my kernel and userland are in sync: ipf: IP Filter: v3.4.35 (336) Kernel: IP Filter: v3.4.35 Running: yes Log Flags: 0 = none set Default: block all, Logging: available Active list: 1 I get a panic right after bringing up lo0 on regular boot. If I boot into single user mode, bring up lo0, bring up my main interface, and then load the rules, I don't panic. My rules are simple -- a pass in quick/pass out quick pair for every interface on the machine, and a general pass in quick/pass out quick for all IPv6. There are four interfaces on this machine: lo0, rl0, fxp0, and a freshly-added ath0. The only ones that come up during boot are lo0 and fxp0. Since the panic passed through pen and paper, whitespace may be off. But here's the boot log/panic: Enabling ipfilter. lo0: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0, apic id = 0 fault virtual address = 0x10 fault code = supervisor read, page not present instruction pointer = 0x8:0xc055dbe0 stack pointer = 0x10:0xe554b95c frame pointer = 0x10:0xe554b95c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 3346 (ipf) kernel: type 12 trap, code 0 Stopped at turnstile_head+0x6: movl 0(%eax),%eax db> trace turnstile_head(0,1000000,e554b998,c052b2d2,0) at turnstile_head+0x6 _mtx_unlock_sleep(c07c2d00,0,0,0,0) at _mtx_unlock_sleep+0x4d frsync(c1b86600,c1d8fa28,c1a7abe0,e554b9bc,0) at frsync+0xfb iplioctl(c1b86600,80047249,e554bc58,3,c1a7abe0) at iplioctl+0x563 spec_ioctl(e554bb80,e554bc2c,c05a41ec,e554bb80,c1eb7a18) at spec_ioctl+0x168 spec_vnoperate(e554bb80,c1cb7a18,3,c0706c52,c07a9960) at spec_vnoperate+0x18 vn_ioctl(e1cb7a18,80047249,e554bc58,c197e600,c1a7abe0)at vn_ioctl+0x18c ioctl(c1a7abe0,e554bd14,c,280ce000,3) at ioctl+0x5a4 syscall(2f,2f,2f,bfbfeec8,2) at syscall+0x2f0 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280ce657, esp = 0xbfbfee5c, ebp = 0xbfbfee78 --- db> - Damian