dma error on startup

Corey Taylor lists at versaqual.com
Tue Dec 2 06:33:33 UTC 2003


Hi Chris, this sounds like this could be the problem. Thanks, I'll try
an 80 pin cable and report my results back to the list.

Corey

On Tue, 2003-12-02 at 01:28, Chris Sparks wrote:
> Hi Corey,
> 
> I get the first part on my system and from the research I have done it 
> comes from using
> a harddrive with UDMA capability with a 40 wire cable (40 pin).  Should 
> be using 80 wire cable (40 pin).,
> Does this make sense for you?
> 
> Chris
> 
> Corey Taylor wrote:
> 
> >Hi all. I get the following message on startup:
> >
> >Journalled Block Device driver loaded
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> >ide0: reset: success
> >
> >Is this a cause for concern. Does this mean I have a bad hard drive?
> >
> >Here's my lspci output:
> >
> >00:00.0 Host bridge: Intel Corp. 82820 820 (Camino) Chipset Host Bridge
> >(MCH) (rev 04)
> >00:01.0 PCI bridge: Intel Corp. 82820 820 (Camino) Chipset AGP Bridge
> >(rev 04)
> >00:1e.0 PCI bridge: Intel Corp. 82801AA PCI Bridge (rev 02)
> >00:1f.0 ISA bridge: Intel Corp. 82801AA ISA Bridge (LPC) (rev 02)
> >00:1f.1 IDE interface: Intel Corp. 82801AA IDE (rev 02)
> >00:1f.2 USB Controller: Intel Corp. 82801AA USB (rev 02)
> >00:1f.3 SMBus: Intel Corp. 82801AA SMBus (rev 02)
> >00:1f.5 Multimedia audio controller: Intel Corp. 82801AA AC'97 Audio
> >(rev 02)
> >01:00.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2
> >Model 64/Model 64 Pro] (rev 15)
> >02:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado]
> >(rev 78)
> >
> >The hard drive itself is a Seagate Barracuda ATA VII, IIRC. The kernel
> >identifies it as: hda: ST340014A, ATA DISK drive.
> >
> >Has anyone else observed this message? If so, can you interpret this for
> >me. Is this something I can fix through software, or is my drive
> >breaking down? Thanks in advance for any responses.
> >
> >Corey
> >
> >
> >
> >
> >
> >--
> >fedora-list mailing list
> >fedora-list at redhat.com
> >To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
> >
> >
> >  
> >
> 
> 
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
> 





More information about the fedora-list mailing list