[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Pkg-sysvinit-devel] Bug#672959: kfreebsd-*: panic: vm_fault_copy_wired


I tried commenting out the code in checkroot.sh that remounts the rootfs
as writable after fsck is finished.  It still panics, but then the
filesystem isn't marked as dirty on next boot (because fsck succeeded,
marked it as clean, and the fs was still mounted read-only at the time
of the panic).

Adding a sleep atop of mtab.sh doesn't seem to delay the panic.  I
figure that would be the next script to run after checkroot.sh.

On 20/08/12 20:50, Steven Chamberlain wrote:
> freebsdutils is [...] free to run before, after, or at
> the same time as checkroot.sh

I've been looking into that.  freebsd-utils provides "udev" and
checkroot depends on that.  That seems to affect the ordering of
/etc/rcS.d/S* symlinks at least.

But the /etc/init.d/.depend.boot file as used by startpar, doesn't seem
to reflect that dependency at all.

Either way, I didn't manage to fix anything yet by changing the
dependencies of the initscripts around.

I can successfully boot a system with a dirty rootfs by starting a shell
instead of /sbin/init, and then:

cd /etc/rcS.d && for i in S* ; do sh "$i" start ; done

Whereas invoking this instead, would trigger the kernel panic, whether I
mount linprocfs beforehand or not:

/sbin/startpar -p 4 -t 20 -T 3 -M boot -P N -R S

And the same happens even with -p 0.  This is a single-CPU VM running

I'm beginning to think that startpar is malfunctioning in some way
(after checkroot.sh returns, but before it runs the next script).

Steven Chamberlain

Reply to: