mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Torsten Kaiser <just.for.lkml@googlemail.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org
Subject: Re: MSI broken in libata?
Date: Sun, 10 Jan 2010 05:33:58 +0100	[thread overview]
Message-ID: <64bb37e1001092033r1f0b4defw46c1a07101bb2d1b@mail.gmail.com> (raw)
In-Reply-To: <4B484829.6060405@kernel.org>

On Sat, Jan 9, 2010 at 10:11 AM, Tejun Heo <tj@kernel.org> wrote:
> On 12/25/2009 06:22 PM, Torsten Kaiser wrote:
>> As reported in http://lkml.org/lkml/2009/12/19/82 the new MSI support
>> for sata_sil24 does not work for me.
>> This is still the same with 2.6.33-rc2.
>>
>> Why I think, this might be a problem within libata:
>>  * other drivers can use MSI successful on my system (tg3, radeon, hda-intel)
>>  * happens both in sata_sil24 and sata_nv
>>  * the count in /proc/interrupts increases for the MSIs assigned to
>> sata_sil24/sata_nv, so interrupt delivery seems to work
>>  * only writing seems to fail
>
> How does it fail?  Timeouts?

Yes, timeouts.
I posted the error messages in http://lkml.org/lkml/2009/12/19/82 and
http://lkml.org/lkml/2010/1/6/60

> Also, ahci enables MSI by default if
> available and works fine on many configurations so I don't think
> anything in libata core layer is broken regarding MSI (there just
> isn't anything which can break).

The system I'm using does not have a ahci compatible controller, so I
could not compare this.
(And my other system that is using ahci, does not use MSI for that)

I just found it suspicious that 3 other drivers (tg3, hda-intel and
radeon) can use MSI, but both of the libata drivers (sata_sil24 and
sata_nv) fail in a similar way.

I did try the patch from Robert Hancock in
http://lkml.org/lkml/2010/1/6/417 ,but without success.

if you need any more information, or have something for me to try,
please just ask. I did look at the code and the documentation about
enabling MSI, but did not see anything (obvious) wrong, so I don't
know what to try next.

Torsten

  reply	other threads:[~2010-01-10  4:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-25  9:22 Torsten Kaiser
2010-01-09  9:11 ` Tejun Heo
2010-01-10  4:33   ` Torsten Kaiser [this message]
2010-01-11  1:15     ` Tejun Heo
2010-01-11  1:39       ` Robert Hancock
2010-01-11  2:17         ` Tejun Heo
2010-01-16 21:58         ` Torsten Kaiser
2010-01-17 19:22           ` Robert Hancock
2010-01-17 21:11             ` Torsten Kaiser
2010-01-18 20:51               ` Torsten Kaiser
2010-01-19  2:03                 ` Robert Hancock
2010-01-19  7:00                   ` Torsten Kaiser
2010-01-19 20:20                   ` Torsten Kaiser
2010-01-20  3:00                     ` Robert Hancock
2010-01-20  6:48                       ` Torsten Kaiser
2010-01-22  0:53                         ` Robert Hancock
2010-01-11  6:44       ` Torsten Kaiser

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=64bb37e1001092033r1f0b4defw46c1a07101bb2d1b@mail.gmail.com \
    --to=just.for.lkml@googlemail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®