From nobody@FreeBSD.org  Mon Sep 16 05:28:33 2002
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1D85C37B400
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 16 Sep 2002 05:28:33 -0700 (PDT)
Received: from www.freebsd.org (www.FreeBSD.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D730C43E65
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 16 Sep 2002 05:28:32 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.4/8.12.4) with ESMTP id g8GCSWOT016216
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 16 Sep 2002 05:28:32 -0700 (PDT)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.4/8.12.4/Submit) id g8GCSWxo016215;
	Mon, 16 Sep 2002 05:28:32 -0700 (PDT)
Message-Id: <200209161228.g8GCSWxo016215@www.freebsd.org>
Date: Mon, 16 Sep 2002 05:28:32 -0700 (PDT)
From: Gary <gary@outloud.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Random Coredumps
X-Send-Pr-Version: www-1.0

>Number:         42836
>Category:       kern
>Synopsis:       Random Coredumps
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep 16 05:30:02 PDT 2002
>Closed-Date:    Fri Sep 20 10:00:12 PDT 2002
>Last-Modified:  Fri Sep 20 13:00:11 PDT 2002
>Originator:     Gary
>Release:        4.6-STABLE and a 4.7-PR
>Organization:
>Environment:
>Description:
I've been experiencing random panics with different programs. This one, recently was bash. I'm using multi-CPU machines and this has been happening on them lately.

Fatal trap 12: page fault while in kernel mode
mp_lock = 00000002; cpuid = 0; lapic.id = 00000000
fault virtual address   = 0x0
fault code              = supervisor write, page not present
instruction pointer     = 0x8:0xc03876b3
stack pointer           = 0x10:0xff390bdc
frame pointer           = 0x10:0xff390c08
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         = 342 (bash)
interrupt mask          = none <- SMP: XXX
trap number             = 12
panic: page fault
mp_lock = 00000002; cpuid = 0; lapic.id = 00000000
boot() called on cpu#0

>How-To-Repeat:
Unknown.

>Fix:
Deinstall 4.x and down-install to freebsd 3.2 :-)

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: schweikh 
State-Changed-When: Fri Sep 20 09:54:06 PDT 2002 
State-Changed-Why:  
Random coredumps and panics in -STABLE are almost certainly due to 
marginal hardware. Very often it is bad RAM. Try a memory tester such as 
memtest86, http://www.memtest86.com/ If that shows RAM is good, replace 
your disks, then other components until you have a stable system. If the 
problem persist, open a new report with much more debug info. See the 
handbook on how to enable crashdumps and getting a stack trace. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=42836 

From: Gary Stanley <gary@outloud.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/42836: Random Coredumps
Date: Fri, 20 Sep 2002 15:55:10 -0400

 The coredumping were a result of manually setting the sendfile() buffers in 
 the kernel. I removed the kernel option and let the system autotune the 
 parameter, and I've not witnessed any more crashes/panics since.
 
 Maybe a LINT entry about manually setting it to a high number, would deter 
 others from submitting anymore bogus PR's ;-)
 
 
 
 
 
 
>Unformatted:
