From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 05:34:31 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 5216016A4CE for ; Fri, 6 Feb 2004 05:34:31 -0800 (PST) Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6949443D1D for ; Fri, 6 Feb 2004 05:34:29 -0800 (PST) (envelope-from ianf@hetzner.co.za) Received: from localhost ([127.0.0.1]) by hetzner.co.za with esmtp (Exim 3.36 #1) id 1Ap67m-0008lj-00 for FreeBSD-current@freebsd.org; Fri, 06 Feb 2004 15:34:26 +0200 From: Ian Freislich In-reply-to: Your message of "Thu, 05 Feb 2004 12:07:37 +0200." X-Attribution: BOFH Date: Fri, 06 Feb 2004 15:34:26 +0200 Sender: ianf@hetzner.co.za Message-Id: cc: FreeBSD-current@freebsd.org Subject: Re: Random panics 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: Fri, 06 Feb 2004 13:34:31 -0000 Ian Freislich wrote: > Hi > > I get these panics at what appears random intervals and indeterminate > cause. Higher load does seem to increase the frequency though. On > an unload machine it might occur this often: Well, I've figured out what was triggering the panics: mail delivery - which is why it appears random. The configuration is somewhat different: Exim-3.36-2 with aliases and relay/local domains in a PostgreSQL-7.4.1 database. Running the queue on my backup MX gets this far: [brane] ~ # exim -d1 -M 1AnyuD-0000vC-00 Exim version 3.36 debug level 1 uid=0 gid=0 probably Berkeley DB version 1.8x (native mode) delivering message 1AnyuD-0000vC-00 Connecting to brane-dead.freislich.nom.za [196.7.162.29.25] ... connected SMTP<< 220 brane-dead.freislich.nom.za ESMTP Exim 3.36 #1 Fri, 06 Feb 2004 15:21:29 +0200 SMTP>> EHLO brane.freislich.nom.za ^C Immediately following the EHLO the other server panics with the message and stack trace below. kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc05136de stack pointer = 0x10:0xcdb1aab0 frame pointer = 0x10:0xcdb1aad0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 29 (swi1: net) trap number = 12 panic: page fault at line 819 in file ../../../i386/i386/trap.c Stack backtrace: backtrace(c0658db6,c06a4e20,333,c066a433,100) at backtrace+0x17 __panic(c066a433,333,c0648fcf,c066a28b,1) at __panic+0xd4 trap_fatal(cdb1aa70,24,ffffffff,7fffffff,24) at trap_fatal+0x346 trap(10018,c3d00010,10,0,c0fc02a0) at trap+0x123 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc05136de, esp = 0xcdb1aab0, ebp = 0xcdb1aad0 --- propagate_priority(c0fc02a0,c3bad2a0,2,0,c06a6770) at propagate_priority+0x7e turnstile_wait(0,c06a922c,c3bad2a0,0,0) at turnstile_wait+0x2f4 _mtx_lock_sleep(c06a922c,0,0,0,c0fc71b8) at _mtx_lock_sleep+0xd8 tcp_input(c0fd1700,14,87,c0501fc5,c0fc02a0) at tcp_input+0x31e ip_input(c0fd1700,de732fb8,c06ad654,0,c06a85b8) at ip_input+0xa8c netisr_processqueue(c06a85b8,4405b730,e97c9fc4,0,c0fb5840) at netisr_processqueu e+0xd9 swi_net(0,42fcc,46a54,425ec,c0fc02a0) at swi_net+0xc9 ithread_loop(c0fbd480,cdb1ad48,c5a0,43740,0) at ithread_loop+0x1d8 fork_exit(c04d4c00,c0fbd480,cdb1ad48) at fork_exit+0x80 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcdb1ad7c, ebp = 0 --- Ian -- Ian Freislich