From owner-freebsd-questions Thu Nov 12 15:53:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14069 for freebsd-questions-outgoing; Thu, 12 Nov 1998 15:53:00 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14052 for ; Thu, 12 Nov 1998 15:52:46 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id PAA15600; Thu, 12 Nov 1998 15:52:19 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 12 Nov 1998 15:52:18 -0800 (PST) From: Doug White To: Don Morrison cc: questions@FreeBSD.ORG Subject: Re: so-called "spindown" problem In-Reply-To: <3649341E.DF727B80@u.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Nov 1998, Don Morrison wrote: > During heavy disk activity, such as performing an fsck I've > run into the kernel messages: > > wd1: interrupt timeout: > wd1: status 50 error 1 > wd1: wdtimeout() DMA status 4 > > I looked at the mail archives, and noticed some suggest that > this is due to a disk spindown. My question is, how does > the disk spindown during an fsck? Maybe I'm just > completely ignorant here, but I can't see a logical reason > for it to do this under constant disk activity. Actually, it appears that the disk controller is loosing the DMA channel. Perhaps you have two devices sharing a DMA channel, like a soundcard? Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message