public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mark gross <mgross@linux.intel.com>
To: Doug Thompson <norsk5@yahoo.com>
Cc: gtm.kramer@inter.nl.net, Andrew Morton <akpm@osdl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6]  EDAC Patch Set
Date: Mon, 22 May 2006 14:34:04 -0700	[thread overview]
Message-ID: <20060522213404.GA9881@linux.intel.com> (raw)
In-Reply-To: <20060524185512.99258.qmail@web50105.mail.yahoo.com>

On Wed, May 24, 2006 at 11:55:12AM -0700, Doug Thompson wrote:
> 
> 
> --- Jurgen Kramer <gtm.kramer@inter.nl.net> wrote:
> > 
> > Will this patchset fix/suppress the "Non-Fatal Error PCI Express B"
> > messages I see with the E7525 edac?
> 
> No not yet. These patches are part of the set we gathered in the queue after EDAC
> was put into the kernel as a result of various other feedback.  The Non-Fatal noise
> has been placed in the queue of work to do. Dave Peterson, who was co-maintainer of
> EDAC, has moved on, so I have picking up the TODO slack and flushing these patches
> out the door so I can start with a somewhat cleaner slate.
> 
> The good news is I have found a maintainer for the E7525 MC driver (I don't have
> access to a mobo with that chipset, so I have a problem in verifying any mods I do
> work) who has agreed to work with that driver. Thanks to mark gross for taking that
> on. He and I have discussed this noise issue.
> 

I have a couple of platforms that reproduce the non-fatal pci express noise.

As I mentioned to Doug, I will dig into this issue after OLS.   However; if
anyone has any ideas to share with me on it I'll take any advice I can get.  I
first would like to get a good root cause on why these things are coming from
the PCI code atfer loading the edac_e752x driver. 

--mgross

> doug thompson
> 
> > 
> > I am running 2.6.16 (or more specific FC5 2.6.16-1.2111) with seems to
> > already include this version:
> > 
> > MC: drivers/edac/edac_mc.c version edac_mc  Ver: 2.0.0 May  4 2006
> > 
> > This version still floods my syslog with "Non-Fatal Error...." messages.
> > 
> > Jurgen
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2006-05-25 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 17:43 [PATCH 0/6] EDAC Patch Set Doug Thompson
2006-05-24 18:17 ` Jurgen Kramer
2006-05-24 18:55   ` Doug Thompson
2006-05-22 21:34     ` mark gross [this message]
2006-05-25  4:42 ` Andrew Morton
2006-05-22 21:35   ` mark gross
  -- strict thread matches above, loose matches on Subject: below --
2006-06-26 22:15 Doug Thompson

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=20060522213404.GA9881@linux.intel.com \
    --to=mgross@linux.intel.com \
    --cc=akpm@osdl.org \
    --cc=gtm.kramer@inter.nl.net \
    --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