linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] sata_sil: disable hotplug interrupts on two ATI IXPs
Date: Mon, 26 Jun 2006 18:33:14 +0200	[thread overview]
Message-ID: <200606261833.14905.ak@suse.de> (raw)
In-Reply-To: <20060626122352.GA10140@htj.dyndns.org>

On Monday 26 June 2006 14:23, Tejun Heo wrote:
> Some SATA controllers embedded in ATI IXPs seem to have broken
> SATA_IRQ bit in their bmdma2 registers which is always stuck at 1.
> This makes the driver believe that there has been a hotplug event and
> freeze the port whenever there's an interrupt thus failing all
> commands.
> 
> This patch disables SATA_IRQ for those controllers.
> 
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> ---
> 
> Andi, can you please verify this patch works?  Jeff, if Andi confirms
> it, please push this to Andrew & Linus.  I'll contact SIMG and try to
> find another way around this.  

Works thanks.

-Andi


libata version 1.30 loaded.
sata_sil 0000:00:11.0: version 1.0
GSI 19 sharing vector 0xC9 and IRQ 19
ACPI: PCI Interrupt 0000:00:11.0[A] -> GSI 23 (level, low) -> IRQ 201
ata1: SATA max UDMA/100 cmd 0xFFFFC2001008E080 ctl 0xFFFFC2001008E08A bmdma 0xFF
FFC2001008E000 irq 201
ata2: SATA max UDMA/100 cmd 0xFFFFC2001008E0C0 ctl 0xFFFFC2001008E0CA bmdma 0xFF
FFC2001008E008 irq 201
scsi0 : sata_sil
ata1: SATA link down (SStatus 0 SControl 300)
scsi1 : sata_sil
ata2: SATA link down (SStatus 0 SControl 300)
ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 22 (level, low) -> IRQ 177
ata3: SATA max UDMA/100 cmd 0xFFFFC20010090080 ctl 0xFFFFC2001009008A bmdma 0xFF
FFC20010090000 irq 177
ata4: SATA max UDMA/100 cmd 0xFFFFC200100900C0 ctl 0xFFFFC200100900CA bmdma 0xFF
FFC20010090008 irq 177
scsi2 : sata_sil
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: configured for UDMA/100
scsi3 : sata_sil
ata4: SATA link down (SStatus 0 SControl 300)
  Vendor: ATA       Model: SAMSUNG SP2504C   Rev: VT10
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3
sd 2:0:0:0: Attached scsi disk sda


  reply	other threads:[~2006-06-26 16:35 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
2006-06-26 12:23           ` [PATCH] sata_sil: disable hotplug interrupts on two ATI IXPs Tejun Heo
2006-06-26 16:33             ` Andi Kleen [this message]
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=200606261833.14905.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 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).