From owner-freebsd-stable Tue Nov 3 18:00:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25773 for freebsd-stable-outgoing; Tue, 3 Nov 1998 18:00:19 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netmug.org (netmug.org [207.88.43.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25768 for ; Tue, 3 Nov 1998 18:00:18 -0800 (PST) (envelope-from perl@netmug.org) Received: from localhost (perl@localhost) by netmug.org (8.8.8/NetMUG_1.0.0) with SMTP id RAA05170; Tue, 3 Nov 1998 17:59:20 -0800 (PST) Date: Tue, 3 Nov 1998 17:59:20 -0800 (PST) From: perl To: Tom cc: stable@FreeBSD.ORG Subject: Re: has this been fixed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 error 1 > > 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