All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Dustin Harrison <d.harrison@sutus.com>,
	Sagar Borikar <sagar.borikar@gmail.com>,
	linux-ide@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: ata_check_status_mmio exception kernel panic
Date: Mon, 06 Apr 2009 23:02:59 -0400	[thread overview]
Message-ID: <49DAC263.2060107@pobox.com> (raw)
In-Reply-To: <20090404170036.7d4d33a2@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> port freeze during an interrupt while DMA is active causes a bus error 
>> to be thrown when the ata_check_status call fires.  I cannot reproduce 
>> this on x86.  I assume it handles the taskfile read error differently.
> 
> I hit this problem with the HPT343 (which locks the bus if you do this).
> For other devices where you get a PCI abort it is usually the case that
> x86 platforms ignore them while on many other platforms they produce
> exceptions.
> 
> In general I think we need to be sure all the core code paths stop DMA
> before poking in the taskfile (other than the basic IRQ check which we
> can't avoid)

I really think we are currently getting the ordering wrong, by calling 
ata_qc_complete() before we call the ->freeze() hook.

You can see sata_promise had problems with this, which led us to add DMA 
disabling in pdc_freeze()

But I think more generally, we seem to be missing a DMA-disable upon 
freeze, across a wide variety of controllers.

	Jeff




      reply	other threads:[~2009-04-07  3:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01  3:06 ata_check_status_mmio exception kernel panic Sagar Borikar
2009-04-01  3:08 ` Sagar Borikar
2009-04-01  3:37 ` Tejun Heo
2009-04-03 17:56 ` Dustin Harrison
2009-04-04  4:58   ` Tejun Heo
2009-04-07  2:59     ` Jeff Garzik
2009-04-04 16:00   ` Alan Cox
2009-04-07  3:02     ` Jeff Garzik [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=49DAC263.2060107@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=d.harrison@sutus.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=sagar.borikar@gmail.com \
    --cc=tj@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.