From owner-freebsd-stable@FreeBSD.ORG Fri Jan 27 03:23:48 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E01A106566C for ; Fri, 27 Jan 2012 03:23:47 +0000 (UTC) (envelope-from gjp@in-addr.com) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id BC6838FC17 for ; Fri, 27 Jan 2012 03:23:47 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.77 (FreeBSD)) (envelope-from ) id 1RqcPX-0007PD-M3 for freebsd-stable@freebsd.org; Thu, 26 Jan 2012 22:23:35 -0500 Date: Thu, 26 Jan 2012 22:23:35 -0500 From: Gary Palmer To: freebsd-stable@freebsd.org Message-ID: <20120127032335.GE17973@in-addr.com> References: <20120127024815.GD17973@in-addr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120127024815.GD17973@in-addr.com> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gjp@in-addr.com X-SA-Exim-Scanned: No (on noop.in-addr.com); SAEximRunCond expanded to false Subject: Re: Panic on 7.4-RELEASE-p5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2012 03:23:48 -0000 On Thu, Jan 26, 2012 at 09:48:15PM -0500, Gary Palmer wrote: > Hi, > > My Soekris firewall just panic'd > [snip] > I think this has happened on this box before (or a similar incident anyway, > I didn't have the console wired up the last time so I didn't get the above > trace). Just found old daily security e-mail with the last panic Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc34b6a08 fault code = supervisor write, page not present instruction pointer = 0x20:0xc06faa58 stack pointer = 0x28:0xd5096a34 frame pointer = 0x28:0xd5096b18 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 38 (syncer) trap number = 12 panic: page fault KDB: stack backtrace: db_trace_self_wrapper(c079803d,c07f6fa0,c0789da0,d50968e0,d50968e0,...) at db_trace_self_wrapper+0x26 panic(c0789da0,c07b423e,c2d087a4,1,1,...) at panic+0xed trap_fatal(c1154000,c34b6000,2,0,c2b5985c,...) at trap_fatal+0x240 trap_pfault(d5096960,d5096964,0,173a,c2d08580,...) at trap_pfault+0x27a trap(d50969f4) at trap+0x35e calltrap() at calltrap+0x6 --- trap 0xc, eip = 0xc06faa58, esp = 0xd5096a34, ebp = 0xd5096b18 --- softdep_disk_io_initiation(c2b96730,1000,c302d84c,9,c2b96730,...) at softdep_disk_io_initiation+0xd8 ffs_geom_strategy(c302d84c,c2b96730,1000,f9fd3000,ffffffff,...) at ffs_geom_strategy+0x13b ufs_strategy(d5096b84,d5096b84,c07ef140,c37e29b4,c2b96730,...) at ufs_strategy+0x64 bufstrategy(c37e2a74,c2b96730,4000,0,c37e29b4,...) at bufstrategy+0x2e bufwrite(c2b96730,ffffffff,4ab2de0,0,d5096c1c,10,8,4000,0,1,d5096c04,ffffe7f4,ffffffff,4000,d5096c24,c0706a53,c37e2a0c,0,4000,0,0) at bufwrite+0xfe vfs_bio_awrite(c2b96730,200012,0,c2cb7d20,0,...) at vfs_bio_awrite+0x51 ffs_syncvnode(c37e29b4,3,c37e2a74,d5096cf0,c05f5083,...) at ffs_syncvnode+0x2c5 ffs_fsync(d5096cd0,d5096cd0,c2cb7d20,c079e9a0,681,...) at ffs_fsync+0x1c sched_sync(0,d5096d38,aa55aa55,aa55aa55,aa55aa55,...) at sched_sync+0x6f3 fork_exit(c05f4990,0,d5096d38) at fork_exit+0x8d fork_trampoline() at fork_trampoline+0x8 Main difference seems to be the above panic came via the syncer but from bufwrite on up the stack is the same Was on 7.3-RELEASE back in July last year. Thanks, Gary