Date: Tue, 1 Apr 2008 12:51:19 -0400 From: Bill Moran <wmoran@potentialtech.com> To: "n j" <nino80@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD crashes Message-ID: <20080401125119.f66c3e38.wmoran@potentialtech.com> In-Reply-To: <92bcbda50804010852s20e5d681y9d2d2a4cd9e9adea@mail.gmail.com> References: <92bcbda50804010613p3cd927e4g4a3c3c7820a6a06e@mail.gmail.com> <002e01c893fd$2bb5e8d0$3202a8c0@glattwerk.local> <92bcbda50804010852s20e5d681y9d2d2a4cd9e9adea@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In response to "n j" <nino80@gmail.com>: > > I hope someone can help me. I have started to experience > > seemingly random crashes causing FreeBSD to shutdown and > > power off the machine. The only trace I can find as far as > > the reason for the crash is concerned are the following > > excerpts from /var/log/messages: > > > > Mar 23 11:52:36 myhostname kernel: <<22>N>NMIMN NIMIMII IISISSSAAA > > A 20,22 200E,0,I, S EIEEASI ISAAS f Aff ff > > Mar 23 11:52:36 myhostname kernel: f > > Mar 23 11:52:36 myhostname kernel: > > Mar 23 11:52:36 myhostname kernel: f< > > Mar 23 11:52:36 myhostname kernel: 2<>2> > > Mar 23 11:52:36 myhostname kernel: f > > Mar 23 11:52:36 myhostname kernel: > > Mar 23 11:52:47 myhostname syslogd: exiting on signal 15 > > Mar 23 13:04:32 myhostname syslogd: kernel boot file is > > /boot/kernel/kernel > > Small update: I have received some feedback that this seemingly random > junk is related to ipfw > (http://www.freebsd.org/cgi/query-pr.cgi?pr=116458). > > However, I have also received information that this junk might not be > completely random and could be, in fact, related to NMI (non-maskable > interrupt) which would suggest hardware error. Any thoughts on this? I suspect you're going to have to get crash dumps in order to get any real answers: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Based purely on the symptom that the crashes started occurring unrelated to any other activity, I would guess that you've got a hardware issue. Have you tried running things like cpuburn and memtest to see if you can reproduce it? -- Bill Moran http://www.potentialtech.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080401125119.f66c3e38.wmoran>