linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Linux PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: Change in PCI behaviour
Date: Tue, 23 Nov 2010 07:26:55 +1100	[thread overview]
Message-ID: <1290457615.32570.67.camel@pasglop> (raw)
In-Reply-To: <4CEA3F87.9080102@mlbassoc.com>

On Mon, 2010-11-22 at 03:01 -0700, Gary Thomas wrote:
> I have a bit more information on this.  I'm pretty sure that the failures
> are only happening in my SCSI (SATA actually) code.  My board (8347ea) has
> a PCI bus with a SIL SATA controller.  This combo works perfectly in 2.6.28.
> In 2.6.32, it will run for a while (possibly quite a while), then timeout
> trying to do a large block write - typically 256 blocks.  Once this timeout
> happens, the SIL controller is stuck and accesses to it will eventually
> cause the whole system to hang (as above).
> 
> Was there any major change in how PCI or DMA was handled between 2.6.28
> and 2.6.32?  Given the ephemeral nature of these failures (multiple runs
> all eventually fail, but never the same twice), my only hope of fixing it
> will be to have some ideas what might have changed.

Maybe the changes you did to the PCI outbound windows are now breaking
DMA ? Make sure the outbound and inbound don't overlap for example and
that all RAM is reachable for inbound.

Cheers,
Ben.

  reply	other threads:[~2010-11-22 20:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 15:42 Change in PCI behaviour Gary Thomas
2010-11-19 21:46 ` Benjamin Herrenschmidt
2010-11-21 17:59   ` Gary Thomas
2010-11-22 10:01     ` Gary Thomas
2010-11-22 20:26       ` Benjamin Herrenschmidt [this message]
2010-11-23 14:44         ` Gary Thomas
2010-12-04 12:49           ` Gary Thomas
2010-12-04 21:07             ` Benjamin Herrenschmidt
2010-11-22 10:37 ` Gabriel Paubert

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=1290457615.32570.67.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=gary@mlbassoc.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;
as well as URLs for NNTP newsgroup(s).