From: David Ronis <ronis@ronispc.chem.mcgill.ca>
To: Jean Delvare <khali@linux-fr.org>
Cc: David Ronis <David.Ronis@mcgill.ca>,
LKML <linux-kernel@vger.kernel.org>,
Parag Warudkar <kernel-stuff@comcast.net>,
linux-ide@vger.kernel.org
Subject: Re: problem with 2.6.13.[0-2]
Date: Thu, 29 Sep 2005 17:26:58 -0400 [thread overview]
Message-ID: <1128029218.15252.16.camel@montroll.chem.mcgill.ca> (raw)
In-Reply-To: <20050929082048.0cca3f58.khali@linux-fr.org>
Hi Jean,
I'm sending this to the linux-ide list as suggested, so first a very
brief summary of the problem:
I'm running a hp pavillion ZV5240ca laptop. The kernel
has the ATIIXP driver installed, and this is what is
loaded for the hard-drive (according to lshw). On
upgrading from 2.6.12.6 to 2.6.13.[0-2] I noticed a huge
slowdown in disk performance (see below for timings) and
have been getting some help tracking the problem down on
the linux-kernel list. (I don't subscribe to either
list so please CC me).
Ok, bakc to Jean. I tried your suggestion; here's what I get running
hdparm -i /dev/hda
On 2.6.12.6:
/dev/hda:
Model=ST9100823A, FwRev=3.00, SerialNo=3LG0V6AP
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=195371568
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
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2:
* signifies the current active mode
On 2.6.13.2:
/dev/hda:
Model=ST9100823A, FwRev=3.00, SerialNo=3LG0V6AP
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=195371568
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
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2:
* signifies the current active mode
They are identical except for the MultSect field (which was already
apparent from the simple hdparm output). As I wrote earlier, I tried
changing it to 16 in 2.6.13.2, but it made a next to no change in the
timings.
I will post the full dmesg output next time I reboot, but greping for
hda or ide0 shows nothing out of the ordinary, at least to me.
David
On Thu, 2005-09-29 at 08:20 +0200, Jean Delvare wrote:
> Hi David,
>
> [David Ronis]
> > In 2.6.12.6:
> >
> > /dev/hda:
> > Timing cached reads: 1140 MB in 2.00 seconds = 569.80 MB/sec
> > Timing buffered disk reads: 102 MB in 3.02 seconds = 33.80 MB/sec
> >
> > In 2.6.13.2:
> >
> > /dev/hda:
> > Timing cached reads: 28 MB in 2.15 seconds = 13.03 MB/sec
> > Timing buffered disk reads: 14 MB in 3.30 seconds = 4.24 MB/sec
> >
> > and after hdparm -m 16 /dev/hda (recall this is the default in 2.6.12.6)
> >
> > /dev/hda:
> > Timing cached reads: 24 MB in 2.05 seconds = 11.73 MB/sec
> > Timing buffered disk reads: 36 MB in 3.11 seconds = 11.56 MB/sec
> >
> > I ran thing a few times in each case and the results were close. There
> > was nothing in dmesg.
>
> Try hdparm -i /dev/hda on both kernels, this will tell you the
> controller/drive operation mode:
>
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2
> UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
> * signifies the current active mode
>
> I expect you to find that your IDE controller is in UDMA mode on
> 2.6.12.6 but not on 2.6.13.2. The figures you obtain for the latter
> suggest mdma2 (those max throughput is 16 MB/sec IIRC) at best.
>
> If I'm right, then you will have to find out which driver your IDE
> controller uses, and why it decided that UDMA was no good for your
> controller/driver combination. You may want to try the linux-ide list
> for a more assistance, my own knowledge of that matter stops here ;)
>
next prev parent reply other threads:[~2005-09-29 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 2:55 problem with 2.6.13.[0-2] Parag Warudkar
2005-09-29 1:37 ` David Ronis
2005-09-29 6:20 ` Jean Delvare
2005-09-29 21:26 ` David Ronis [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-29 4:13 kernel-stuff
2005-09-25 18:24 David Ronis
[not found] ` <20050926005531.90DF42E0018@asmx1.McGill.CA>
2005-09-27 2:34 ` David Ronis
2005-09-29 10:29 ` Bartlomiej Zolnierkiewicz
2005-09-29 21:34 ` David Ronis
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=1128029218.15252.16.camel@montroll.chem.mcgill.ca \
--to=ronis@ronispc.chem.mcgill.ca \
--cc=David.Ronis@mcgill.ca \
--cc=kernel-stuff@comcast.net \
--cc=khali@linux-fr.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).