Um.. where is dmesg?
On 11/09/06, Jeff Bromberger <[EMAIL PROTECTED]> wrote:
I have a dual core Opteron system that I'm trying to make into a mail server
for my company to replace a 7 year old Linux box that's on its last leg. I
started off using the 3.9 release of the amd64 system and ran into a few
problems (keyboard and cdrom didn't work). It was suggested that I move to
the latest snapshot, which I did about a week ago. That fixed the keyboard
and cdrom problems, so I began configuring the box. I am only running a few
packages on this machine: courier imap, postfix, fetchmail, procmail. In
the past 2-3 days (which is how long the box has actually been active, i.e.
running all the daemons and having mail clients connect to it) I have
experienced two kernel panics. I thought that the info from the panic would
show up in the dmesg after rebooting, but that data seems to have been
corrupted. I could only see bits and pieces of the kernel debugger message
from the first panic. This time around, I'm still sitting in the kernel
debugger so I am able to run a few commands if anybody has any specific
requests.
Trace shows:
panic() at panic+0x12a
amap_wipeout() at amap_wipeout+0x71
uvm_unmap_detach() at uvm_unmap_detach+0x9b
sys_munmap() at sys_munmap+0x145
syscall() at syscall+0x25c
--- syscall (number 73) ---
"ps" shows the active process was imapd.
I am running the bsd.mp kernel from the amd64 snapshot.
To ask a different question, for the hardware that I have, what would be the
most stable port/version that I could run? Am I better off going with the
3.9 release of the i386 code vs. the current snapshot of the amd64 stuff?
My top priorities for this box are stability first and then security second,
performance is a distant third since it's just a mail server for a small
company.
Thanks,
Jeff
