From owner-freebsd-current Fri Oct 1 6:45:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1]) by hub.freebsd.org (Postfix) with ESMTP id 5F8B61504F for ; Fri, 1 Oct 1999 06:45:14 -0700 (PDT) (envelope-from lh@aus.org) Received: from PHOENIX.ZER0.NET (lh@ZER0.NET [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id JAA00826; Fri, 1 Oct 1999 09:45:04 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910010628.IAA62851@freebsd.dk> Date: Fri, 01 Oct 1999 09:45:03 -0400 (EDT) From: Luke To: Soren Schmidt Subject: Re: ata driver (again) Cc: freebsd-current@FreeBSD.ORG, (Kenneth Wayne Culver) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A dmesg to start with would be fine that way I may be able to reproduce > it here pn semilar HW. wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-16, sleep-hack wd0: 8693MB (17803440 sectors), 1108 cyls, 255 heads, 63 S/T, 512 B/S (sleep-hack I turned on last night) >> > /kernel: wd0: wdtimeout() DMA status 4 > Thats not the ata driver thats the wd driver :) > Looks like interrupt lossage to me... > yes it is, it happens to me with either driver. I keep suspecting it is something other than the disk or OS , like the motherboard or something but I have no idea how to find out. Thanks Luke --------------------------------------------------- To be sure of hitting the target, shoot first and, whatever you hit, call it the target. XFMail 1.3 FreeBSD-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message