linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: "David Shirley" <tephra@gmail.com>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: SATA DMA problem (sata_uli)
Date: Wed, 13 Dec 2006 11:20:04 +0000	[thread overview]
Message-ID: <20061213112004.59cb186c@localhost.localdomain> (raw)
In-Reply-To: <f0e65c090612122102o327ac693u2f24a74a9ba973ef@mail.gmail.com>

> 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>

--- drivers/ata/sata_uli.c~	2006-12-13 10:53:58.848881256 +0000
+++ drivers/ata/sata_uli.c	2006-12-13 10:53:58.848881256 +0000
@@ -211,6 +211,8 @@
 	if (rc)
 		goto err_out_regions;
 
+	ata_pci_clear_simplex(pdev);
+
 	ppi[0] = ppi[1] = &uli_port_info;
 	probe_ent = ata_pci_init_native_mode(pdev, ppi, ATA_PORT_PRIMARY | ATA_PORT_SECONDARY);
 	if (!probe_ent) {

  reply	other threads:[~2006-12-13 11:11 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 [this message]
2006-12-16 16:13   ` Jeff Garzik
2006-12-20  0:32     ` Tejun Heo
2006-12-20  0:39       ` Jeff Garzik
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=20061213112004.59cb186c@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.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 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).