Date: Wed, 1 Aug 2012 15:20:21 -0400 From: Mark Saad <nonesuch@longcount.org> To: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: How to diagnose system freezes? Message-ID: <CAMXt9NYviCBenNkmG6CUgccnLKago4XOKUzf6mxazt6T9W9QRw@mail.gmail.com> In-Reply-To: <50189F13.8020803@rawbw.com> References: <501871FD.601@rawbw.com> <50187853.7080206@freebsd.org> <B675E827-07F5-4F41-9983-1E1B1B095326@longcount.org> <50189F13.8020803@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 31, 2012 at 11:14 PM, Yuri <yuri@rawbw.com> wrote: > On 07/31/2012 17:50, Mark Saad wrote: >> >> Yuri >> Install sysutils/mcelog and try running the example included . While >> not a complete definitative hardware test it can report other hardware >> issues that memtest86+ misses and it can be run on line in multiuser mode >> and via cron . > > > Thanks for suggesting this. I have a question, however. Let's say 'mcelog > --daemon' runs and encounters some MCE and logs it. Wouldn't this record be > lost during the subsequent ungraceful (poweroff) reboot? Nonfatal MCEs, if > any, will stay but what about the fatal one? > Daemon mode does not work on FreeBSD , and on most if not all linux distros it runs via cron. In this example you can have it write the logged results via syslog and hopefully you should be able to review them. /usr/local/bin/mcelog --ignorenodev --filter --no-dmi --syslog or /usr/local/bin/mcelog --no-dmi > /var/log/mce.log Now that being said , when mcelog reports an error , it continuously reports the error, each time mcelog is run, power cycling did not clear the mcelog . -- mark saad | nonesuch@longcount.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMXt9NYviCBenNkmG6CUgccnLKago4XOKUzf6mxazt6T9W9QRw>