From owner-freebsd-current@FreeBSD.ORG Tue Feb 17 07:02:48 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 8D45D16A4D0 for ; Tue, 17 Feb 2004 07:02:48 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 61BDB43D2D for ; Tue, 17 Feb 2004 07:02:48 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 83548 invoked by uid 1002); 17 Feb 2004 15:02:45 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 17 Feb 2004 15:02:45 -0000 Message-ID: <40322C72.7080008@freebsd.org> Date: Tue, 17 Feb 2004 08:00:02 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Raphael H. Becker" References: <20040217060844.GA74711@local.net> In-Reply-To: <20040217060844.GA74711@local.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD Current Subject: Re: kernel panic after 5.2 RELEASE --> 5.2.1, DELL PE2650, SCSI 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: Tue, 17 Feb 2004 15:02:48 -0000 Raphael H. Becker wrote: > Hi, > > yesterday I got a new DELL PE2650 with PERC and two RAIDs (complete > dmesg [1]). > Installed with 5.2 from "miniinst.iso" and updated with fresh sources > from CVS, -r RELENG_5_2. buildworld and buildkernel went fine. Just > after reboot with the new kernel and after "installworld" the system > died with some strange SCSI-Errors, kernel panic. "Calling boot() for > CPU1 ... " something like that. Then the well known few lines, syncing > disc etc ... > While syncing disks there were some more SCSI-Errors, Timeout after ... > 75 ... 255 ... seconds and so on, no more acting drives. > > I powercycled after 7 minutes, the console was messed up with the > scsi-errors, so I have no more details about the panic, powercycle > flushed the dmesg .oO(why not dumping kernelmessages to an USB-stick??) > > System rebootet, but with a nearly empty /usr/sbin. > Retry of "make installworld" failed, because it wants to copy some tools > in an temporary dir in /tmp and didn't find some tools in /usr/sbin. > Managed that manually, installworld succeeded. > > > Kernel ist a GENERIC with only > -cpu I486_CPU > -cpu I586_CPU > +#cpu I486_CPU > +#cpu I586_CPU > ( BTW: has anyone a perfect DELL PE2650 kernelconfig for 5.x? ) > > Anyone some hints about the panic? > How to avoid this? > > Regards, > Raphael Becker > > PS: The actual dmesg.boot: > [1] http://rhb.uugrn.org/temp/dmesg.boot.pinserv4 > Hi, Is there any way that you could hook up a serial console to the machine and record what the SCSI errors are? Without any specific information, it's hard to diagnose the problem. That said, there is a known problem with the raid controller driver for that machine that can cause lost i/o, though that doesn't sound like something that is affecting you. This particular bug will be fixed in 5.2.1. Scott