From: Dave Jones <davej@redhat.com>
To: Jurgen Kramer <gtm.kramer@inter.nl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Non-Fatal Error PCI Express messages
Date: Fri, 31 Mar 2006 15:19:59 -0500 [thread overview]
Message-ID: <20060331201959.GI4133@redhat.com> (raw)
In-Reply-To: <1143793550.3331.4.camel@paragon.slim>
On Fri, Mar 31, 2006 at 10:25:50AM +0200, Jurgen Kramer wrote:
> With 2.6.16 (from FC5s 2.6.16-1.2080_FC5smp) I am getting a lot of
>
> Mar 31 09:35:16 paragon kernel: Non-Fatal Error PCI Express B
> Mar 31 09:35:17 paragon kernel: Non-Fatal Error PCI Express B
> Mar 31 09:35:17 paragon kernel: Non-Fatal Error PCI Express B
> Mar 31 09:35:18 paragon kernel: Non-Fatal Error PCI Express B
> Mar 31 09:35:18 paragon kernel: Non-Fatal Error PCI Express B
> Mar 31 09:35:20 paragon kernel: Non-Fatal Error PCI Express B
> Mar 31 09:35:20 paragon kernel: Non-Fatal Error PCI Express B
> Mar 31 09:35:39 paragon kernel: Non-Fatal Error PCI Express B
>
> messages which presumably come from
>
> Mar 31 09:17:15 paragon kernel: MC: drivers/edac/edac_mc.c version
> edac_mc Ver: 2.0.0 Mar 28 2006
> Mar 31 09:17:15 paragon kernel: EDAC MC0: Giving out device to
> "e752x_edac" E7525: PCI 0000:00:00.0
>
> Is there really something broken here of just a noisy driver?
really noisy driver.
http://lkml.org/lkml/2006/1/26/381
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-03-31 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 8:25 Non-Fatal Error PCI Express messages Jurgen Kramer
2006-03-31 18:22 ` Dave Peterson
2006-03-31 19:18 ` Jurgen Kramer
2006-03-31 20:03 ` Dave Jiang
2006-03-31 20:19 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-31 19:53 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=20060331201959.GI4133@redhat.com \
--to=davej@redhat.com \
--cc=gtm.kramer@inter.nl.net \
--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