linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: Jeff Garzik <jgarzik@pobox.com>, Alan Cox <alan@redhat.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Port Multiplier drives not always all found on cold plug
Date: Sat, 17 May 2008 23:21:21 +0900	[thread overview]
Message-ID: <482EE9E1.5000805@gmail.com> (raw)
In-Reply-To: <482DCD1F.4090503@rtr.ca>

Mark Lord wrote:
> Mark Lord wrote:
>>
>>> So I guess the questions are:
>>>
>>> 1. Where are these unexpected interrupts coming from?
> ..
> 
> Well, I'm still not sure of the source of the interrupt,
> but I did just now find an ancient bug in sata_mv,
> in it's internal handling of the port interrupt mask.
> 
> The DONE_IRQ bit gets enabled a tad early in the EH sequence,
> enabling us to receive interrupts when we're not expecting them.
> 
> Looks like that mv_unexpected_intr() function was useful after all.  :)
> 
> Patches forthcoming to clean this up, once I study things a bit more.

I've been studying things for last two days and discovered a number of 
things.  I'll soon post patch series.  Thanks a lot for digging into PMP 
stuff.  It's great to have someone else's eyes on this stuff.

-- 
tejun

  reply	other threads:[~2008-05-17 14:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 16:34 Port Multiplier drives not always all found on cold plug Mark Lord
2008-05-16 16:46 ` Mark Lord
2008-05-16 16:54   ` Mark Lord
2008-05-16 17:27     ` Mark Lord
2008-05-16 18:06       ` Mark Lord
2008-05-17 14:21         ` Tejun Heo [this message]
2008-05-17 17:32           ` Mark Lord
2008-05-17 17:52             ` Tejun Heo
2008-05-17 19:16               ` Mark Lord
2008-05-18  5:23                 ` Tejun Heo
2008-06-02  3:38                   ` JR Wilbert
2008-06-09  1:47                     ` 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=482EE9E1.5000805@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@redhat.com \
    --cc=jgarzik@pobox.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 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).