From owner-freebsd-stable Tue Nov 3 17:24:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21680 for freebsd-stable-outgoing; Tue, 3 Nov 1998 17:24:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA21675 for ; Tue, 3 Nov 1998 17:24:53 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zargb-0000nf-00; Tue, 3 Nov 1998 17:24:37 -0800 Date: Tue, 3 Nov 1998 17:24:34 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: perl 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 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