mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vikas Kedia" <kedia.vikas@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Can we ignore errors in mcelog if the server is running fine
Date: Thu, 27 Jul 2006 04:11:47 -0700	[thread overview]
Message-ID: <fbe022af0607270411u78ad633m650063061ea6bd5@mail.gmail.com> (raw)

The server seems to be running fine. A. can I ignore the following
mcelog errors ? B. If not what should i do to stop the server from
reporting mcelog errors.

root@srv3:~# less /var/log/mcelog
MCE 0
CPU 0 0 data cache TSC 997fa760e9
ADDR 2c13340
  Data cache ECC error (syndrome e3)
       bit46 = corrected ecc error
  bus error 'local node origin, request didn't time out
      data read mem transaction
      memory access, level generic'
STATUS 9471c00000000833 MCGSTATUS 0
MCE 0
CPU 0 0 data cache TSC 1afa02913ab
ADDR 2c13380
  Data cache ECC error (syndrome e3)
       bit46 = corrected ecc error
       bit62 = error overflow (multiple errors)
  bus error 'local node origin, request didn't time out
      data read mem transaction
      memory access, level generic'
STATUS d471c00000000833 MCGSTATUS 0
root@srv3:~# pwd
/root
root@srv3:~# less /var/log/mcelog
MCE 0
CPU 0 0 data cache TSC 997fa760e9
ADDR 2c13340
  Data cache ECC error (syndrome e3)
       bit46 = corrected ecc error
  bus error 'local node origin, request didn't time out
      data read mem transaction
      memory access, level generic'
STATUS 9471c00000000833 MCGSTATUS 0
MCE 0
CPU 0 0 data cache TSC 1afa02913ab
ADDR 2c13380
  Data cache ECC error (syndrome e3)
       bit46 = corrected ecc error
       bit62 = error overflow (multiple errors)
  bus error 'local node origin, request didn't time out
      data read mem transaction
      memory access, level generic'
STATUS d471c00000000833 MCGSTATUS 0


Best regards,

v

             reply	other threads:[~2006-07-27 11:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 11:11 Vikas Kedia [this message]
     [not found] <6Dc4C-1tt-47@gated-at.bofh.it>
2006-07-27 12:34 ` Bodo Eggert
     [not found] <fa.2RkKSvRvPsGNSGCsUHQ9gQ8qlrg@ifi.uio.no>
2006-07-27 19:34 ` Robert Hancock
2006-07-28  5:28   ` Handle X
     [not found] <fa.5uWgnVpIOBN4Pb1aWwNzF8P2OA0@ifi.uio.no>
     [not found] ` <fa.9M8mPetEI5HZ8L2RMGPhKPm3gJA@ifi.uio.no>
2006-07-28  8:34   ` Robert Hancock
2006-07-28 18:13     ` Handle X

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fbe022af0607270411u78ad633m650063061ea6bd5@mail.gmail.com \
    --to=kedia.vikas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®