Date: Tue, 27 Feb 2007 01:28:07 -0500 From: Joe Auty <joe@netmusician.org> To: FreeBSD Questions <freebsd-questions@freebsd.org>, freebsd-hackers@freebsd.org Subject: Re: kernel panic at boot on any 6.x OS *SOLVED!* Message-ID: <07E8C3BD-8764-488B-8CD7-D8A106D922C1@netmusician.org> In-Reply-To: <20070227043324.GX844@turion.vk2pj.dyndns.org> References: <39E24107-964D-414C-95D1-5B1C376291E4@netmusician.org> <001001c759a6$438d5ed0$3c01a8c0@coolf89ea26645> <73B261EE-79C5-4773-B563-9D9FCA16B4C8@netmusician.org> <20070227043324.GX844@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07E8C3BD-8764-488B-8CD7-D8A106D922C1>