All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Tejun Heo 6t <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: More information on ATI IXP failure in git9
Date: Mon, 26 Jun 2006 11:13:30 +0200	[thread overview]
Message-ID: <200606261113.30316.ak@suse.de> (raw)
In-Reply-To: <449F9D78.7070503@gmail.com>

On Monday 26 June 2006 10:40, Tejun Heo wrote:
> Hello, Andi.
> 
> Andi Kleen wrote:
> > Still doesn't work with it - see http://one.firstfloor.org/~andi/sata3.jpg
> 
> * SATA_IRQ bit is stuck (on all other sil controllers, this gets cleared 
> when SError is cleared)
> 
> * whenever interrupt occurs (from itself or from any other ones sharing 
> the IRQ), irq handler sees SATA_IRQ bit set and thus thinks it just 
> received phy status changed IRQ.
> 
> * phy status change aborts the active command, so no command gets completed.
> 
> I'm attaching two patches.  The first one tries to clear SATA_IRQ by 
> writing 1 to it in thaw() assuming the bit is implemented as W1C (which 
> BTW is out of spec).  The second one kills SATA_IRQ handling completely. 
>   I wish the first one works but if not I'll update the second one such 
> that it applies only to ATI IXP.

Patch 0 and 1 together work, patch 0 only runs into the usual zero err_mask
problem and doesn't find root.

-Andi


  parent reply	other threads:[~2006-06-26  9:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-25 21:59 More information on ATI IXP failure in git9 Andi Kleen
2006-06-25 22:19 ` Jeff Garzik
2006-06-26  5:24   ` Andi Kleen
2006-06-25 23:23 ` Jeff Garzik
2006-06-26  2:10   ` Tejun Heo
2006-06-26  6:18     ` Andi Kleen
2006-06-26  8:40       ` Tejun Heo
2006-06-26  8:57         ` Tejun Heo
2006-06-26  9:22           ` Andi Kleen
2006-06-26  9:13         ` Andi Kleen [this message]
2006-06-26 12:23           ` [PATCH] sata_sil: disable hotplug interrupts on two ATI IXPs Tejun Heo
2006-06-26 16:33             ` Andi Kleen
2006-06-27  1:02             ` Jeff Garzik

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=200606261113.30316.ak@suse.de \
    --to=ak@suse.de \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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.