All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Avuton Olrich <avuton@gmail.com>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: EDAC (was: Re: 2.6.14-rc5-mm1)
Date: Wed, 26 Oct 2005 09:48:24 +0200	[thread overview]
Message-ID: <20051026074824.GA7121@favonius> (raw)
In-Reply-To: <1130265540.25191.55.camel@localhost.localdomain>

Alan Cox wrote (ao):
> On Maw, 2005-10-25 at 10:55 -0700, Avuton Olrich wrote:
> > After upgrading to 2.6.14-rc5-mm1 I have been greeted with:
> > 
> > PCI-Bridge- Detected Parity Error on 0000:00:08.0 0000:00:08.0
> 
> > ... I probably get a new one every minute or so. Is this new, perhaps
> > part of the new EDAC stuff? And what kind of adverse effect does this
> > have on my computer (the actual parity error)?
> 
> If the parity error is real then it would indicate a bad PCI transfer
> has occurred and data corrupted in the transfer. Unfortunately because
> some vendors don't use PCI parity checking much and some card vendors
> don't debug their products except on that OS there are some cards that
> generate spurious parity errors.
> 
> Can you send an lspci -vxx. That'll help the EDAC folk build up a view
> of what needs to be blacklisted.

Stupid question: should EDAC work on a Via Epia board? Because I see the
"Detected Parity Error" messages too (and a lot of them), but figured
that the option is just 'not an option' :-)

If it should work I'll be happy to send the error and lspci if that
helps.

-- 
Humilis IT Services and Solutions
http://www.humilis.net

  parent reply	other threads:[~2005-10-26  7:48 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24  8:48 2.6.14-rc5-mm1 Andrew Morton
2005-10-24  9:28 ` 2.6.14-rc5-mm1 Magnus Damm
2005-10-24  9:34 ` 2.6.14-rc5-mm1 Benoit Boissinot
2005-10-24 12:23 ` 2.6.14-rc5-mm1 Jens Axboe
2005-10-24 14:09 ` 2.6.14-rc5-mm1 Jasper Spaans
2005-10-24 15:40 ` 2.6.14-rc5-mm1 Badari Pulavarty
2005-10-24 15:43   ` 2.6.14-rc5-mm1 Adrian Bunk
2005-10-24 17:21     ` 2.6.14-rc5-mm1 Alan Cox
2005-10-25  9:54       ` 2.6.14-rc5-mm1 Adrian Bunk
2005-10-25 13:00         ` 2.6.14-rc5-mm1 Alan Cox
2005-10-25 13:29           ` 2.6.14-rc5-mm1 Adrian Bunk
2005-10-24 16:06 ` 2.6.14-rc5-mm1 Yoichi Yuasa
2005-10-24 17:51 ` 2.6.14-rc5-mm1 Lexington Luthor
2005-10-24 19:05   ` 2.6.14-rc5-mm1 Benoit Boissinot
2005-10-24 20:48 ` 2.6.14-rc5-mm1 Badari Pulavarty
2005-10-24 21:16   ` 2.6.14-rc5-mm1 Andrew Morton
2005-10-25 15:12     ` 2.6.14-rc5-mm1 Badari Pulavarty
2005-10-25 17:57       ` 2.6.14-rc5-mm1 Andrew Morton
2005-10-25 16:13     ` 2.6.14-rc5-mm1 Christoph Hellwig
2005-10-27 15:26     ` 2.6.14-rc5-mm1 Andrew Vasquez
2005-10-27 15:44       ` 2.6.14-rc5-mm1 Badari Pulavarty
2005-10-27 16:48         ` 2.6.14-rc5-mm1 Andrew Vasquez
2005-10-27 19:02       ` 2.6.14-rc5-mm1 Christoph Hellwig
2005-10-27 21:53         ` 2.6.14-rc5-mm1 Andrew Vasquez
2005-10-28 22:51           ` HEADS UP for QLA2100 users Christoph Hellwig
2005-10-28 23:03             ` Andrew Vasquez
2005-10-28 23:35               ` Badari Pulavarty
2006-02-04 22:58                 ` Adrian Bunk
2006-02-14  0:14                   ` [2.6 patch] schedule the SCSI qlogicfc driver for removal Adrian Bunk
2006-02-14 17:43                     ` Christoph Hellwig
2006-03-25 18:04                       ` Adrian Bunk
2005-10-25  5:13 ` intel-agp and yenta-socket issues (was Re: 2.6.14-rc5-mm1 Valdis.Kletnieks
2005-10-25  5:32   ` Andrew Morton
2005-10-25 14:07     ` Valdis.Kletnieks
2005-10-27  8:07       ` 2.6.14-rc5-mm1 crypto issues (was " Valdis.Kletnieks
2005-10-25 17:55 ` 2.6.14-rc5-mm1 Avuton Olrich
2005-10-25 18:39   ` 2.6.14-rc5-mm1 Alan Cox
2005-10-25 18:16     ` 2.6.14-rc5-mm1 Avuton Olrich
2005-10-26  7:48     ` Sander [this message]
2005-10-26 11:09       ` EDAC (was: Re: 2.6.14-rc5-mm1) Alan Cox
2005-10-26 13:11         ` Sander
2005-10-26 19:08           ` Doug Thompson
2005-10-26 19:38             ` Sander
2005-10-26 20:22               ` Doug Thompson
2005-10-27  6:23                 ` Sander
2005-10-27 16:59                   ` Roger Heflin
2005-10-27 16:50                 ` Roger Heflin
2005-10-25 23:49 ` 2.6.14-rc5-mm1 - ide-cs, pcmcia ioctl Damir Perisa
2005-10-27 21:31   ` 2.6.14-rc5-mm1 - ide-cs broken! Damir Perisa
2005-10-27 22:03     ` Andrew Morton
2005-10-27 23:18       ` Damir Perisa
2005-10-28 17:58 ` 2.6.14-rc5-mm1: EDAC: several options without a help text Adrian Bunk
2005-10-31 15:26   ` Alan Cox
2005-10-29 19:46 ` 2.6.14-rc5-mm1: reiser4: ICE with gcc 2.95 Adrian Bunk
2005-10-29 19:59 ` 2.6.14-rc5-mm1: SAS: compile error " Adrian Bunk
2005-10-29 20:15   ` Luben Tuikov
2005-10-29 20:48 ` [-mm patch] EDAC drivers: missing PCI dependencies Adrian Bunk
2005-10-30 15:53 ` [-mm patch] fs/namei.c: make path_lookup_create() static Adrian Bunk
2005-10-30 15:58   ` Trond Myklebust
2005-11-02  0:53 ` [-mm patch] fix NET_RADIO=n, IEEE80211=y compile Adrian Bunk
2005-11-02 16:24 ` [-mm patch] EDAC: remove proc_ent from struct mem_ctl_info Adrian Bunk
2005-11-02 17:44   ` Alan Cox

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=20051026074824.GA7121@favonius \
    --to=sander@humilis.net \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=avuton@gmail.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.