Hello,
I'm having problems with the performance of my harddrives after I
upgraded my kernel from 2.2.17 to 2.2.18.
The performancedrop is noticable on every IDE drive.
Here are some numbers to show what I mean:
2.2.17:
/dev/hdc:
Timing buffered disk reads: 64 MB in 4.32 seconds =14.81 MB/sec
2.2.18:
/dev/hdc:
Timing buffered disk reads: 64 MB in 10.49 seconds = 6.10 MB/sec
These are hdparm -t outputs and the performance drop is pretty noticable
:-/
I also copied a 600Mb file from my HDD to /dev/null and the results
were:
2.2.17: 1 minute 9 seconds
2.2.18: 1 minute 38 seconds
My system consists of:
FIC VA-503+ motherboard with the MVP3 chipset
K6-2 500MHz
128Mb SDRAM
3 IDE disks (see below)
Slackware 7.0
dmesg output for the IDE system (no differences between .17 and .18):
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xe400-0xe407, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xe408-0xe40f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALL ST6.4A, ATA DISK drive
hdb: QUANTUM FIREBALL SE4.3A, ATA DISK drive
hdc: IBM-DJNA-352030, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: QUANTUM FIREBALL ST6.4A, 6149MB w/81kB Cache, CHS=784/255/63
hdb: QUANTUM FIREBALL SE4.3A, 4110MB w/80kB Cache, CHS=524/255/63
hdc: IBM-DJNA-352030, 19470MB w/1966kB Cache, CHS=39560/16/63
When I performed the tests I used similiar .17 and .18 kernels with a
minimum components included. No network, SCSI, sound and such things.
.config files can be supplied if needed.
Does anyone know what could be wrong? Have I forgot something? Is this a
known problem with the 2.2.18 kernel?
Thanks in advance!
Robert
On Wed, 20 Dec 2000, Robert H?gberg wrote:
> I'm having problems with the performance of my harddrives after I
> upgraded my kernel from 2.2.17 to 2.2.18.
> The performancedrop is noticable on every IDE drive.
[snip]
> Does anyone know what could be wrong? Have I forgot something? Is this a
> known problem with the 2.2.18 kernel?
Is DMA enabled on the hard drives?
Did you turn on "Use DMA by default" in the kernel configuration?
Did you compile in DMA support (if needed)?
What is the output of "hdparm /dev/hda /dev/hdb /dev/hdc" ?
Rob Adamson.
Hello,
On Wed, 20 Dec 2000, Robert H?gberg wrote:
> hda: QUANTUM FIREBALL ST6.4A, 6149MB w/81kB Cache, CHS=784/255/63
> hdb: QUANTUM FIREBALL SE4.3A, 4110MB w/80kB Cache, CHS=524/255/63
> hdc: IBM-DJNA-352030, 19470MB w/1966kB Cache, CHS=39560/16/63
>
> When I performed the tests I used similiar .17 and .18 kernels with a
> minimum components included. No network, SCSI, sound and such things.
> .config files can be supplied if needed.
>
> Does anyone know what could be wrong? Have I forgot something? Is this a
> known problem with the 2.2.18 kernel?
Yes, 2.2.18 is not friendly to all MVP3 users. The autodma
detection was disabled for the all *VP3 users in drivers/block/ide-pci.c.
If you don't experience any problems with the DMA you can:
1. Add append="ide0=dma ide1=dma" in lilo.conf
2. Use ide patches:
http://www.kernel.org/pub/linux/kernel/people/hedrick/ide-2.2.18/ide.2.2.18.1209.patch.bz2
Regards
--
Julian Anastasov <[email protected]>
> > known problem with the 2.2.18 kernel?
>
> Yes, 2.2.18 is not friendly to all MVP3 users. The autodma
> detection was disabled for the all *VP3 users in drivers/block/ide-pci.=
> c.
Because it was causing disk corruption for some people. It took a lot of
tracking down and I want the shipped kernel safe. I now know I'm covering too
many chip versions so 2.2.19 I can get the later VP3's back okay
On Wed, 20 Dec 2000, Julian Anastasov wrote:
>> hda: QUANTUM FIREBALL ST6.4A, 6149MB w/81kB Cache, CHS=784/255/63
>> hdb: QUANTUM FIREBALL SE4.3A, 4110MB w/80kB Cache, CHS=524/255/63
>> hdc: IBM-DJNA-352030, 19470MB w/1966kB Cache, CHS=39560/16/63
>>
>> When I performed the tests I used similiar .17 and .18 kernels with a
>> minimum components included. No network, SCSI, sound and such things.
>> .config files can be supplied if needed.
>>
>> Does anyone know what could be wrong? Have I forgot something? Is this a
>> known problem with the 2.2.18 kernel?
>
> Yes, 2.2.18 is not friendly to all MVP3 users. The autodma
>detection was disabled for the all *VP3 users in drivers/block/ide-pci.c.
>
> If you don't experience any problems with the DMA you can:
>
>1. Add append="ide0=dma ide1=dma" in lilo.conf
>
>2. Use ide patches:
>
>http://www.kernel.org/pub/linux/kernel/people/hedrick/ide-2.2.18/ide.2.2.18.1209.patch.bz2
Using an MVP3 board (DFI), 2.2.18 + the above patch, with the
above mentioned config changes, DMA by default, and word93
invalidate enabled, I just enabled UDMA66 on my 2 drives and got
disk corruption.
Both drives are UDMA66 or better, and I'm using the 80 pin cable.
2 root@asdf:~# hdparm -i /dev/hd[ab]
/dev/hda:
Model=IBM-DTLA-307030, FwRev=TX4OA50C, SerialNo=YKDYKGF1437
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16,
MultSect=16
CurCHS=16383/16/63, CurSects=-66060037, LBA=yes,
LBAsects=60036480
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 udma0 udma1 *udma2 udma3 udma4
udma5
/dev/hdb:
Model=QUANTUM FIREBALL EL7.6A, FwRev=A08.1100,
SerialNo=347816714615
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=15907/15/63, TrkSize=32256, SectSize=21298, ECCbytes=4
BuffType=DualPortCache, BuffSize=418kB, MaxMultSect=16,
MultSect=16
CurCHS=15907/15/63, CurSects=1597178085, LBA=yes,
LBAsects=15032115
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1
*udma2
Using "hdparm -d1X66" on these drives results in errors to syslog
followed by disk corruption. With word93 thingie NOT built into
the kernel, the corruption doesn't occur, but instead I get a
message saying UDMA 3/4/5 is not supported. It also claims the
MVP3 chipset is UDMA-33 only, whereas all relevant docs I can
muster including the mobo manual state the board is UDMA-66
capable. Mental note to myself: Do not enable WORD93 invalidate.
;o)
I've never seen UDMA66 work at all on any mobo/disk combo yet
that I've tried. My belief has been that the mobo/chipsets are
broken, and Andre's code just disables stuff known to be crap
hardware. Forcing it as I did, resulted in corruption, so I'll
tend to believe the driver next time and not push the issue. ;o)
Andre, is MVP3 capable of UDMA66 in any way shape or form, or
should I just drop the thought of ever getting it to work and buy
an add-in board? If the latter, what recommendation of hardware
would you give?
I'm getting 11 - 12Mb/s out of my disks now with the IDE patches,
which is a MAJOR improvement over the stock kernel. I'd like to
push this up closer to the drive's rated capacities though.
I'd also like to be able to use whatever kernel I want without
using vendor supplied binary-only modules for IDE support.
Is there a totally open-source solution for me? ;o)
Would I get better results at all with 2.4.0testXX, with or
without any patches, and what value of XX?
TIA
----------------------------------------------------------------------
Mike A. Harris - Linux advocate - Open source advocate
This message is copyright 2000, all rights reserved.
Views expressed are my own, not necessarily shared by my employer.
----------------------------------------------------------------------
Red Hat FAQ tip: Having trouble upgrading RPM 3.0.x to RPM 4.0.x? Upgrade
first to version 3.0.5, and then to 4.0.x. All packages are available on
Red Hat's ftp sites: ftp://ftp.redhat.com ftp://rawhide.redhat.com
On Thu, 21 Dec 2000, Alan Cox wrote:
>Date: Thu, 21 Dec 2000 00:49:45 +0000 (GMT)
>From: Alan Cox <[email protected]>
>To: Julian Anastasov <[email protected]>
>Cc: Robert H?gberg <[email protected]>,
> linux-kernel <[email protected]>
>Content-Type: text/plain; charset=us-ascii
>Subject: Re: Extreme IDE slowdown with 2.2.18
>
>> > known problem with the 2.2.18 kernel?
>>
>> Yes, 2.2.18 is not friendly to all MVP3 users. The autodma
>> detection was disabled for the all *VP3 users in drivers/block/ide-pci.=
>> c.
>
>Because it was causing disk corruption for some people.
I wish I read this email 24 hours ago. ;o(
>It took a lot of tracking down and I want the shipped kernel
>safe. I now know I'm covering too many chip versions so 2.2.19
>I can get the later VP3's back okay
Any info I can provide to help with my corruption problem
enabling UDMA?
00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo
MVP3] (rev 04)
Flags: bus master, medium devsel, latency 16
Memory at d8000000 (32-bit, prefetchable)
Capabilities: [a0] AGP version 1.0
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3
AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Apollo
PRO] (rev 23)
Subsystem: VIA Technologies, Inc. VT82C596/A/B PCI to ISA
Bridge
Flags: bus master, stepping, medium devsel, latency 0
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE
[Apollo] (rev 10) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 32
I/O ports at e000
Capabilities: [c0] Power Management version 2
00:07.3 Host bridge: VIA Technologies, Inc.: Unknown device 3050
(rev 30)
Flags: medium devsel
Dunno if that helps...
----------------------------------------------------------------------
Mike A. Harris - Linux advocate - Open source advocate
This message is copyright 2000, all rights reserved.
Views expressed are my own, not necessarily shared by my employer.
----------------------------------------------------------------------
Red Hat FAQ tip: Having trouble upgrading RPM 3.0.x to RPM 4.0.x? Upgrade
first to version 3.0.5, and then to 4.0.x. All packages are available on
Red Hat's ftp sites: ftp://ftp.redhat.com ftp://rawhide.redhat.com
Mike A. Harris wrote:
[snip]
> message saying UDMA 3/4/5 is not supported. It also claims the
> MVP3 chipset is UDMA-33 only, whereas all relevant docs I can
> muster including the mobo manual state the board is UDMA-66
> capable. Mental note to myself: Do not enable WORD93 invalidate.
> ;o)
I'm somewhat tired and busy, so I'll post URLs without quoting anything
from them (look at the data in *all* of them, and connect the dots, before
you come to any conclusions). Short version of the story: Some MVP3's
support UDMA-66, some don't -- it depends on the southbridge. 596B & 686A
do, others don't.
http://www.via.com.tw/news/98mvp3nr.htm
http://www.via.com.tw/products/prodmvp3.htm
http://www.via.com.tw/support/faq.htm#ide
-Barry K. Nathan <[email protected]>
On Wed, 20 Dec 2000, Barry K. Nathan wrote:
>[snip]
>> message saying UDMA 3/4/5 is not supported. It also claims the
>> MVP3 chipset is UDMA-33 only, whereas all relevant docs I can
>> muster including the mobo manual state the board is UDMA-66
>> capable. Mental note to myself: Do not enable WORD93 invalidate.
>> ;o)
>
>I'm somewhat tired and busy, so I'll post URLs without quoting anything
>from them (look at the data in *all* of them, and connect the dots, before
>you come to any conclusions). Short version of the story: Some MVP3's
>support UDMA-66, some don't -- it depends on the southbridge. 596B & 686A
>do, others don't.
>
>http://www.via.com.tw/news/98mvp3nr.htm
>http://www.via.com.tw/products/prodmvp3.htm
>http://www.via.com.tw/support/faq.htm#ide
Thanks for the info! Here is the most relevant portion I found:
* Q: Which VIA Chipsets support UDMA 66?
A: For UDMA 66 you must first make sure that you're southbridge is
either VT82C596B or VT82C686A. You must also have a UDMA 66
capable hard drive and be using an 80 pin cable which enables
faster transmission of data. Windows 98 is UDMA 66 enabled, but if
you have Win95 you should install our busmaster drivers.
Here is my mobo info:
2 root@asdf:~# lspci -v
00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)
Flags: bus master, medium devsel, latency 16
Memory at d8000000 (32-bit, prefetchable)
Capabilities: [a0] AGP version 1.0
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Apollo PRO] (rev 23)
Subsystem: VIA Technologies, Inc. VT82C596/A/B PCI to ISA Bridge
Flags: bus master, stepping, medium devsel, latency 0
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 32
I/O ports at e000
Capabilities: [c0] Power Management version 2
00:07.3 Host bridge: VIA Technologies, Inc.: Unknown device 3050 (rev 30)
Flags: medium devsel
Clear as mud. Board docs say it does ATA66, so I am assuming it
is the VT82C596B model. lspci doesn't appear to know which it is
though. The numbers on the chip itself are:
VT82C596B
^
Thus indicating from all the info I've collected so far, that my
hardware setup according to docs, is ata66.
My drive is ATA100 capable so that is no problem. 80 conductor
cable...
12Mb/s on drive rated 37Mb/s sustained.. ;o(
Without Andre's fine IDE patches I get 5Mb/s... 12M/s is better
than 5.
Getting 1/2 of the hardware specs rated values would even be
nice... I think it is shoddy hardware with made up specs
myself.. makes a good sell to people... ;o)
----------------------------------------------------------------------
Mike A. Harris - Linux advocate - Open source advocate
This message is copyright 2000, all rights reserved.
Views expressed are my own, not necessarily shared by my employer.
----------------------------------------------------------------------
If you're interested in computer security, and want to stay on top of the
latest security exploits, and other information, visit:
http://www.securityfocus.com