Joe Auty <[EMAIL PROTECTED]> writes:
> I guess the trick here was not considering that user space apps would
> be trying to do a kldload, and that calling upon a module that is
> either missing in /boot/kernel or /boot/modules or resides outside
> of /boot can trigger these panics.
That is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sort of...
Thanks for everybody that has helped me!
It turns out I had a couple of rc.d scripts in /usr/local/etc/rc.d
that were doing kldloads: rtc.sh and kqemu.sh - one of these was
causing the panic. It might be worthwhile adding to the world
