From: Tejun Heo <htejun@gmail.com>
To: Mark Nelson <mdnelson8@gmail.com>
Cc: George Spelvin <linux@horizon.com>,
grundler@google.com, linux-ide@vger.kernel.org,
shane.huang@amd.com, jgarzik@redhat.com
Subject: Re: What's the SB600 64-bit DMA problem?
Date: Wed, 24 Sep 2008 18:46:51 +0900 [thread overview]
Message-ID: <48DA0C8B.3000406@gmail.com> (raw)
In-Reply-To: <65a6ef750809231730h52f6bf47g23b33db1d2f4ca08@mail.gmail.com>
Mark Nelson wrote:
> On Sun, Sep 21, 2008 at 10:15 AM, George Spelvin <linux@horizon.com> wrote:
>> "Grant Grundler" <grundler@google.com> wrote:
>>> On Sat, Sep 20, 2008 at 8:17 AM, George Spelvin <linux@horizon.com> wrote:
>>>> I just got a couple of MSI KA92 (AMD 790FX-based) motherboards with
>>>> 8 GiB of RAM each. I noticed on boot that the SB600 AHCI implementation
>>>> had a 32-bit DMA limitation, and looking in the archives, it
>>>> appears that folks from AMD think it doesn't need to be there.
>>> URL?
>>> Just want to be sure I'm looking at the same thread.
>> "About forcing 32bit DMA patch for AMD690G(SB600)"
>> http://marc.info/?t=120107450600001
>
> It looks like the results from people testing it further never arrived...
>
>>From git commit a878539ef994787c447a98c2e3ba0fe3dad984ec ("ahci:
> work around ATI SB600 h/w quirk"), it looks like the initial
> idea was to limit each command to a maximum of 255 sectors (but
> to still allow 64bit DMA), but according to a later commit
> (4cde32fc4b32e96a99063af3183acdfd54c563f0; "ahci: SB600
> workaround is suspect... play it safe for now") this did not
> solve the lockups. But there are references in the thread above
> to broken MSI on the SB600 possibly being the cause of the problem,
> and now that commit 22b5e7a74280deae560c20ee1a9b502b35181327
> ("ahci: SB600 ahci can't do MSI, blacklist that capability") has gone in
> maybe this is why you're able to get 64bit DMA working? (although
> we do need more hints on how to conclusively test this)
Hmm... I doubt MSI has anything to do with 64bit DMA but then again
anything is possible. Shane, anything came out of the testing?
Thanks.
--
tejun
next prev parent reply other threads:[~2008-09-24 9:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-20 15:17 What's the SB600 64-bit DMA problem? George Spelvin
2008-09-20 22:28 ` Grant Grundler
2008-09-21 0:15 ` George Spelvin
2008-09-24 0:30 ` Mark Nelson
2008-09-24 9:46 ` Tejun Heo [this message]
2008-09-24 10:19 ` Huang, Shane
2008-09-25 3:24 ` George Spelvin
2008-09-26 14:06 ` Tejun Heo
2008-09-28 21:04 ` George Spelvin
2008-09-28 23:20 ` Tejun Heo
2008-09-29 4:08 ` George Spelvin
2008-09-29 4:25 ` Tejun Heo
2008-09-30 2:00 ` George Spelvin
2008-10-01 3:57 ` Tejun Heo
2008-10-01 13:26 ` George Spelvin
2008-09-26 16:04 ` Grant Grundler
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=48DA0C8B.3000406@gmail.com \
--to=htejun@gmail.com \
--cc=grundler@google.com \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux@horizon.com \
--cc=mdnelson8@gmail.com \
--cc=shane.huang@amd.com \
/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.