All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Shane Huang <Shane.Huang@amd.com>
Cc: sriharivijayaraghavan@yahoo.com.au, linux-ide@vger.kernel.org
Subject: Re: About forcing 32bit DMA patch for AMD690G(SB600)
Date: Fri, 25 Jan 2008 09:21:55 +0900	[thread overview]
Message-ID: <47992BA3.3070104@gmail.com> (raw)
In-Reply-To: <B90463BC30D2E446BA423D888DC85E501BF3CB@sshaexmb1.amd.com>

Hello, Shane.  Sorry about the delay.  Got caught up in other stuff.

Shane Huang wrote:
> Quoting Tejun:
>> Uh-oh, wait a bit. Nope. Until we figure out what the something
>> else
> is
>> and positively verify 64bit DMA works fine, the quirk stays in.
> 
> Our HW engineer has confirmed that our SB600 SATA controller indeed
> has some MSI issue, and we do not have any workaround.
> 
> The workaround "quirk_msi_intx_disable_bug" to SB700 SATA controller 
> can NOT work to SB600 SATA controller in my debug, while disablement
> to RS690 MSI in kernel source can fix it.

Hmmm... Okay.  Is the SB600 SATA controller culprit or the north bridge
- RS690?  If the former is the case, proper way to work around it is to
add AHCI_HFLAG_NO_MSI for SB600 AHCI.

> As to the SB600 64 bit DMA capacity, do you have any methods to do 
> further verification? I do NOT find any problem in my debug after I
> disabled RS690 MSI in kernel 2.6.24-rc7.

The problem is that we didn't actually prove anything.  In the tests
you've done, pci=nomsi didn't fix the problem but disable_all_msi quirk
did.  pci=nomsi and disable_all_msi quirk are identical.  Also,
Srihari's problem was not reproduced, so currently we can't say much
from the test results.  Srihari, do you still have the system around?

Thanks.

-- 
tejun

  parent reply	other threads:[~2008-01-25  0:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23  7:44 About forcing 32bit DMA patch for AMD690G(SB600) Shane Huang
2008-01-24  3:53 ` Shane Huang
2008-01-25  0:21 ` Tejun Heo [this message]
2008-01-25  4:19   ` Andrew Paprocki
2008-01-25  5:50     ` Tejun Heo
2008-01-25 20:57       ` Konstantin A. Lepikhov
2008-01-25 23:13         ` Jeff Garzik
2008-01-26  1:24         ` Tejun Heo
2008-01-31  9:14           ` Shane Huang
2008-01-26  1:07       ` Andrew Paprocki
2008-01-31  8:53         ` Shane Huang
2008-02-01  8:23           ` Tejun Heo
2008-02-02  4:04             ` Shane Huang
2008-02-10 20:55               ` Srihari Vijayaraghavan
  -- strict thread matches above, loose matches on Subject: below --
2008-01-29 20:10 Kelly Anderson

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=47992BA3.3070104@gmail.com \
    --to=htejun@gmail.com \
    --cc=Shane.Huang@amd.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=sriharivijayaraghavan@yahoo.com.au \
    /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.