Subject: Re: -current does not like non-boot disk
To: Christos Zoulas <christos@zoulas.com>
From: Allen Briggs <briggs@canolog.ninthwonder.com>
List: port-mac68k
Date: 12/14/1998 10:48:42
> The only panic in fstat it when the file is not a vnode or a socket...
> What the hell is it then?
In my case, it was zero. I think that something is getting corrupted on
access to the second disk. If I have a kernel that is doing this, I get
a panic during fsck if I forget to boot single-user. I have root on
sd0a and /u on sd1g. When I boot, I get (from memory):
/dev/sd0a: filesystem clean; not checking (or whatever)
NO WRITE ACCESS
/dev/sd1g: unexpected inconsistency; run fsck(8) by hand (or whatever)
panic: uvm_fault...
When using the first disk, though, everything seems to be OK. I haven't
beat on it too heavily, but it seems to be OK until I touch the second
disk... (although the probe doesn't seem to affect anything--at least
nothing serious)
I'm using the esp driver (dev/ic/ncr53c9x.c and arch/mac68k/obio/esp.c)
on the 68040 processor, but it sounds like this is also happening with
the sbc (5380) driver on a 68030 processor.
-allen
--
Allen Briggs - briggs@ninthwonder.com
Try free *nix: http://www.netbsd.org/, http://www.freebsd.org/,
http://www.linux.org/, http://www.openbsd.org/