From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 1 19:20:28 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 720DF106566C for ; Wed, 1 Aug 2012 19:20:28 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 26B318FC14 for ; Wed, 1 Aug 2012 19:20:27 +0000 (UTC) Received: by vbmv11 with SMTP id v11so1366464vbm.13 for ; Wed, 01 Aug 2012 12:20:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=vjilbEBnuYXttoUqKCsGXMWotFd9LFS24zaI1qQKwfg=; b=mt6zXZrvslur6OMvUDEk0k6S8baqCUnL53JktHOJzX1hQdtS53A5Mdc6XeuSERVYZH uRGLo7z11pJ46L6WCCH1CNIvcb/P4kAFKsBecqd0b8EDlo2KaSJrP64M1UlZ1ERqcd+w UJJiaDAH/KnAm8BGFFwyeWnd7aKuowYvC/Qao8uFEpHTRdvbrIZUuYTdEB3IEXuNJ25R t8ffDafL6BFdK8Zrq2IPCxx2ugAfqK7h2QQWU37WuRjJGDlDOhE9AkgMeeuAqAMHRPTO MWgF5Qb4WpdWDYXKRpr7f8QBM1R+Ic6h+yRGJOAP4uNpebKzlSxQzsIaHg9EGECOIlfK L0fw== MIME-Version: 1.0 Received: by 10.52.22.50 with SMTP id a18mr15699555vdf.60.1343848821155; Wed, 01 Aug 2012 12:20:21 -0700 (PDT) Received: by 10.58.171.6 with HTTP; Wed, 1 Aug 2012 12:20:21 -0700 (PDT) X-Originating-IP: [209.66.78.50] In-Reply-To: <50189F13.8020803@rawbw.com> References: <501871FD.601@rawbw.com> <50187853.7080206@freebsd.org> <50189F13.8020803@rawbw.com> Date: Wed, 1 Aug 2012 15:20:21 -0400 Message-ID: From: Mark Saad To: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnMUKcsKpIcTvJHkCyQOb9BckivTbFC4CdAtw7FPKjaH82ihOVXVPuoIElbAC7jlGwt6XmD Subject: Re: How to diagnose system freezes? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Aug 2012 19:20:28 -0000 On Tue, Jul 31, 2012 at 11:14 PM, Yuri 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