All I can offer on this, is that "-i" is *100%* dependent upon
whatever the IDE driver in the kernel decides to tell us.
Whereas "-I" (uppercase) is what the drive itself tells hdparm.
I plan on removing "-i" relatively soon (next year or so)
since it will not be supported at all by libata ("-I" works, though).
Or perhaps simply having "-i" use the data from "-I",
if people want hdparm to keep the abbreviated output format.
Cheers
--
Mark Lord
Real-Time Remedies Inc.
[EMAIL PROTECTED]
Stephen Gran wrote:
tags 336244 upstream
forwarded 336244 [EMAIL PROTECTED]
thanks
Mark,
When you get a minute, can you take a look at this? I just have no idea
why this would be happening. Or, rather, I have no idea why the test
performed should return true in one case and false in another.
Thanksm
------------------------------------------------------------------------
Subject:
Bug#336244: uncomplete udma list with hdparm -tTi
From:
Frisco <[EMAIL PROTECTED]>
Date:
Fri, 28 Oct 2005 23:26:50 +0200
To:
Debian Bug Tracking System <[EMAIL PROTECTED]>
To:
Debian Bug Tracking System <[EMAIL PROTECTED]>
Package: hdparm
Version: 6.1-2
Severity: normal
hdparm -tTi shows an uncomplete udma list for a harddisk drive when the
drive is connected as master with an ide burner (both P-ATA) at the same
controller port. Without the burner output is correct. See:
[EMAIL PROTECTED]:/downloads# hdparm -tTi /dev/hda
/dev/hda:
Model=SAMSUNG SP2514N, FwRev=VF100-33, SerialNo=S08BJ1RY501138
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16,
MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2
AdvancedPM=no WriteCache=enabled
Drive conforms to: unknown:
* signifies the current active mode
Timing cached reads: 2980 MB in 2.00 seconds = 1489.48
MB/sec
Timing buffered disk reads: 216 MB in 3.01 seconds =
71.80 MB/sec
read speed is the same as for the drive connected alone, so it seems to
be running udma6:
[EMAIL PROTECTED]:~# hdparm -tTi /dev/hda
/dev/hda:
Model=SAMSUNG SP2514N, FwRev=VF100-33, SerialNo=S08BJ1RY501138
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16,
MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=no WriteCache=enabled
Drive conforms to: unknown:
* signifies the current active mode
Timing cached reads: 3120 MB in 2.00 seconds = 1559.46
MB/sec
Timing buffered disk reads: 222 MB in 3.02 seconds =
73.59 MB/sec
As one can see, current udma mode is marked correctly by a star, which
is missing in the first example.
So the so called "Independent Device Timing" seems to be supported by
the chipset (NForce4 Ultra), otherwise the harddisk drive should run
udma2 in the first example, which it doesn't.
More testing can be done if wished.
-- System Information:
Debian Release: testing/unstable
APT prefers stable
APT policy: (900, 'stable'), (400, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-386
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages hdparm depends on:
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
hdparm recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
