On Wed, 2003-03-12 at 17:29, Tom Allison wrote:
> I've been runnign this PC for about a year now.
> I recently upgraded from 2.4.18 to 2.4.20.
> And this is the thanks I get....
> Any suggestions? It seems to work.
> --------------------------------------------------------------------
> Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
> DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
> status=0x51 { DriveReady
> SeekCompleteError }
> Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
> DriveStatusError BadCRC }Mar 12 12:14:21 gandolf kernel: hda: dma_intr:
> status=0x51 { DriveReady
> SeekCompleteError }
> Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
> DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
> status=0x51 { DriveReady
> SeekCompleteError }
> Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
> DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
> status=0x51 { DriveReady
> SeekCompleteError }
> Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
> DriveStatusError BadCRC }Mar 12 12:17:32 gandolf kernel: hda: dma_intr:
> status=0x51 { DriveReady
> SeekCompleteError }
> Mar 12 12:17:32 gandolf kernel: hda: dma_intr: error=0x84 {
> DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
> status=0x51 { DriveReady
> SeekCompleteError }
> Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
> DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
> status=0x51 { DriveReady
> SeekCompleteError }
> Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
> DriveStatusError BadCRC }Mar 12 12:26:18 gandolf kernel: hda: dma_intr:
> status=0x51 { DriveReady
> SeekCompleteError }
> Mar 12 12:26:18 gandolf kernel: hda: dma_intr: error=0x84 {
> DriveStatusError BadCRC }Mar 12 12:32:35 gandolf kernel: hda: dma_intr:
> status=0x51 { DriveReady
> SeekCompleteError }
> Mar 12 12:32:35 gandolf kernel: hda: dma_intr: error=0x84 {
> DriveStatusError BadCRC }Mar 12 12:32:35 gandolf kernel: hda: dma_intr:
> status=0x51 { DriveReady
> SeekCompleteError }
>
>
>
> --
> Boling's postulate:
> If you're feeling good, don't worry. You'll get over it.
While there is maybe a chance that you have a badly configured selection
of routines for accessing the hda's filesystems, it looks far more like
YouNeedToBackupEverythingAndGetANewPhysicalDriveInThatBoxNow.
Maybe you could have something missing about dma access or maybe even
confused irq assignments, but even if that is the case, your filesystems
could be in the midst of being shredded if there is any active writing
to those partitions.
If you go back to 2.4.18, are you getting any such messages?
--
Mark L. Kahnt, FLMI/M, ALHC, HIA, AIAA, ACS, MHP
ML Kahnt New Markets Consulting
Tel: (613) 531-8684 / (613) 539-0935
Email: kahnt@hosehead.dyndns.org
Attachment:
signature.asc
Description: This is a digitally signed message part