From owner-freebsd-current@FreeBSD.ORG Tue Feb 17 07:34:14 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 5D63016A4CF for ; Tue, 17 Feb 2004 07:34:14 -0800 (PST) Received: from lorax.ldc.upenn.edu (lorax.ldc.upenn.edu [158.130.16.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46A0143D2D for ; Tue, 17 Feb 2004 07:34:14 -0800 (PST) (envelope-from fuzz@ldc.upenn.edu) Received: by lorax.ldc.upenn.edu (Postfix, from userid 32822) id 92C0122852; Tue, 17 Feb 2004 10:34:13 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by lorax.ldc.upenn.edu (Postfix) with ESMTP id 7CABC22831; Tue, 17 Feb 2004 10:34:13 -0500 (EST) Date: Tue, 17 Feb 2004 10:34:13 -0500 (EST) From: "Jason M. Leonard" To: Raphael.Becker@gmx.de Message-ID: <20040217102453.V59439@lorax.ldc.upenn.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org 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:34:14 -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 Without seeing the actual SCSI errors it is hard to say, but I was experiencing a very similar issue with my PE2650. Disabling write caching on the RAID 1 container cleared it up. I do not know if that is the best way to go about it, but this server had to be in production pronto, so I was happy. :Fuzz