| From | Sent On | Attachments |
|---|---|---|
| Joe Auty | Feb 25, 2007 7:55 am | |
| Kip Macy | Feb 25, 2007 7:59 am | |
| Daan Vreeken [PA4DAN] | Feb 25, 2007 11:03 am | |
| Joe Auty | Feb 25, 2007 4:15 pm | |
| Joe Auty | Feb 25, 2007 4:16 pm | |
| Joe Auty | Feb 25, 2007 4:17 pm | |
| Ted Mittelstaedt | Feb 26, 2007 5:35 am | |
| Joe Auty | Feb 26, 2007 6:40 am | |
| Ted Mittelstaedt | Feb 26, 2007 2:13 pm | |
| Mike Meyer | Feb 26, 2007 4:35 pm | |
| Joe Auty | Feb 26, 2007 6:01 pm | |
| Joe Auty | Feb 26, 2007 10:38 pm | |
| Kip Macy | Feb 27, 2007 2:51 am | |
| Peter Jeremy | Feb 27, 2007 4:33 am | |
| Joe Auty | Feb 27, 2007 4:45 am | |
| Joe Auty | Feb 27, 2007 6:28 am | |
| Ted Mittelstaedt | Feb 27, 2007 1:06 pm | |
| Ted Mittelstaedt | Feb 27, 2007 1:07 pm |
| Subject: | kernel panic at boot on any 6.x OS *SOLVED!* | |
|---|---|---|
| From: | Joe Auty (jo...@netmusician.org) | |
| Date: | Feb 27, 2007 6:28:10 am | |
| List: | org.freebsd.freebsd-hackers | |
-----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-----





