All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: htejun@gmail.com, linux-ide@vger.kernel.org, jeremy@sgi.com,
	Mark Lord <liml@rtr.ca>
Subject: Re: sata_vsc with iq3124h regression in 2.6.20
Date: Fri, 09 Feb 2007 17:33:33 -0500	[thread overview]
Message-ID: <45CCF6BD.9020404@garzik.org> (raw)
In-Reply-To: <0C7297FA1D2D244A9C7F6959C0BF1E52015235BE@azsmsx413.amr.corp.intel.com>

Williams, Dan J wrote:
> When I fire up 2.6.20 with an iq3124h I get:
> 
> ata1: SATA max UDMA/133 cmd 0xC8822200 ctl 0xC8822229 bmdma 0xC8822270
> irq 25
> ata2: SATA max UDMA/133 cmd 0xC8822400 ctl 0xC8822429 bmdma 0xC8822470
> irq 25
> ata3: SATA max UDMA/133 cmd 0xC8822600 ctl 0xC8822629 bmdma 0xC8822670
> irq 25
> ata4: SATA max UDMA/133 cmd 0xC8822800 ctl 0xC8822829 bmdma 0xC8822870
> irq 25
> scsi0 : sata_vsc
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> irq 25: nobody cared (try booting with the "irqpoll" option)
> handlers:
> [<c01796e0>] (vsc_sata_interrupt+0x0/0x194)
> Disabling IRQ #25
> 
> I did a git bisect and came up with: [PATCH] libata: always use polling
> IDENTIFY (800b399669ad495ad4361d134df87401ae36f44f)
> 
> I could probably cobble together a workaround to use irq-driven IDENTIFY
> for this card but wanted to see if there was a better way.

As I recall, the 31244 and VSC-7174 always send an interrupt, so the 
driver should account for this.  I thought we had code already in the 
driver to handle this, but perhaps recent changes stomped that.

It would be good to standardize the way we handle these sorts of 
controllers, because (I think) Mark Lord has the same problem on 
sata_qstor (or pdc_adma?).

	Jeff




  reply	other threads:[~2007-02-09 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 22:21 sata_vsc with iq3124h regression in 2.6.20 Williams, Dan J
2007-02-09 22:33 ` Jeff Garzik [this message]
2007-02-10 14:58   ` Tejun Heo
2007-02-10 21:08   ` Mark Lord
2007-02-09 23:26 Dan Williams
2007-02-12  3:19 ` Tejun Heo

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=45CCF6BD.9020404@garzik.org \
    --to=jeff@garzik.org \
    --cc=dan.j.williams@intel.com \
    --cc=htejun@gmail.com \
    --cc=jeremy@sgi.com \
    --cc=liml@rtr.ca \
    --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.