From owner-freebsd-scsi Fri Mar 5 13:49:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (Postfix) with ESMTP id 1C58314C35 for ; Fri, 5 Mar 1999 13:49:07 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.8.8/Debian/GNU) with ESMTP id WAA28280 for ; Fri, 5 Mar 1999 22:48:49 +0100 Date: Fri, 5 Mar 1999 22:48:48 +0100 (CET) From: N X-Sender: niels@liquid.tpb.net To: freebsd-scsi@FreeBSD.ORG Subject: Re: 2940U2W supported? In-Reply-To: Message-ID: <9903052245550.28252-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 5 Mar 1999, Matt Simerson wrote: >> "waiting for SCSI devices to settle" during boot (I'd guess >> it happens at every 10th reboot or something like that). >> This happens both with the Adaptec 2940-U2W and with the >> onboard Adaptec U2W of an ASUS P2B-LS, using 3.1-RELEASE. > I can confirm this behavior. Me too (3.0-CURRENT dating back to January, doing fine until then, and afterwards too. P2B-LS, with another 2940U2W card in a PCI slot. Only LVD devices on the two SCSI buses; one IDE disk.) >> It's extremely annoying, because you cannot reboot such a >> machine remotely and be sure that it comes up again. :-( >> It renders the Adaptec controllers essentially unusable for >> production use. > Why do you have to reboot production servers? Because this particular one crashed. Had to send someone out to lean on the reset button, which worked. -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message