From owner-freebsd-hackers Thu Jul 22 6:52:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 547441522C for ; Thu, 22 Jul 1999 06:52:53 -0700 (PDT) (envelope-from kbyanc@alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from kbyanc (ws-41.alcnet.com [63.69.28.41]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id KAA11856; Thu, 22 Jul 1999 10:08:02 -0400 (EDT) From: "Kelly Yancey" To: Cc: Subject: Re: UDMA broken in -CURRENT/-STABLE? Date: Thu, 22 Jul 1999 10:04:30 -0400 Message-ID: <003a01bed44b$1dfce020$291c453f@kbyanc.alcnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I updated a system to -CURRENT last night and got a panic with alot of > messages about UDMA failing (I don't have the exact messages, I can get > them if need be). I backed down the wdc0/wdc1 controller flags from > 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that > is to be expected. > > I updated another system to -STABLE as of earlier today, and I got the same > thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a > champ. > > The messages came right after init(8) started, and before any of the > filesystems were mounted r/w (it happened most during the fsck). > > I hope someone else has seen this (sorry I am so skimpy on the details, I > will be able to provide more soonish.) > > uname -a: > FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 root@phoenix.cs.rpi.edu:/usr/src/sys/compile/PHOENIX i386 > > dmesg: > [...] > ide_pci0: rev 0x00 on pci0.7.1 > [...] I've seen the exact same problem on -stable builds since the 20th (I don't know how much further back it went than that). I'm not in front of my computer right now, but the errors were all DMA errors (status as I recall). I have a PIIX4 controller. I played around with it a bit and found that simply turning of the DMA hint in the flags cleared the problems (my flags went from f0fff0ff to d0ffd0ff I believe). Actually, once I accidentilly left the flags with DMA enabled on only 1 drive and only received DMA errons on that single drive. I don't know if this is related, but my atapi CD (Acer 40x) still reports DMA (apparently not affected by the wdc flags), but won't play audio CDs from most CD apps (apparently the ones which use the CDIOCPLAYWMF ioctl to play audio). This has been going on for longer, but I don't know if it was maybe a precursor to the UDMA bug? Kelly ~kbyanc@posi.net~ FreeBSD - The Power To Serve - http://www.freebsd.org/ Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message