From owner-freebsd-stable Thu Mar 2 9:50:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id BE61637BD95 for ; Thu, 2 Mar 2000 09:50:26 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id SAA22002 for ; Thu, 2 Mar 2000 18:50:21 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id SAA22450 for ; Thu, 2 Mar 2000 18:50:21 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id SAA66877 for ; Thu, 2 Mar 2000 18:50:21 +0100 (CET) Date: Thu, 2 Mar 2000 18:50:19 +0100 From: Andre Albsmeier To: Brad Knowles Cc: Vivek Khera , freebsd-stable@FreeBSD.ORG Subject: Re: Crash on boot when disks are present? Message-ID: <20000302185019.B20215@internal> References: <14526.37497.981697.452892@onceler.kcilink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from blk@skynet.be on Thu, Mar 02, 2000 at 05:22:51PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Don't remeber if my other reply went to Brad also or only to the list... ] On Thu, 02-Mar-2000 at 17:22:51 +0100, Brad Knowles wrote: > At 11:10 AM -0500 2000/3/2, Vivek Khera wrote: > > > There are anecdotal reports of other external SCSI drives causing such > > errors at boot on BSD/OS as well. The solution is to power up with > > the drive off, and turn it on once the boot is started, or something > > silly like that. > > But why is it a problem now, when it wasn't a problem earlier > this week? Could a simple firmware upgrade of the controller on the > drive array really cause problems that severe? Yes. See PR #16803. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message