18 messages in org.freebsd.freebsd-hackerskernel panic at boot on any 6.x OS| 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 | |
|---|---|---|
| From: | Peter Jeremy (pete...@optushome.com.au) | |
| Date: | Feb 27, 2007 4:33:09 am | |
| List: | org.freebsd.freebsd-hackers | |
On 2007-Feb-26 17:38:10 -0500, Joe Auty <jo...@netmusician.org> wrote:
My system does boot off of disc 1 of the FreeBSD 6.2 CD.
That's a good start. Together with your memtest results, it suggests that your hardware is OK.
However, even when copying the /boot directory from the CD to my machine, it still produces the same kernel panic, even when starting in safe mode.
Can you confirm that you have either deleted or renamed /boot before replacing it with files from the CD. An out-of-sync module does sound the most likely problem. If that doesn't help, please start DDB and get a backtrace.
I've run a memtest, and it checked out fine.
Note that memtest cannot prove that your system doesn't have a problem. There are far too many states that your system could potentially be in. DRAM is especially susceptable to pattern- dependent and temporal glitches.
There must be something in my user space or world that it barfs on. I guess I will try a clean install and rebuild at some point...
If you're not sure where this is being triggered, you could try adding 'rc_debug="YES"' to your rc.conf (or even a 'set -x' if you are getting really desperate). This will make the boot sequence far more verbose.
-- Peter Jeremy