All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: Dave Jones <davej@redhat.com>,
	alan@redhat.com, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: noisy edac
Date: Sun, 29 Jan 2006 16:52:06 -0500	[thread overview]
Message-ID: <20060129215206.GA18670@devserv.devel.redhat.com> (raw)
In-Reply-To: <20060127014105.GD16422@redhat.com>

On Thu, Jan 26, 2006 at 08:41:05PM -0500, Dave Jones wrote:
> e752x_edac is very noisy on my PCIE system..
> my dmesg is filled with these...
> 
> [91671.488379] Non-Fatal Error PCI Express B
> [91671.492468] Non-Fatal Error PCI Express B
> [91901.100576] Non-Fatal Error PCI Express B
> [91901.104675] Non-Fatal Error PCI Express B

Pre-production system or final release ?

> Something need whitelisting? 

Its logging in a manner consistent with real errors so its hard to be sure
at first glance.

  reply	other threads:[~2006-01-29 21:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-27  1:41 noisy edac Dave Jones
2006-01-29 21:52 ` Alan Cox [this message]
2006-01-29 23:42   ` Dave Jones
2006-01-30 18:59     ` Doug Thompson
2006-01-30 19:58       ` Dave Peterson
2006-01-30 21:04         ` doug thompson
2006-01-30 22:24           ` Dave Peterson
2006-01-30 23:44             ` Gunther Mayer
2006-01-30 23:52               ` Dave Peterson
2006-01-31  0:02                 ` Gunther Mayer
2006-01-31  0:32                   ` doug thompson
2006-01-31  4:09                     ` Dave Peterson
2006-01-31  0:53                   ` Dave Peterson
2006-01-31  3:22                     ` Eric W. Biederman
2006-01-31  4:15                       ` Dave Peterson
2006-01-31 16:34                         ` doug thompson
2006-02-02  3:16                       ` [PATCH] EDAC printk() cleanup Dave Peterson
2006-02-02 16:16                         ` doug thompson
2006-01-31  3:28       ` noisy edac Eric W. Biederman

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=20060129215206.GA18670@devserv.devel.redhat.com \
    --to=alan@redhat.com \
    --cc=davej@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.