From owner-freebsd-net@FreeBSD.ORG Sun Apr 11 12:35:04 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DF74106566C; Sun, 11 Apr 2010 12:35:04 +0000 (UTC) (envelope-from jille@quis.cx) Received: from mulgore.hexon-is.nl (mulgore.hexon-is.nl [82.94.237.14]) by mx1.freebsd.org (Postfix) with ESMTP id DD38A8FC08; Sun, 11 Apr 2010 12:35:03 +0000 (UTC) Received: from hinterlands.hexon-is.nl (hinterlands.hexon-is.nl [82.94.237.6]) by mulgore.hexon-is.nl (8.14.3/8.14.3) with ESMTP id o3BC3Lfh021761; Sun, 11 Apr 2010 14:03:21 +0200 MIME-Version: 1.0 Date: Sun, 11 Apr 2010 14:03:21 +0200 From: Jille Timmermans To: , Message-ID: <8d194046e93da0b44295f29a75a5775f@imap.hexon.cx> X-Sender: jille@quis.cx User-Agent: RoundCube Webmail/0.2.2 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 X-Hexon-MailScanner-Information: Please contact the ISP for more information X-Hexon-MailScanner-ID: o3BC3Lfh021761 X-Hexon-MailScanner: Found to be clean X-Hexon-MailScanner-From: jille@quis.cx X-Hexon-MailScanner-Watermark: 1271592202.73004@bnkzIcjHfemPkIezA1LqTg Cc: Subject: Panic with VIMAGE and pf X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Apr 2010 12:35:04 -0000 Hello, I was trying to enable VIMAGE (for use with jails) but stumbled upon the following panic: Fatal trap 12: page fault while in kernel mode fault virtual address: 0x28 current proceess = 38 (pfctl) db> bt pfil_head_get() at +0x41 pfioctl() at +0x11f2 devfs_ioctl_f() at +0x77 kern_ioctl() at +0xf6 ioctl() at +0xf0 syscall() +0x137 I can easily reproduce this in single user mode using: # kldload pf # pfctl -f /etc/pf.conf I disabled VIMAGE and the panic didn't occur anymore. I'm running amd64 stable/8; r206458. (I also tried this 3 weeks ago; but had the same problem) I'm not able to get a dump; the memory dump-thing stalls after printing the first mark. -- Jille