[260] in netbsd-help mailing list archive
Re: partition error
daemon@ATHENA.MIT.EDU (Greg Hudson)
Sun Jul 16 13:38:33 1995
To: Kenneth K Pang <kennethp@MIT.EDU>
Cc: netbsd-help@MIT.EDU
In-Reply-To: Your message of "Sun, 16 Jul 1995 00:01:41 EDT."
<9507160401.AA27174@venus.MIT.EDU>
Date: Sun, 16 Jul 1995 13:39:15 EDT
From: Greg Hudson <ghudson@MIT.EDU>
> I tried using both nfsaha.fs and nfsbt.fs and they both fail the
> same way. Some errors like "Lost Contact : status 0 error 0" were
> displayed. A dos partition error is also displayed before it
> locates the netbsd partition.
I'm afraid I'm not sure what this error means. I couldn't find the
mssage in the fdisk sources, or in the wd driver in the kernel (the wd
driver is the driver for IDE disks). I found some error messages in
the wd driver which fit the general scheme (printing out "status" and
"error"), and the closest one is "lost interrupt", whicih happens if
NetBSD makes a disk query and doesn't get an interrupt from the wd
driver within a certain interval.
If the error you got was "lost interrupt," then you may have an IRQ
conflict between your disk controller and some other peripheral in
your machine. When your system boots, look for a line during the
autoprobe messages like:
wdc0 at isa0 port 0x1f0-0x1f7 irq 14
Then see if there are any other autoprobes using the same IRQ as wdc0;
if there aren't, check other devices in your machine (sound cards,
etc..) which might be using the same IRQ.
I think normally the WD controller uses IRQ 14, and other devices
won't use it because of that, but there might still be a conflict. If
there isn't a conflict, then there's something funny about your disk
or your wd controller that NetBSD doesn't like. In that case, you
might be able to arrange to bring your machine into the SIPB office at
a time when Charles Hannum (the i386 port maintainer for NetBSD) can
look at it. Other than that, I don't know of any workarounds (apart
from using the SCSI disk instead of the IDE disk for NetBSD).
