From nobody@FreeBSD.org  Thu Nov  3 16:22:56 2005
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 AFEB516A41F
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  3 Nov 2005 16:22:56 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5A77343D49
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  3 Nov 2005 16:22:56 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id jA3GMtNe087818
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 3 Nov 2005 16:22:55 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id jA3GMtgF087816;
	Thu, 3 Nov 2005 16:22:55 GMT
	(envelope-from nobody)
Message-Id: <200511031622.jA3GMtgF087816@www.freebsd.org>
Date: Thu, 3 Nov 2005 16:22:55 GMT
From: Eric Lo <wxluo@ntnu.edu.tw>
To: freebsd-gnats-submit@FreeBSD.org
Subject: [panic] Fatal trap 19 (process: idle: cpu0) on HP proliant DL380G3 server
X-Send-Pr-Version: www-2.3

>Number:         88459
>Category:       i386
>Synopsis:       [panic] Fatal trap 19 (process: idle: cpu0) on HP proliant DL380G3 server
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    gavin
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Nov 03 16:30:14 GMT 2005
>Closed-Date:    Fri Feb 22 19:57:21 UTC 2008
>Last-Modified:  Fri Feb 22 19:57:21 UTC 2008
>Originator:     Eric Lo
>Release:        5.4-STABLE
>Organization:
National Yang-Ming University, Taiwan, ROC
>Environment:
FreeBSD ym78116.ym.edu.tw 5.4-STABLE FreeBSD 5.4-STABLE #32: Thu Nov  3 10:30:14 CST 2005     root@ym78116.ym.edu.tw:/usr/obj/usr/src/sys/SERVER  i386

>Description:
This machine is a SMP machine with 2 Intel/P4 XEON CPUs.
In recent days, our server has occurred many kernel panic events even with very low loading.
Is it a hardware problem?
If anyone has some suggestion, it is welcome.

Hardware spec:
HP Proliant DL380G3 server
CPU: Intel P4 Xeon 3.06GHz * 2
memory: 4GB physical ECC registered memory
2 bge NIC on board
1 em NIC in PCI-X 1
6 SCSI320 HDDs with HP smartRAID config as RAID5  


the error message just as below:

Fatal trap 19: non-maskable interrupt trap while in kernel mode
cpuid = 0; apic id = 00
instruction pointer     = 0x8:0xc0b252cc
stack pointer           = 0x10:0xe7860ca8
frame pointer           = 0x10:0xe7860ca8
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, IOPL = 0
current process         = 14 (idle: cpu0)
[thread pid 14 tid 100006 ]

ps output of pid 14
root       14 99.0  0.0     0     8  ??  RL    8:20PM 218:09.25 [idle: cpu0]

Diff between GENERIC and our kernel config:

include GENERIC

ident           SMP-GENERIC

# To make an SMP kernel, the next line is needed
options         SMP                     # Symmetric MultiProcessor Kernel

device          ehci            # EHCI PCI->USB interface (USB 2.0)
device          smbus
device          smb
device          ichsmb
options         COMPAT_LINUX
options         LINPROCFS
options         LIBICONV
options         LIBMCHAIN
options         QUOTA
options         SYSVSHM
options         SYSVSEM
options         SEMMNI=256
options         SEMMNS=1024
options         SEMMAP=1024
options         SHMSEG=256
options         SHMMAXPGS=4096
options         SEMMNU=256
options         MAXDSIZ=(2048UL*1024*1024)
options         MAXSSIZ=(128UL*1024*1024)
options         DFLDSIZ=(2048UL*1024*1024)
device          snp
options         CPU_ENABLE_SSE
options         NMBCLUSTERS=65535
options         DDB
options         KDB

options         IPFILTER
options         IPFILTER_LOG

>How-To-Repeat:
kernel panic occurs about 2 or 3 times per day

>Fix:
none
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: gavin 
State-Changed-When: Tue Feb 19 17:20:56 UTC 2008 
State-Changed-Why:  
To submitter:  Firstly, I'm sorry that this PR has sat for so long without 
anyone looking at it.  Can you tell me, is this still a problem with newer 
versions of FreeBSD?  To be honest, from the sound of your report, it 
sounds like it may well be a hardware issue, especially if you had made no 
changes to the server before it started crashing. 


Responsible-Changed-From-To: freebsd-i386->gavin 
Responsible-Changed-By: gavin 
Responsible-Changed-When: Tue Feb 19 17:20:56 UTC 2008 
Responsible-Changed-Why:  
Track 

http://www.freebsd.org/cgi/query-pr.cgi?pr=88459 
State-Changed-From-To: feedback->closed 
State-Changed-By: remko 
State-Changed-When: Fri Feb 22 19:57:19 UTC 2008 
State-Changed-Why:  
Apparently this got fixed. Thanks for the feedback! Let us known in case 
it was not an hardware issue! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=88459 
>Unformatted:
