From owner-freebsd-stable Tue Nov 3 18:35:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00339 for freebsd-stable-outgoing; Tue, 3 Nov 1998 18:35:34 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00334 for ; Tue, 3 Nov 1998 18:35:31 -0800 (PST) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.9.1/8.9.1) id KAA24822; Wed, 4 Nov 1998 10:34:52 +0800 (GMT) Date: Wed, 4 Nov 1998 10:34:52 +0800 (GMT) From: Michael Robinson Message-Id: <199811040234.KAA24822@public.bta.net.cn> To: perl@netmug.org, tom@uniserve.com Subject: Re: has this been fixed? Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom writes: > 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. Just out of curiousity, how did the threshold for "a bit too long" get determined? Is this defined in the IDE standard? Did someone conduct a comprehensive survey of popular drives under various error-recovery modes? Did the driver writer just pull a number out of the air? -Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message