Hi,

First, thank you very much Mark, Tim, Jeremy and Holger for your continuing contributions which, I think, are at last casting some light on my "problem".

> Yes this is why I originally replied to the post... but he's not using a
> PIIXx at
> all,
> but the IDE chip on an Intel 815 motherboard.  I'm not sure if they use
> the same
> driver
> , but I don't think so.
> 

I found a helpful post from Peter Denison on 6th January this year which suggests that it is at least the same driver.

"Description:
Includes new PCI device IDs for the Intel i815E chipset, and corrects some
of the names for the associated parts of the chipset. This has effects in
the EEPro100 network driver and the PCI IDE driver.
Detail & Justification:
The Intel ICH2 (I/O Controller Hub 2) is used in several chipsets, not
just the 820 (Camino) chipset it is accredited to in the PCI ID database.
Nor is the IDE portion of the ICH2 really a PIIX4 chip, though it is very
similar and PIIX driver works on both. These changes are just
internal macro naming and minor user interface tweaks."


> try hdparm -t /dev/hda1 instead of hda5 (if those are on opposite ends
> of the
> disk)
> 
> include output of fdisk so we can see partition layout, and results of
> hdparm on
> different areas.

Here is my fdisk output :

Disk /dev/hda: 255 heads, 63 sectors, 3737 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1       932   7486258+   b  Win95 FAT32
/dev/hda2           933      3737  22531162+   5  Extended
/dev/hda5           933       935     24066   83  Linux
/dev/hda6           936       952    136521   82  Linux swap
/dev/hda7           953      3737  22370481   83  Linux


I also ran hdparm -tT /dev/hda1:

Timing buffer-cache reads:   128 MB in  1.28 seconds =100.00 MB/sec
 Timing buffered disk reads:  64 MB in  4.35 seconds = 14.71 MB/sec

Which obviously gives much the same result as my usual hdparm -tT /dev/hda

I then tried hdparm -tT /dev/hda7:

 Timing buffer-cache reads:   128 MB in  1.28 seconds =100.00 MB/sec
 Timing buffered disk reads:  64 MB in  2.12 seconds = 30.19 MB/sec

As you would expect, I get almost identical results with several repetitions.

Does this solve the mystery ?

Regards,

Geoff

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/