From: Brian King <brking@us.ibm.com>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: linuxppc64-dev@ozlabs.org,
Grant Grundler <grundler@parisc-linux.org>,
linux-scsi@vger.kernel.org, matthew@wil.cx
Subject: Re: Symbios PCI error recovery [Was: Re: [PATCH/RFC] ppc64: EEH + SCSI recovery (IPR only)]
Date: Tue, 22 Mar 2005 11:38:36 -0600 [thread overview]
Message-ID: <4240581C.1000906@us.ibm.com> (raw)
In-Reply-To: <20050321231028.GV498@austin.ibm.com>
Linas Vepstas wrote:
> Hi,
>
> There has been a running thread for a while on several mailing lists
> concerning PCI bus error recovery. Very breifly, some architectures
> have PCI error recovery mechanisms built into them (e.g. IBM PowerPC,
> also new PCI-Express chips from Intel (and other vendors) and possibly
> pa-risc and others).
>
> I've been trying to prototype error recovery. I currently have
> ethernet and the IPR scsi driver working, but I am having trouble with
> the symbios driver. I need help/advice ...
>
> On Fri, Feb 25, 2005 at 11:36:09PM -0700, Grant Grundler was heard to remark:
>
>>On Wed, Feb 23, 2005 at 07:31:37PM -0600, Linas Vepstas wrote:
>>
>>>I also want to do the symbios driver...
>>
>>FYI, Mathew Wilcox maintains the sym2 driver in cvs.parisc-linux.org.
>
>
>
> My current hardware will halt all i/o to/from the symbios controller
> upon detection of a PCI error. The recovery proceedure that I am
> currently using is to call system firmware (aka 'bios') to raise
> and then lower the #RST pci signal line for 1/4 second, then wait 2
> seconds for the PCI bus to settle, then restore the PCI config space
> registers (BARs, interrupt line, etc) to what they used to be. Then,
> I call sym_start_up() in an attempt to get the symbios card working
> again. And that's where I get stuck ...
>
> My assumption is that after the #RST, that the symbios card will sit
> there, dumb and stupid, with no scripts running. But sometimes I find
> that the card has done something to make the PCI error hardware trip
> again. Typically, this means that the card attempted to DMA to some
> address that its not allowed to touch, or raised #SERR or possibly
> #PERR (I can't tell which).
What config registers are you restoring? Is it possible symbios does not
like something in your config restore?
Another possiblity is that asserting PCI reset is not cleanly resetting
the card. Does PCI reset force BIST to be run on these cards? You could
try to manually run BIST on the card after the PCI reset to see if that
helps, or you could try power cycling the slot instead of using PCI reset.
-Brian
>
> Sometimes, I get the PCI error while the card is sitting there idly
> after the #RST, but more often, I get the error in sym_chip_reset(),
> immediately after the OUTB (nc_istat, SRST);
>
> Any clue what this is about? Am I missing something? I'm rather
> perplexed at this point, any clues/hints/suggestions are welcome.
>
> --linas
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
next prev parent reply other threads:[~2005-03-22 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050223002409.GA10909@austin.ibm.com>
[not found] ` <20050223174356.GH13081@kroah.com>
[not found] ` <1109207532.5384.32.camel@gaston>
[not found] ` <20050224013137.GF2088@austin.ibm.com>
[not found] ` <20050226063609.GC7036@colo.lackof.org>
2005-03-21 23:10 ` Symbios PCI error recovery [Was: Re: [PATCH/RFC] ppc64: EEH + SCSI recovery (IPR only)] Linas Vepstas
2005-03-22 17:38 ` Brian King [this message]
2005-03-31 20:14 ` Linas Vepstas
2005-04-01 6:15 ` Grant Grundler
2005-03-22 17:57 ` Grant Grundler
2005-03-31 20:06 ` Linas Vepstas
2005-04-01 6:08 ` Grant Grundler
2005-04-01 15:27 ` Brian King
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=4240581C.1000906@us.ibm.com \
--to=brking@us.ibm.com \
--cc=grundler@parisc-linux.org \
--cc=linas@austin.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=matthew@wil.cx \
/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