From: Albert Lee <albertcc@tw.ibm.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: jeff@garzik.org, linux-ide@vger.kernel.org,
Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: Implement the technote about promise/maxtor drives
Date: Fri, 16 Feb 2007 14:32:35 +0800 [thread overview]
Message-ID: <45D55003.6030307@tw.ibm.com> (raw)
In-Reply-To: <20070131171251.4210bcdb@localhost.localdomain>
Alan wrote:
> I don't have the hardware combination to test this one so would
> appreciate people testing it before it goes anywhere further
>
I've gotten two Maxtor UDMA/133 drives for testing with 2.6.20-git11.
Those Maxtors drives are quite old: the media access commands no longer
work, but device identify/configuration still works.
Below is the test result:
1. Before the patch, both drives are configured to UDMA/133:
pata_pdc2027x 0000:02:05.0: version 0.74-ac5
ACPI: PCI Interrupt 0000:02:05.0[A] -> Link [LNK1] -> GSI 10 (level, low) -> IRQ 10
pata_pdc2027x 0000:02:05.0: PLL input clock 16713 kHz
ata5: PATA max UDMA/133 cmd 0xe09e97c0 ctl 0xe09e9fda bmdma 0xe09e9000 irq 10
ata6: PATA max UDMA/133 cmd 0xe09e95c0 ctl 0xe09e9dda bmdma 0xe09e9008 irq 10
scsi4 : pata_pdc2027x
ata5.00: ATA-5: MAXTOR 6L060L3, A93.0500, max UDMA/133
ata5.00: 117266688 sectors, multi 16: LBA
ata5.01: ATA-7: Maxtor 6Y060L0, YAR41BW0, max UDMA/133
ata5.01: 120103200 sectors, multi 16: LBA
ata5.00: configured for UDMA/133
ata5.01: configured for UDMA/133
scsi5 : pata_pdc2027x
ATA: abnormal status 0x8 on port 0xe09e95df
scsi 4:0:0:0: Direct-Access ATA MAXTOR 6L060L3 A93. PQ: 0 ANSI: 5
SCSI device sdb: 117266688 512-byte hdwr sectors (60041 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdb: 117266688 512-byte hdwr sectors (60041 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb:
sd 4:0:0:0: Attached scsi disk sdb
scsi 4:0:1:0: Direct-Access ATA Maxtor 6Y060L0 YAR4 PQ: 0 ANSI: 5
SCSI device sdc: 120103200 512-byte hdwr sectors (61493 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdc: 120103200 512-byte hdwr sectors (61493 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1
sd 4:0:1:0: Attached scsi disk sdc
======================================================================================
2. After the patch, the slave drive is limited to UDMA/100:
pata_pdc2027x 0000:02:05.0: version 0.74-ac5
ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 10
ACPI: PCI Interrupt 0000:02:05.0[A] -> Link [LNK1] -> GSI 10 (level, low) -> IRQ 10
pata_pdc2027x 0000:02:05.0: PLL input clock 16992 kHz
ata3: PATA max UDMA/133 cmd 0xe08497c0 ctl 0xe0849fda bmdma 0xe0849000 irq 10
ata4: PATA max UDMA/133 cmd 0xe08495c0 ctl 0xe0849dda bmdma 0xe0849008 irq 10
scsi2 : pata_pdc2027x
input: ImPS/2 Logitech Wheel Mouse as /class/input/input1
ata3.00: ATA-5: MAXTOR 6L060L3, A93.0500, max UDMA/133
ata3.00: 117266688 sectors, multi 16: LBA
ata3.01: ATA-7: Maxtor 6Y060L0, YAR41BW0, max UDMA/133
ata3.01: 120103200 sectors, multi 16: LBA
ata3.00: configured for UDMA/133
ata3.01: configured for UDMA/100
scsi3 : pata_pdc2027x
ATA: abnormal status 0x8 on port 0xe08495df
scsi 2:0:0:0: Direct-Access ATA MAXTOR 6L060L3 A93. PQ: 0 ANSI: 5
SCSI device sdb: 117266688 512-byte hdwr sectors (60041 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdb: 117266688 512-byte hdwr sectors (60041 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb:
sd 2:0:0:0: Attached scsi disk sdb
scsi 2:0:1:0: Direct-Access ATA Maxtor 6Y060L0 YAR4 PQ: 0 ANSI: 5
SCSI device sdc: 120103200 512-byte hdwr sectors (61493 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdc: 120103200 512-byte hdwr sectors (61493 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1
sd 2:0:1:0: Attached scsi disk sdc
===================================================
So, it looks the patch works as designed/intended.
BTW, maybe we should print something similar to the "applying bridge limits" message,
otherwise the end users might wonder why their slave drive is configured as UDMA/100.
--
albert
next prev parent reply other threads:[~2007-02-16 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 17:12 Implement the technote about promise/maxtor drives Alan
2007-02-02 16:49 ` Jeff Garzik
2007-02-16 6:32 ` Albert Lee [this message]
2007-02-16 6:53 ` Albert Lee
2007-02-17 17:59 ` Eric D. Mudama
-- strict thread matches above, loose matches on Subject: below --
2007-02-02 18:27 Mikael Pettersson
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=45D55003.6030307@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).