Bug 67366
Summary: | (IDE)new error messages with Athlon 2.4.18-5 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | baulv | ||||
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> | ||||
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 7.3 | CC: | pawsa | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | athlon | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2003-06-27 22:19:55 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
baulv
2002-06-23 17:39:52 UTC
Created attachment 62264 [details]
/var/log/dmesg
Jun 23 12:36:49 w1 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } ehm that's a cable problem! ehm... and it still works? The old 2.4.18-4 kernel did not seem to mind my cable? I'll reseat it and report back. OK. cable was fine. But your ide(a) of cabling made me think. The the two drives I have on the primary IDE channel uses Cable SELect. When I changed the Cable SELect on both to MASTER and SLAVE respectively, the boot up error message disappeared. oops, the messages are back... Jun 26 19:00:31 w1 kernel: ROM checksum self-test: passed (0x3258698e). Jun 26 19:00:31 w1 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jun 26 19:00:31 w1 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Jun 26 19:00:31 w1 kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Jun 26 19:00:31 w1 kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Jun 26 19:00:32 w1 apmd[861]: Charge: * * * (-1% unknown) I'll try another cable. This is not a problem with a IDE cable. It is a problem with RH patches on top of stock kernel, as far as I can tell - see #71545. bug #71545 has been fixed and this may be closed as well (I seem not to have right to do that). I have a box with a WDC WD1000JB-00CRA1 100GB drive, and a VIA chipset, and have been getting these same errors once we upgraded to Redhat 7.3. After much futzing (BIOS uogrades, disabled cable-select, etc.) I upgraded to Redhat 8.0 and the errors still occur: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC } (thousands of these a day) However, there are two things I can do to reduce/stop these messages, but nither is fully acceptible: 1) force the WD drive to run in UDMA/33 mode (instead of UDMA/66). This reduces the errors to a handful a day, but cuts the performance from around 32MB/s to around 26MB/s. 2) disable DMA (hdparm -d 0 /dev/hda). This stops the errors, but cuts the performace down to around 6MB/s, ugh!! This is very frustrating. :( Here are the vitals: -------------------- [root@sparky rc3.d]# uname -a Linux sparky 2.4.20-13.8 #1 Mon May 12 11:48:50 EDT 2003 i686 athlon i386 GNU/Linux [root@sparky rc3.d]# /sbin/lspci 00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] System Controller (rev 25) 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] AGP Bridge (rev 01) 00:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 1b) 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 06) 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 0e) 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 20) 01:05.0 VGA compatible controller: ATI Technologies Inc Rage 128 RF/SG AGP ------------- [root@sparky rc3.d]# /sbin/hdparm -i /dev/hda dev/hda: Model=WDC WD1000JB-00CRA1, FwRev=17.07W17, SerialNo=WD-WMA8C3239128 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq } RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40 BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16 CurCHS=17475/15/63, CurSects=16513875, LBA=yes, LBAsects=195371568 IORDY=on/off, tPIO={min:120,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 AdvancedPM=no WriteCache=enabled Drive conforms to: device does not report version: 1 2 3 4 5 The original bug seems sorted. The later VIA report is unrelated and seems to be hardware noise. |