public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederman@lnxi.com (Eric W. Biederman)
To: Doug Thompson <norsk5@yahoo.com>
Cc: Dave Jones <davej@redhat.com>, Alan Cox <alan@redhat.com>,
	"bluesmoke-devel@lists.sourceforge.net" 
	<bluesmoke-devel@lists.sourceforge.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: noisy edac
Date: Mon, 30 Jan 2006 20:28:37 -0700	[thread overview]
Message-ID: <m3vew1jct6.fsf@maxwell.lnxi.com> (raw)
In-Reply-To: <20060130185931.71975.qmail@web50112.mail.yahoo.com> (Doug Thompson's message of "Mon, 30 Jan 2006 10:59:31 -0800 (PST)")

Doug Thompson <norsk5@yahoo.com> writes:

> that driver should be refactored to only output NON-FATALs with debug turned on.

We need to root cause this before that decision is made.

> --- Dave Jones <davej@redhat.com> wrote:
>
>> On Sun, Jan 29, 2006 at 04:52:06PM -0500, Alan Cox wrote:
>>  > 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 ?
>> 
>> Currently shipping Dell Precision 470.
>> 

Actually I remember something very weird with this error.
I think the Non-Fatal was some weird designation by Intel,
that came right out of the data sheet but didn't have a useful
interpretation.

I suspect that you have an actual hardware problem there.
Quite possibly that a riser or card is not plugged in all of
the way.

As I recall most of the checks clear the error bit when they
detect the error so the fact that it is reoccurring suggests
that the error is reoccurring this frequently.

So before we go off and give up and interpreting this error
can we please root cause at least what the driver is doing?

It has been about a year since I saw something like this and
someone else was tracking the error but I seem to remember
an error message like this resulting from  an actual fixable problem.

Eric



      parent reply	other threads:[~2006-01-31  3:28 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
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       ` Eric W. Biederman [this message]

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=m3vew1jct6.fsf@maxwell.lnxi.com \
    --to=ebiederman@lnxi.com \
    --cc=alan@redhat.com \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=norsk5@yahoo.com \
    /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