All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Alan <alan@lxorguk.ukuu.org.uk>, David Shirley <tephra@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: SATA DMA problem (sata_uli)
Date: Tue, 19 Dec 2006 19:39:47 -0500	[thread overview]
Message-ID: <45888653.6080702@pobox.com> (raw)
In-Reply-To: <458884B2.9080802@gmail.com>

Tejun Heo wrote:
> Jeff Garzik wrote:
>> Alan wrote:
>>>> I tracked it down to one of the drives being forced into PIO4 mode
>>>> rather than UDMA mode; dmesg bits:
>>>> ata4.00: ATA-7, max UDMA/133, 586072368 sectors: LBA48 NCQ (depth 0/32)
>>>> ata4.00: ata4: dev 0 multi count 16
>>>> ata4.00: simplex DMA is claimed by other device, disabling DMA
>>> Your ULi controller is reporting that it supports UDMA upon only one
>>> channel at a time. The kernel is honouring this information. The older
>>> ULi (was ALi) PATA devices report simplex but let you turn it off so
>>> see if the following does the trick. Test carefully as always with
>>> disk driver
>>> changes.
>>>
>>> (Jeff probably best to check the docs before merging this but I believe
>>> it is sane)
>>>
>>> Signed-off-by: Alan Cox <alan@redhat.com>
>> My Uli SATA docs do not appear to cover the bmdma registers :(  Only the
>> PCI config registers.
>>
>> But regardless, I think the better fix is to never set ATA_HOST_SIMPLEX
>> if ATA_FLAG_NO_LEGACY is set.
>>
>> None of the SATA controllers I've ever encountered has been simplex.
> 
> Just another data point.  The same problem is reported by bug #7590.
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=7590
> 
> Is somebody brewing a patch?

Not to my knowledge.  Did you just volunteer?  ;-)

/me runs...

	Jeff




  reply	other threads:[~2006-12-20  0:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13  5:02 SATA DMA problem (sata_uli) David Shirley
2006-12-13 11:20 ` Alan
2006-12-16 16:13   ` Jeff Garzik
2006-12-20  0:32     ` Tejun Heo
2006-12-20  0:39       ` Jeff Garzik [this message]
2006-12-20  2:44         ` Tejun Heo
2006-12-27 13:44           ` 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=45888653.6080702@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tephra@gmail.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.