From: Alan Cox <alan@redhat.com>
To: Mark Lord <liml@rtr.ca>
Cc: Gene Heskett <gene.heskett@gmail.com>, Alan Cox <alan@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux ide Mailing list <linux-ide@vger.kernel.org>
Subject: Re: Problem with ata layer in 2.6.24
Date: Mon, 28 Jan 2008 15:01:05 -0500 [thread overview]
Message-ID: <20080128200105.GA20201@devserv.devel.redhat.com> (raw)
In-Reply-To: <479E2130.5020208@rtr.ca>
On Mon, Jan 28, 2008 at 01:38:40PM -0500, Mark Lord wrote:
> >[ 31.195305] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max UDMA/66
> >[ 31.243813] ata2.01: ATA-7: MAXTOR STM3320620A, 3.AAE, max UDMA/100
> >[ 31.243816] ata2.01: 625142448 sectors, multi 16: LBA48
> >[ 31.243825] ata2.00: limited to UDMA/33 due to 40-wire cable
> >[ 31.417074] ata2.00: configured for UDMA/33
> >[ 31.451769] ata2.01: configured for UDMA/100
> ..
>
> That looks like an unrelated bug to me: the driver says "40-wire cable"
> but then goes and chooses UDMA/100 on one of the drives.
We currently assume that
- If we have host side detecting 40 that we use 40
- If we have drive side detecting 40 use 40
- If we have drive side detecting 80 and host thinks 80 use 80
The case where the drives disagree isn't currently considered.
next prev parent reply other threads:[~2008-01-28 20:01 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200801272122.21823.gene.heskett@gmail.com>
[not found] ` <18333.36746.819935.641383@harpo.it.uu.se>
[not found] ` <1201521783.6149.33.camel@lappy>
2008-01-28 12:54 ` Problem with ata layer in 2.6.24 Gene Heskett
2008-01-28 13:19 ` Gene Heskett
2008-01-28 13:57 ` Mikael Pettersson
2008-01-28 16:35 ` Gene Heskett
2008-01-28 16:50 ` Calvin Walton
2008-01-28 17:20 ` Zan Lynx
2008-01-28 17:30 ` Gene Heskett
2008-01-28 17:44 ` Gene Heskett
2008-01-28 17:59 ` Daniel Barkalow
2008-01-28 18:23 ` Richard Heck
2008-01-28 20:01 ` Daniel Barkalow
2008-01-29 0:05 ` Gene Heskett
2008-01-29 0:34 ` Daniel Barkalow
2008-01-29 1:31 ` Gene Heskett
2008-01-29 1:51 ` Daniel Barkalow
2008-01-29 4:48 ` Michal Jaegermann
2008-01-29 12:12 ` Alan Cox
2008-01-29 14:30 ` Gene Heskett
2008-01-29 14:51 ` Gene Heskett
2008-01-29 15:47 ` Alan Cox
2008-01-29 16:32 ` Gene Heskett
2008-01-29 16:48 ` Mikael Pettersson
2008-01-29 17:04 ` Gene Heskett
2008-01-29 17:38 ` Daniel Barkalow
2008-01-29 17:44 ` Alan Cox
2008-01-29 18:12 ` Daniel Barkalow
2008-01-29 17:59 ` Gene Heskett
2008-01-29 18:54 ` Alan Cox
2008-01-29 22:41 ` Gene Heskett
2008-01-29 22:48 ` Alan Cox
2008-01-30 0:19 ` rgheck
2008-01-30 0:19 ` Mark Lord
2008-01-29 17:06 ` rgheck
2008-01-29 17:12 ` Alan Cox
2008-01-29 17:24 ` rgheck
2008-01-29 17:40 ` Alan Cox
2008-01-29 18:11 ` Mark Lord
2008-01-29 18:28 ` rgheck
2008-01-29 18:32 ` Mark Lord
2008-01-29 18:14 ` Daniel Barkalow
2008-01-29 18:46 ` Alan Cox
2008-01-29 19:14 ` Daniel Barkalow
2008-01-29 19:34 ` Alan Cox
2008-01-28 16:56 ` Gene Heskett
2008-01-28 18:20 ` Mark Lord
2008-01-28 18:59 ` Gene Heskett
2008-01-28 20:43 ` Mark Lord
2008-01-29 0:06 ` Gene Heskett
2008-01-29 3:16 ` Mark Lord
2008-01-29 4:07 ` Gene Heskett
2008-01-28 17:06 ` Dave Neuer
2008-01-29 4:23 ` Kasper Sandberg
2008-01-29 4:49 ` Gene Heskett
2008-01-29 5:01 ` Kasper Sandberg
2008-02-02 7:13 ` Tejun Heo
2008-01-28 14:44 ` Richard Heck
2008-01-28 17:01 ` Gene Heskett
2008-01-28 18:38 ` Mark Lord
2008-01-28 20:01 ` Alan Cox [this message]
2008-01-28 20:29 ` Mark Lord
[not found] ` <479E24F7.4090502@rtr.ca>
2008-01-28 19:01 ` Mark Lord
[not found] ` <200801281404.12937.gene.heskett@gmail.com>
[not found] ` <479E399C.1030409@rtr.ca>
2008-01-28 20:32 ` Mark Lord
2008-01-28 19:08 ` Jeff Garzik
2008-01-28 19:13 ` Gene Heskett
2008-01-29 6:41 ` Florian Attenberger
2008-01-29 15:04 ` Gene Heskett
2008-01-29 16:12 ` Mark Lord
2008-01-29 16:36 ` Gene Heskett
2008-01-29 18:09 ` Mark Lord
2008-01-29 16:50 ` rgheck
2008-01-29 16:58 ` Jeff Garzik
2008-01-29 17:12 ` Gene Heskett
2008-01-29 17:32 ` Jeff Garzik
2008-01-29 17:53 ` Gene Heskett
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=20080128200105.GA20201@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=gene.heskett@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.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;
as well as URLs for NNTP newsgroup(s).