LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: eeh bug
Date: Fri, 18 May 2007 08:43:39 +1000	[thread overview]
Message-ID: <1179441819.32247.317.camel@localhost.localdomain> (raw)
In-Reply-To: <20070517164438.GD4325@austin.ibm.com>

On Thu, 2007-05-17 at 11:44 -0500, Linas Vepstas wrote:
> I'll take a look. Usually, there's no pci_dev only when its a slot
> with no device plugged into it; these can still receive EEH errors
> during config space i/o to the bridge (I presume that the
> justification
> is when aluminum scrap shorts out a pci connector or something like
> that). In all other cases, there's a pci_dev, which is why the 
> bug slipped by.

Hrm... in that case, there's a device in. I'll try to track down why we
don't get it.

Ben.

      reply	other threads:[~2007-05-17 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17  4:46 eeh bug Benjamin Herrenschmidt
2007-05-17  4:59 ` Benjamin Herrenschmidt
2007-05-17 16:44   ` Linas Vepstas
2007-05-17 22:43     ` Benjamin Herrenschmidt [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=1179441819.32247.317.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linas@austin.ibm.com \
    --cc=linuxppc-dev@ozlabs.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