VIA686A chipset crash under 2.4.2-ac20
Kernel 2.4.2 with ac20 patch seems doesn't like my motherboard I have FIC SD11 with VIA686A chipset. I compiled it with support of VIA82Cxxx and DMA support by default. First it seemed like work but after a while I started to get errors like these:
kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Before I compiled kernel 2.4.2 without ac patches and got the same errors.
HDD Fujitsu MPE3136AT.
Here is a part of config file for kernel (only set variables)
#
# ATA/IDE/MFM/RLL support
#CONFIG_IDE=y
#
# IDE, ATA and ATAPI Block devices
#CONFIG_BLK_DEV_IDE=yCONFIG_BLK_DEV_IDEDISK=yCONFIG_IDEDISK_MULTI_MODE=yCONFIG_BLK_DEV_IDECD=y
#
# IDE chipset support/bugfixes
#CONFIG_BLK_DEV_IDEPCI=yCONFIG_IDEPCI_SHARE_IRQ=yCONFIG_BLK_DEV_IDEDMA_PCI=yCONFIG_IDEDMA_PCI_AUTO=yCONFIG_BLK_DEV_IDEDMA=yCONFIG_BLK_DEV_VIA82CXXX=yCONFIG_IDEDMA_AUTO=yCONFIG_BLK_DEV_IDE_MODES=y
Quoted 8 lines · On Thu, 15 Mar 2001, kozkir-8 wrote:
Kernel 2.4.2 with ac20 patch seems doesn't like my motherboard I have FIC SD11 with VIA686A chipset. I compiled it with support of VIA82Cxxx and DMA support by default. First it seemed like work but after a while I started to get errors like these:
kernel: hda:
dma_intr: status=0x51 { DriveReady SeekComplete Error }
kernel: hda:dma_intr: error=0x84 { DriveStatusError BadCRC }
I am so tired of this report, I am about to hide these in a /dev/null It is a nothing message. And if the via-core is correct it will auto down grade the trnasfer rate and you will not feel any effect. Only a marginally slow disk service.
Quoted 32 lines
Before I compiled kernel 2.4.2 without ac patches and got the same errors.
HDD Fujitsu MPE3136AT.
Here is a part of config file for kernel (only set variables)
#
# ATA/IDE/MFM/RLL support
#CONFIG_IDE=y#
# IDE, ATA and ATAPI Block devices
#CONFIG_BLK_DEV_IDE=yCONFIG_BLK_DEV_IDEDISK=yCONFIG_IDEDISK_MULTI_MODE=yCONFIG_BLK_DEV_IDECD=y#
# IDE chipset support/bugfixes
#CONFIG_BLK_DEV_IDEPCI=yCONFIG_IDEPCI_SHARE_IRQ=yCONFIG_BLK_DEV_IDEDMA_PCI=yCONFIG_IDEDMA_PCI_AUTO=yCONFIG_BLK_DEV_IDEDMA=yCONFIG_BLK_DEV_VIA82CXXX=yCONFIG_IDEDMA_AUTO=yCONFIG_BLK_DEV_IDE_MODES=y
Quoted 6 lines
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-----------------------------------------------------------------------------
ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035 Web: www.aslab.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5
It wouldn't be a problem if after these messages fsck wouldn't have found errors in FS.
AH> I am so tired of this report, I am about to hide these in a /dev/null AH> It is a nothing message. And if the via-core is correct it will auto down AH> grade the trnasfer rate and you will not feel any effect. Only a AH> marginally slow disk service.
- --
Best regards,
Kirill Kozmin
-----BEGIN PGP SIGNATURE-----
Version: 2.6
iQCVAwUAOrJaHj5SQymVx3NvAQE1NQP6A3Pm9X3EPpOERs6xoTnpc0UpBb5F+l01 sfzZmqodu4FGvGriFTUAbZNNtrPcE4os9dcnxjHtlfyW4PZ+YyWUjtIekx1ZdbLI I21hwuA2dA+lyLM5jaAS3aC5mPzfauVMRIbozegtPnaQViWUShSM8x1XWHtsQFBy iam5xbL8gXo=
=Qxq1
-----END PGP SIGNATURE-----
Okay not to worry, I now have a my hands on a VIA 686B and will look at the changes that happened to the VIA686A
Have you run 2.2.18 plus my patches off kernel.org?
Quoted 21 lines · On Fri, 16 Mar 2001, kozkir-8 wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5It wouldn't be a problem if after these messages fsck wouldn't have found errors in FS.
AH> I am so tired of this report, I am about to hide these in a
/dev/nullAH> It is a nothing message. And if the via-core is correct it will auto down AH> grade the trnasfer rate and you will not feel any effect. Only a AH> marginally slow disk service.- --
Best regards,
Kirill Kozmin-----BEGIN PGP SIGNATURE-----
Version: 2.6
Quoted 8 lines
iQCVAwUAOrJaHj5SQymVx3NvAQE1NQP6A3Pm9X3EPpOERs6xoTnpc0UpBb5F+l01 sfzZmqodu4FGvGriFTUAbZNNtrPcE4os9dcnxjHtlfyW4PZ+YyWUjtIekx1ZdbLI I21hwuA2dA+lyLM5jaAS3aC5mPzfauVMRIbozegtPnaQViWUShSM8x1XWHtsQFBy iam5xbL8gXo=
=Qxq1
-----END PGP SIGNATURE-----
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-----------------------------------------------------------------------------
ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035 Web: www.aslab.com
Quoted 5 lines · Andre Hedrick
Okay not to worry, I now have a my hands on a VIA 686B and will look at the changes that happened to the VIA686A
Have you run 2.2.18 plus my patches off kernel.org?
No, I didn't run it. Whould I?
--
**************************
Sincerely yours
Kirill Kozmin
E-mail:[email protected]
Homepage:www.ludd.luth.se/~kozkir-8/
**************************
Yes you should try because there is a fundamental difference in design of VIA between 2.2.x + patches and 2.4.x
Quoted 13 lines · Kirill Kozmin
Quoted 5 lines · Andre Hedrick
Okay not to worry, I now have a my hands on a VIA 686B and will look at the changes that happened to the VIA686A
Have you run 2.2.18 plus my patches off kernel.org?
No, I didn't run it. Whould I?
--
**************************
Quoted 10 lines
Sincerely yours
Kirill KozminE-mail:[email protected]
Homepage:www.ludd.luth.se/~kozkir-8/
**************************
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-----------------------------------------------------------------------------
ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035 Web: www.aslab.com
Quoted 5 lines · Andre Hedrick
Okay not to worry, I now have a my hands on a VIA 686B and will look at the changes that happened to the VIA686A
Have you run 2.2.18 plus my patches off kernel.org?
Ok, now its clear that I have a big troubles with hardware.
I compiled kernel 2.2.18+IDE_patches with support for VIA chipset and still get errors of type:
kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
before these kernel reports a long string of messages
kernel: hda: Write Cache SUCCESSED Flushing!<6>hda: Write Cache....
Probably it's not a question for this list but what should I do and how can I determinate broken hardware? (Or configuration? I still hope that it's not a hardware)
//Kirill
VIA686b chipset and dma_intr errors, and 3c905B errors
In reply to Andre HedrickQuoted 10 lines
Ok, now its clear that I have a big troubles with hardware.
I compiled kernel 2.2.18+IDE_patches with support for VIA chipset and still get errors of type:kernel: hda:
dma_intr: status=0x51 { DriveReady SeekComplete Error }
kernel: hda:dma_intr: error=0x84 { DriveStatusError BadCRC }before these kernel reports a long string of messages
I got those errors on a brand new IBM ATA100 drive. I exchanged it for a new one which worked fine for a couple of weeks, but now the new one is beginning to give me the same errors. I've noticed a rash of people reporting these errors since 2.4.x. Is it really that the new kernel is simply better at reporting bad drives? Or is there something else going on with the kernel? (Or are IBM drives just crappy?)
Here's a portion of the messages I'm getting...
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error}
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=48973752, sector=1854944end_request: I/O error, dev 03:08 (hda), sector 1854944
asus a7v/kt133
IDE is Via 686b
By the way, my 3c905B went bahooties since about ac21 I think. I was under the impression that Alan backed out of the suspected changes for ac23 but the problem remained. I replaced it with an eepro100, but I don't know if it's the card or what.
-Nick
Signature · 5 lines
********************************************************** Nicholas Petreley Caldera Systems - LinuxWorld/InfoWorld [email protected] - http://www.petreley.com - Eph 6:12 ********************************************************** .
Re: VIA686b chipset and dma_intr errors, and 3c905B errors
In reply to Andre HedrickUpdate:
Thanks to some advice and help from Mark Hahn, I downloaded the DFT utility from IBM that checks and fixes their drives. A low-level format fixed the problems (the utility calls it "erase disk". That seems odd to me, since I thought that IDE drives automatically took care of bad blocks, but apparently this needed the low-level format. I'll keep an eye on that drive, though...
As for the 3C905B, I've already replaced it with an eepro100, but as Mark suggested in an email, I will turn off the "optimal" performance setting in the BIOS and see if that gets rid of all the bizarre behavior. Apparently that's not a kernel problem but a bios problem.
-Nick
Signature · 5 lines
********************************************************** Nicholas Petreley Caldera Systems - LinuxWorld/InfoWorld [email protected] - http://www.petreley.com - Eph 6:12 ********************************************************** .
VIA686B + 2.2.18 (was: VIA686A chipset crash under 2.4.2-ac20)
In reply to kozkir-8Quoted 5 lines · Andre Hedrick
Okay not to worry, I now have a my hands on a VIA 686B and will look at the changes that happened to the VIA686A
Have you run 2.2.18 plus my patches off kernel.org?
Hi Andre,
I'm running 2.2.18 on VIA686B (ABit VP6). Some time ago, you mentioned that you got ~80Mb/s from 'hdparm -t /dev/hda'. Please tell us how? Which hdparm/kernel options did you enable?
:wq --William Park, Open Geometry Consulting, Linux/Python, 8 CPUs.
Re: VIA686B + 2.2.18 (was: VIA686A chipset crash under 2.4.2-ac20)
Quoted 3 lines · William Park
I'm running 2.2.18 on VIA686B (ABit VP6). Some time ago, you mentioned that you got ~80Mb/s from 'hdparm -t
/dev/hda'. Please tell us how? Which hdparm/kernel options did you enable?
Nope not w/ 'hdparm' with DiskPerf and correcting for CR3's on memcpy's.
[root@via DiskPerf-1.0.3]# ./DiskPerf /dev/hda
Device: IBM-DTLA-307030 Serial Number: YKDYKM37674
LBA 0 DMA Read Test = 56.62 MB/Sec (4.42 Seconds) Outer Diameter Sequential DMA Read Test = 35.46 MB/Sec (7.05 Seconds) Inner Diameter Sequential DMA Read Test = 17.72 MB/Sec (14.10 Seconds)
When you adjust for memory delays (of 35-40%) then you get those number. and those numbers are valid inside for kernel-kernel access, not kernel-user-space.
Cheers,
Andre Hedrick
Linux ATA Development