From owner-freebsd-current@FreeBSD.ORG  Wed Nov 24 21:31:02 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 E4E9616A4CE; Wed, 24 Nov 2004 21:31:02 +0000 (GMT)
Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com
	[209.20.186.192])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B2BAE43D2F; Wed, 24 Nov 2004 21:31:02 +0000 (GMT)
	(envelope-from randy@psg.com)
Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com)
	by ran.psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CX4j8-000GUq-CN; Wed, 24 Nov 2004 13:31:02 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16804.64917.872924.733444@ran.psg.com>
Date: Wed, 24 Nov 2004 13:31:01 -0800
To: Robert Watson <rwatson@freebsd.org>
References: <20041123182254.GB10721@ninthgate.net>
	<Pine.NEB.3.96L.1041124152633.98085Y-100000@fledge.watson.org>
cc: freebsd-current@freebsd.org
Subject: Re: Random panics with 5.3-REL, SMP
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Nov 2004 21:31:03 -0000

> - Using a serial console to the box, you can reliably gather information
>   without the core dump mechanism working.

i caught one, but the rest happened and reboot's beastie wiped the console

    Fatal trap 12: page fault while in kernel mode
    cpuid = 0; apic id = 00
    fault virtual address   = 0x41959c25
    fault code              = supervisor write, page not present
    instruction pointer     = 0x8:0xc04e813a
    stack pointer           = 0x10:0xe784d978
    frame pointer           = 0x10:0xe784d994
    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         = 68301 (sshd)
    trap number             = 12
    panic: page fault
    cpuid = 0
    boot() called on cpu#0
    Uptime: 9h29m10s
    Cannot dump. No dump device defined.
    Automatic reboot in 15 seconds - press a key on the console to abort
    Rebooting...
    cpu_reset called on cpu#0
    cpu_reset: Stopping other CPUs

since then, i installed a kernel with debugging symbols (blush), but
have yet to get a usable savecore and the beastie got me too.

> - "Random panics" could mean "A lot of seemingly different panics
>   happening with relatively frequency", or it might mean "A few similar
>   panics, happening at random intervals".

as i can't really characterize the causes, let's just say they seem
random to me.

i have not reported this stuff, as i had no good data.  but since
hogan whined, i thought i should sing the harmony.

randy