hda: dma_intr Problem with kernel 2.0.34 !

hda: dma_intr Problem with kernel 2.0.34 !

Post by DinosauR Mi » Fri, 03 Jul 1998 04:00:00



  After I compiled the linux kernel 2.0.34 and during
bootup, it displayed the following error !

  I tried to use the badblocks tools to check for
badblock, and the answer is "None of your disk have badblocks",
I haven't any problem with da 2.0.33 kernel, so I guess that this
is the bugs of the DMA module or somethings ! Am I right ?

  Anyone knew how can I fix this ?

-------------------------------------------------------------------------
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
hdc: [PTBL] [527/255/63] hdc1 hdc2 < hdc5 hdc6 hdc7 >
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 130748k swap-space (priority -1)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
hda: disabled DMA
ide0: reset: success
-------------------------------------------------------------------------

--
-----------------------------------
DinosauR MinG - Crazy LinuZer {*_*}
-----------------------------------

 
 
 

hda: dma_intr Problem with kernel 2.0.34 !

Post by DinosauR Mi » Fri, 03 Jul 1998 04:00:00




Quote:>   After I compiled the linux kernel 2.0.34 and during
> bootup, it displayed the following error !

>   I tried to use the badblocks tools to check for
> badblock, and the answer is "None of your disk have badblocks",
> I haven't any problem with da 2.0.33 kernel, so I guess that this
> is the bugs of the DMA module or somethings ! Am I right ?

>   Anyone knew how can I fix this ?

> -------------------------------------------------------------------------
> Partition check:
> hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
> hdc: [PTBL] [527/255/63] hdc1 hdc2 < hdc5 hdc6 hdc7 >
> VFS: Mounted root (ext2 filesystem) readonly.
> Adding Swap: 130748k swap-space (priority -1)
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
> hda: disabled DMA
> ide0: reset: success
> -------------------------------------------------------------------------

 All the damn error is during I overclock , I have a PII 233 --> 83x3 !!
 When the new kernel init the DMA of hda , the error occured, after I
 changed the externel bus clock back to 66 ! All worked fine !

--
-----------------------------------
DinosauR MinG - Crazy LinuZer {*_*}
-----------------------------------

 
 
 

1. hda: dma_intr Problem with kernel 2.0.34 !

  After I compiled the linux kernel 2.0.34 and during
bootup, it displayed the following error !

  I tried to use the badblocks tools to check for
badblock, and the answer is "None of your disk have badblocks",
I haven't any problem with da 2.0.33 kernel, so I guess that this
is the bugs of the DMA module or somethings ! Am I right ?

  Anyone knew how can I fix this ?

-------------------------------------------------------------------------
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
hdc: [PTBL] [527/255/63] hdc1 hdc2 < hdc5 hdc6 hdc7 >
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 130748k swap-space (priority -1)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { BadSector DriveStatusError }, LBAsect=546215, sector=2
hda: disabled DMA
ide0: reset: success
-------------------------------------------------------------------------

--
-----------------------------------
DinosauR MinG - Crazy LinuZer {*_*}
-----------------------------------

2. Netscape for Linux+term?

3. hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC )

4. identd usage

5. hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x84 { DriveStatusError BadCRC }

6. 3c90x 3Com drivers and 2.3.* kernels?

7. disk error: kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }

8. Firewall Needed for Linux

9. hda: dma_intr: status=0x51

10. hda: dma_intr: error=0x40

11. hda: dma_intr: error=0x84 { DriveStatusError BadCRC

12. Compiling Kernel 2.0.34 to Kernel 2.2.7

13. Kernel 2.0.34 module problems