August 2007 Archives
Paraphrased from a recent discussion, saving this off in case it is useful to myself or anyone else looking.
If the FreeBSD kernel crashes pretty reliably, ie if you boot with hardware it doesn't like, you can try and catch the function pointer address where the panic happens. From there, you can cross reference it back to what function in the kernel it is, using these ideas, in order from worst to best:
- Use a released generic kernel, post asking for help, include uname -a output.
- nm /boot/kernel/kernel and search for a function symbol close to the address you crashed at
- objdump -d /boot/kernel/kernel and search..
- Best is to break to debugger if possible, and get a stack trace, check the freebsd handbook.
Folks, I'm making a "notify" mailing list -- I'll be using that to communicate the status of the server upgrade and such. I also intend to keep the web site up to date with that regard, so if you're reading this via web or RSS, you're find. However, if you're not, and I haven't subscribed you to the notify mailing list, you can subscribe at http://gigo.com/mailman/listinfo/notify.
If you maintain an "aliases" file on gigo.com for one or more of your domains, please note the following changes are being made:
