From owner-freebsd-hackers Wed Jul 21 12:47: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 3426214C4C for ; Wed, 21 Jul 1999 12:47:00 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA57713 for ; Wed, 21 Jul 1999 15:45:20 -0400 (EDT) Message-Id: <199907211945.PAA57713@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: UDMA broken in -CURRENT/-STABLE? Date: Wed, 21 Jul 1999 15:45:20 -0400 From: "David E. Cross" 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 [...] -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message