[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: DMA errors with hard disk



On Thu, 2004-10-28 at 13:24, VJ wrote:
> ----- Original Message ----- 
> From: "Jacob L E Blain Christen" <dweomer+fedora entheal com>
> To: "For users of Fedora Core releases" <fedora-list redhat com>
> Sent: Thursday, October 28, 2004 6:56 PM
> Subject: Re: DMA errors with hard disk
> 
> 
> > VJ wrote:
> >> Hi,
> >>     I get this error a lot of times, and I have tried looking at google 
> >> too
> >> without any solution(all I saw were postings of the problem). My System 
> >> is
> >> Gigabyte 7DXR. Kernel version is 2.6.8-1.521.
> >>     Has anybody found any solution to this problem?
> >> Thanks and regards from
> >> VJ
> >>
> >> ******************************* Result of lspci command
> >> 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
> >> (rev 40)
> >> 00:07.1 IDE interface: VIA Technologies, Inc.
> >> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
> >> 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 
> >> 40)
> >> [root dxr root]# lspci
> >> 00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] 
> >> System
> >> Controller (rev 13)
> >> 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] AGP
> >> Bridge
> >> 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
> >> (rev 40)
> >> 00:07.1 IDE interface: VIA Technologies, Inc.
> >> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
> >> 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 
> >> 40)
> >> 00:09.0 Multimedia video controller: Internext Compression Inc iTVC15 
> >> MPEG-2
> >> Encoder (rev 01)
> >> 00:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03)
> >> 00:0e.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
> >> 00:10.0 Unknown mass storage controller: Promise Technology, Inc. 20265 
> >> (rev
> >> 02)
> >> 01:05.0 VGA compatible controller: ATI Technologies Inc Rage 128 RF/SG 
> >> AGP
> >> 02:04.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] 
> >> (rev
> >> 05)
> >> 02:05.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] 
> >> (rev
> >> 05)
> >>
> >> *************************** Part of /var/log/messages
> >> kernel: hdb: dma_timer_expiry: dma status == 0x60
> >> kernel: hdb: DMA timeout retry
> >> kernel: hdb: timeout waiting for DMA
> >> kernel: hda: status timeout: status=0xd0 { Busy }
> >> kernel: hda: DMA disabled
> >> kernel: hda: drive not ready for command
> >> kernel: ide0: reset timed-out, status=0x80
> >> kernel: hdb: status error: status=0x34 { DeviceFault SeekComplete
> >> CorrectedError }
> >> kernel: hdb: no DRQ after issuing WRITE
> >> kernel: ide0: reset timed-out, status=0x80
> >> kernel: hdb: status error: status=0x34 { DeviceFault SeekComplete
> >> CorrectedError }
> >
> >
> > Have had this happen with some crappy hard drives I've run into over the
> > years.  Usually accompanies some loud clicking.  Chances are you are
> > trying to run in a DMA mode that the drive doesnt support, eg UDMA(100)
> > instead of UDMA(66) or the like.  Check your BIOS, if you have
> > configured your hard drives by hand you may have have a wrong setting.
> > Consider either letting your BIOS autodetect or passing values to the
> > kernel at boot time.  If this doesn't work I would like to see your
> > dmesg output, specifically where the kernel detects your drives and ide
> > controller(s).
> > --
> > Jacob
> >
> 
> 
> --------------------------------------------------------------------------------
> 
> 
> > -- 
> > fedora-list mailing list
> > fedora-list redhat com
> > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
> 
> 
> 
> Hi Jacob,
>     Thanks for reply. Hard disks are
> hda : ST340016A
> hdh : ST3160023A (was hdb)
> and they are pretty new. Today morning I moved hdb (the second hard disk to 
> prmise controller(i had it disabled first, but had to enable it today using 
> a jumper on the mobo. Now hdb is hdh)
> 
> Partial output of dmesg is at the end
> 
> *******************************************************
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> divert: not allocating divert_blk for non-ethernet device lo
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> VP_IDE: IDE controller at PCI slot 0000:00:07.1
> VP_IDE: chipset revision 6
> VP_IDE: not 100% native mode: will probe irqs later
> VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1
>     ide0: BM-DMA at 0xb000-0xb007, BIOS settings: hda:DMA, hdb:pio
>     ide1: BM-DMA at 0xb008-0xb00f, BIOS settings: hdc:DMA, hdd:DMA
> hda: ST340016A, ATA DISK drive
> Using cfq io scheduler
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hdc: LG DVD-ROM DRD-8120B, ATAPI CD/DVD-ROM drive
> hdd: LG CD-RW CED-8081B, ATAPI CD/DVD-ROM drive
> ide1 at 0x170-0x177,0x376 on irq 15
> PDC20265: IDE controller at PCI slot 0000:00:10.0
> ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 11 (level, low) -> IRQ 11
> PDC20265: chipset revision 2
> PDC20265: 100% native mode on irq 11
> PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
>     ide2: BM-DMA at 0xe000-0xe007, BIOS settings: hde:pio, hdf:pio
>     ide3: BM-DMA at 0xe008-0xe00f, BIOS settings: hdg:pio, hdh:DMA
> hdh: ST3160023A, ATA DISK drive
> ide3 at 0xd800-0xd807,0xdc02 on irq 11
> hda: max request size: 128KiB
> hda: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
>  hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
> hdh: max request size: 128KiB
> hdh: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, 
> UDMA(100)
>  hdh: hdh1 hdh2 hdh3 hdh4
> hdc: ATAPI 40X DVD-ROM drive, 512kB Cache, UDMA(33)
> Uniform CD-ROM driver Revision: 3.20
> hdd: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
> *******************************************************

What causes the "waiting for dma exit" error" ?  It doesn't happen often but it seem like FC2 can't read the drives.

Tim...

 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]