From: Dave Jiang <djiang@mvista.com>
To: gtm.kramer@inter.nl.net
Cc: Dave Peterson <dsp@llnl.gov>,
linux-kernel@vger.kernel.org,
bluesmoke-devel@lists.sourceforge.net
Subject: Re: Non-Fatal Error PCI Express messages
Date: Fri, 31 Mar 2006 13:03:49 -0700 [thread overview]
Message-ID: <442D8B25.7070308@mvista.com> (raw)
In-Reply-To: <1143832684.3328.15.camel@paragon.slim>
Jurgen Kramer wrote:
> On Fri, 2006-03-31 at 10:22 -0800, Dave Peterson wrote:
>> On Friday 31 March 2006 00:25, 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?
>>>
>>> BTW this is on a Asus NCT-D mobo with Intel E7525 chipset.
>>>
>>> Jurgen
>> Hi Jurgen,
>>
>> I haven't seen this particular error before, and I can't say for sure
>> whether it's a genuine problem that should be dealt with or just a
>> minor annoyance that can be safely ignored. EDAC is a relatively new
>> piece of code, and still very much a work in progress. If this is in
>> fact a benign type of error, EDAC should provide a mechanism by which
>> a sysadmin can silence it. This is an area of future work.
>>
>> I'm forwarding your message to the bluesmoke mailing list just in
>> case anyone who reads that list has seen instances of this error in
>> the past and can provide more info on it.
>>
>> Dave
>
> Hi Dave,
>
> So far the system is running just fine. For reference, so far I found 92
> "Non-Fatal Error PCI Express B" messages since the system was booted 8
> hours ago.
>
> BTW Dave Jones reported similar problems on the LKML:
> http://lkml.org/lkml/2006/1/26/381
>
> Cheers,
>
> Jurgen
>
Do you have the sysbus message patch in the e752x driver? I've seen this before
on certain Intel ATCA boards, but it's actually the system bus complaining
and not the PCIe but the code is referencing the wrong print out messages. If
you do then it's probably PCIe.
next prev parent reply other threads:[~2006-03-31 20:03 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 [this message]
2006-03-31 20:19 ` Dave Jones
-- 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=442D8B25.7070308@mvista.com \
--to=djiang@mvista.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=dsp@llnl.gov \
--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