Date: Wed, 14 Apr 1999 20:18:32 +0200 (CEST) From: Remy Nonnenmacher <remy@synx.com> To: asami@FreeBSD.ORG Cc: ken@plutotech.com, scsi@FreeBSD.ORG Subject: Re: timed out while idle? Message-ID: <199904141818.UAA42196@rt2.synx.com> In-Reply-To: <199904132318.QAA49274@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 Apr, Satoshi - Ports Wraith - Asami wrote: > * From: "Kenneth D. Merry" <ken@plutotech.com> > > * The timed out while idle message means that the drive took longer than the > * timeout (60 seconds) to respond to a read or write request, and nothing was > * going on on the bus at the time. In other words, your drive went out to > * lunch, and we hit it with a BDR to get it to come back. > > Wow, 60 seconds? That's indeed a pretty good lunch. :) > > * Yep. There's a timeout for each transaction. If the transaction doesn't > * complete in the specified period of time (60 seconds for disk > * reads/writes), the timeout fires, a BDR is sent and all transactions that > * were queued to the disk are requeued. > > I see. By the way, can any of these cause panics? Here's an example: > If that can serve: I got _exactly_ the same problem on one machine that was otherwise stable for months. It turned out that updating adpatec BIOS (1.23 and 1.32 to 1.34.2) and disabling auto-termination solved the problem. Unfortunetly, i can't say what of the two actions fixed this for me since i made the two at the same time. RN. IeM 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?199904141818.UAA42196>