>> Removing KDB_UNATTENDED from your kernel will allow you
>> to interact with the debugger and obtain backtraces etc,
>> which is useful when dumps are not being saved.
>
> Easier said than done, this cause a few panics - no dumps
> though ...g!!
>
> Still the same result ... the system
> John, a question, how is swap set up on your system? I was
> swapping to a file (a memory disk device /dev/md0). I was
> doing this because for some reason lost in ancient history,
> this machine was not set up with a real swap partition.
> Hence, no crash dump.
Swap is a partition on t
> Could be memory, but I'd also suggest looking at
> temperatures. I've had overheating systems produce lots of
> such errors.
Temperature is fine - it never get's that hot here in the UK ;-) Seriously, I
put my hand in the box, touched a few heat sync's, it
is not running hot enough to cause
> Can the system in question run memtest86+ successfully (no
> errors) for an hour? It would help diminish (but not
> entirely rule out) hardware (memory or chipset) issues.
Sorry, forgot to mention, I ran memtest over night without any problem
reported. I ran Fedora 9 for a month without a
I am experiencing 'random' reboots interspersed with panics whenever I put a
newly installed system under load (make index in
/usr/ports is enough). A sample panic is at the end of this email.
I have updated to 7.0-RELEASE-p2 using the GENERIC amd64 kernel and it is still
the same. The system
