Date: Wed, 11 Oct 1995 23:55:02 -0700 (PDT) From: Morgan Davis <root@io.cts.com> To: freebsd-current@FreeBSD.org Subject: Re: Major problem with IDE hard drive and current Message-ID: <199510120655.XAA16122@io.cts.com> In-Reply-To: <199509130916.TAA00257@godzilla.zeta.org.au> from "Bruce Evans" at Sep 13, 95 07:16:41 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce, I saved this message in my mailbox now until I had some time to get back into debugging this. Before I get started, though, I was wondering if over the last month if anything has been done to address this problem. I've been hesitant to sup -current ever since the last attempt failed to see my drives at bootup. BTW, the Conner drives in my machine are very new (like less than 1 year old). And using the onboard IDE controller on my motherboard works fine with them. The caching IDE controller I'm now using for some performance advantages is the culprit, I'm sure. So I don't think the trouble is with the drives themselves, but in communicating with them through the caching IDE controller card. We already determined that the status result on resetting the card is returning an unexepected bit. I'll bet other operations are hampered in the same way, causing the problems I describe below. --Morgan Bruce Evans writes: > > >> It is probably a drive problem. What drives do both of you have? > > >I suppose. But why would these same drives not have the problem in > >previous versions of FreeBSD (going back to 2.0 for me)? > > Because the cdrom code changed the test. > > >You know, I recall the boot display showing the name of the hard > >drives before, so I was just going to suck in the relevant output from > >dmesg. And lo: > > >wdreset: du->dk_status: 0x52 > >wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa > >wdc0: unit 0 (wd0): <> > >wd0: size unknown, using BIOS values > > This shows that the WDCC_READP command failed. It shouldn't fail for > any standard IDE drive, especially a modern one that supports all those > flags. > > >The drives are both Conners, but I'm not sure of the exact model > >number (without resorting to opening the case ... only if you insist.) > > It's probably not important. But please find out why WDCC_READP is > failing. (Call wderror() in wdgetctlr(). The only normal error is > "abort" which means that the drive doesn't support the command.) > > Bruce >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510120655.XAA16122>