Date: Wed, 10 Apr 2002 14:41:05 -0600 From: "Kenneth D. Merry" <ken@kdm.org> To: Shawn Walker <shawn@eblend.org> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Bus Error Message-ID: <20020410144105.A31326@panzer.kdm.org> In-Reply-To: <B8D8D450.6513%shawn@eblend.org>; from shawn@eblend.org on Tue, Apr 09, 2002 at 05:24:32PM -0400 References: <B8D8D450.6513%shawn@eblend.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 09, 2002 at 17:24:32 -0400, Shawn Walker wrote: > Hi, > > I have been having a problem with a server that is currently > running FreeBSD 4.1. Last night the box locked up with the following error > messages appearing on the console: > > (da0:ahc0:0:1:0): SCB 0x49 - timed out while idle. > (da0:ahc0:0:1:0): SEQADDR=0x9 > (da0:ahc0:0:1:0): Queuing a BDR SCB > (da0:ahc0:0:1:0): no longer in timeout, status = 34a > > About one month ago, it locked up with the same error messages. The > controller is an Adaptec aic7896/97 Ultra2. Any ideas? I am not sure if > this is a driver error that could be solved with an upgrade or the sign of > some impending hardware fault. Typically a "timed out while idle" error means that the drive went out to lunch and never came back. In the case of the da(4) driver, it means the drive didn't come back after 60 seconds. What sort of drive is this (dmesg would work)? You can try upgrading to a newer -stable, but there are no guarantees that that would fix your problem. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020410144105.A31326>