From owner-freebsd-stable  Wed Oct 28 17:58:25 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA09335
          for freebsd-stable-outgoing; Wed, 28 Oct 1998 17:58:25 -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 RAA09321
          for <stable@FreeBSD.ORG>; Wed, 28 Oct 1998 17:58:18 -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 JAA20221;
	Thu, 29 Oct 1998 09:57:17 +0800 (GMT)
Date: Thu, 29 Oct 1998 09:57:17 +0800 (GMT)
From: Michael Robinson <robinson@public.bta.net.cn>
Message-Id: <199810290157.JAA20221@public.bta.net.cn>
To: logix@foobar.franken.de, stable@FreeBSD.ORG
Subject: Re: HD problems
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Harold Gutch <logix@foobar.franken.de>:
>but then I got the following errormessages:
>
>	** Phase 5 - Check Cyl Groups
>	wd1: interrupt timeout:
>	wd1: status 58<rdy,seekdone,drq> error 0
>	wd1: interrupt timeout:
>	wd1: status 50<rdy,seekdone> error 1<no_dam>
>
>	the last 4 lines being repeated every 30s or so.

This is a known deficiency in the wd driver.  Check the mailing list
archives for this error message.  There was discussion a few months ago 
about how to increase the interrupt timeout in the driver code to give the
disk enough time to report a read error.

	-Michael Robinson


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message