Re: kernel panic at boot on any 6.x OS *SOLVED!*
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 because they are *not* user-space applications. They are kernel-space code. There is a PORTS_MODULES variable documented for make.conf(5) which is intended for just this problem. I haven't used it, though, and offhand I can't find the macro definition for it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic at boot on any 6.x OS *SOLVED!*
-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 rebuild doc a suggestion to grep kldload /usr/local/etc/rc.d and disable/ remove these services... Or, simply moving /usr/local/etc/rc.d might also be worthwhile test. 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. Always the most simple of solutions that kicks you in the ass, isn't it? =) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFF4894CgdfeCwsL5ERAlvfAKCiLEGZMTsGonn0OrdlTTMCp9GeZACePQ2V WCwXuHBFh/FOVsDJLa84Yks= =85PR -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]