problems with -current
Robert C. Noland III
rnoland at 2hip.net
Tue Nov 29 20:01:11 GMT 2005
On Tue, 2005-11-29 at 10:37 -0800, Maksim Yevmenkin wrote:
> problem 2: when system is booted and filesystem is not clean fsck is
> started and checks all dirty filesystems. then boot process continues
> as
> usual, however root filesystem is still mounted read-only, i.e.
>
> ---> /dev/ad0s1a on / (ufs, local, read-only) <---
> devfs on /dev (devfs, local)
> /dev/ad0s1d on /tmp (ufs, local, soft-updates)
> /dev/ad0s1f on /usr (ufs, local, soft-updates)
> /dev/ad0s1e on /var (ufs, local, soft-updates)
> linprocfs on /usr/compat/linux/proc (linprocfs, local)
> devfs on /var/named/dev (devfs, local)
>
> so, anyone sees this as well or its just me.
I have also seen this issue. The machine in question wasn't running X.
I am not convinced that the panics (trap 12: page faults) were not
somehow hardware related, but the results after the panics were as you
described.
robert.
More information about the freebsd-current
mailing list