From owner-freebsd-current@FreeBSD.ORG Wed Aug 27 04:01:48 2003 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 4B67D16A4BF for ; Wed, 27 Aug 2003 04:01:48 -0700 (PDT) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 2DBE643F85 for ; Wed, 27 Aug 2003 04:01:47 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: (qmail 16457 invoked by uid 1002); 27 Aug 2003 11:01:45 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 27 Aug 2003 11:01:45 -0000 Message-ID: <3F4C8F9B.4090405@freebsd.org> Date: Wed, 27 Aug 2003 05:01:47 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt Dainty References: <20030827093942.GB21056@gelf.bodgit-n-scarper.com> In-Reply-To: <20030827093942.GB21056@gelf.bodgit-n-scarper.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current Subject: Re: Panic on 5.1-RELEASE with ahc 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: Wed, 27 Aug 2003 11:01:48 -0000 Hi, This is a known problem that showed up late in the 5.1 release cycle. I declined to allow the fix in as it was also somewhat disruptive. Updating to 5.1-CURRENT should make the problem go away. In any case it's fairly harmless as it happens after the disks have been synced. Scott Matt Dainty wrote: > Hi, > > I've just acquired a new Dell PowerEdge 4600 server (2x 2.4GHz Xeons, > 2GB, PERC 3/Di, ...) which I've installed FreeBSD 5.1-RELEASE on. > > All the hardware seems to be detected okay, and I've rebuilt a kernel > with unnecessary drivers removed and to take advantage of the SMP, and > this seems to be working in my limited testing so far. > > The only problem I have, (and this happened with the stock installed > kernel too ISTR) is that on shutting down, I consistently get a panic, > which after rebuilding my kernel with the debugging turned on, I have > slightly more information: > > ... > Uptime: 1m48s > NMI ISA a0, EISA ff > RAM parity error, likely hardware failure. > > Fatal trap 19: non-maskable interrupt trap while in kernel mode > cpuid = 0; lapic.id = 00000000 > instruction pointer = 0x8:0xc014cd64 > stack pointer = 0x10:0xe11eac78 > frame pointer = 0x10:0xe11eac84 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, IOPL = 0 > current process = 1 (init) > kernel: type 19 trap, code=0 > Stopped at ahc_shutdown+0x24: jmp ahc_shutdown+0x29 > db> trace > ahc_shutdown(c3b0bc00,0,c03326cd,175,32) at ahc_shutdown+0x24 > boot(0,0,c03326cd,af,e11ead40) at boot+0x6c0 > reboot(c3b17720,e11ead10,c0345860,3fb,1) at reboot+0x46 > syscall(2f,2f,2f,80a943a,bfbffdf8) at syscall+0x26e > Xint0x80_syscall() at Xint0x80_syscall+0x1d > --- syscall (55, FreeBSD ELF32, reboot), eip = 0x80507ab, esp = 0xbfbffc2c, ebp = 0xbfbffcf8 --- > db> > > This also causes the Hardware LCD display on the front to display "E13F5 > PCI SYSTEM", which I have to remove all power from the machine to clear, > although the machine appears to still work with this message displayed. > > On advice of the message regarding RAM/hardware failure, I've run all of > the Dell diagnostics to check things like the RAM, and they all pass > with no problem. > > The machine has a 39160 fitted in one of the PCI-X slots and also has > both an AIC7899 and AIC7890 onboard, the latter of which has a Quantum > SDLT320 tape drive connected. I've tried removing the 39160 and this > makes no difference. If I remove the ahc driver from my config and > rebuild, I no longer get the panic, problem is I'd like to use the tape > drive :-) > > I've included the output of "pciconf -v -l" below if that's any use, > otherwise I'm a bit green on debugging FreeBSD so if there is any more > information you want/need, please let me know how to get it. > > Cheers > > Matt