Date: Tue, 3 Nov 1998 17:59:20 -0800 (PST) From: perl <perl@netmug.org> To: Tom <tom@uniserve.com> Cc: stable@FreeBSD.ORG Subject: Re: has this been fixed? Message-ID: <Pine.BSF.4.02A.9811031758370.5076-100000@netmug.org> In-Reply-To: <Pine.BSF.4.02A.9811031722090.29296-100000@shell.uniserve.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
how would I go about fixing my hardware? is this caused by the drive spining down? (i'm not sure if it is or not) Thanks, Michael On Tue, 3 Nov 1998, Tom wrote: > > On Tue, 3 Nov 1998, perl wrote: > > > Hi, I was wondering if someone has changed the timeout in the wd driver so > > that > > Nov 3 17:06:17 netmug /kernel: wd2: interrupt timeout: > > Nov 3 17:06:17 netmug /kernel: wd2: status 50<rdy,seekdone> error 1<no_dam> > > is less common. > > It is hardware problem. Fix the hardware so it > responds faster, and the warning message will disapear. > > > Or is there a way to keep that from happening? What causes that error? > > An IDE timeout, right? > > You can lengthen the timeout, but this would just hide the problem. > Your drive is taking a bit too long to respond. > > > Thanks, > > > > Michael > > > > > Tom > Systems Support > Uniserve > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.02A.9811031758370.5076-100000>