[snafuu] kernel frustrations

  • From: phrostie <pfrostie@xxxxxxxxx>
  • To: ale@xxxxxxx, snafuu@xxxxxxxxxxxxx
  • Date: Mon, 01 Apr 2002 07:57:15 -0500

long ago i'd switched from a 2.4 kernel back to a 2.2 because the 2.4 was 
giving me all sorts of drive errors.  last night i upgraded because i'd been 
told that 2.4 has better sound support.  

i'm getting the drive errors again.  i'd hoped they'd been fixed.
this drive worked flawless under 2.2, and the vender diagnostics show it to 
be good.  how can this be fixed.  i can't go back to 2.2 forever

Apr  1 07:32:29 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:32:29 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:32:32 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:32:32 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:35:09 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:35:09 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:00 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:00 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:00 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:00 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:00 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:00 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:02 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:02 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:12 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:12 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:12 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:12 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:12 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:12 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:12 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:12 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:12 galveston kernel: hdb: DMA disabled                           
                                                 
Apr  1 07:36:12 galveston kernel: ide0: reset: success                        
                                                 
Apr  1 07:36:12 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:12 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:43 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:43 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:43 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:43 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:43 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:43 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:36:43 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:36:43 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:38:02 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:38:02 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:38:47 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:38:47 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }                                        
Apr  1 07:38:48 galveston kernel: hda: dma_intr: status=0x51 { DriveReady 
SeekComplete Error }                                 
Apr  1 07:38:48 galveston kernel: hda: dma_intr: error=0x84 { 
DriveStatusError BadCRC }
-- 
Oh, I have slipped the surly bonds of DOS,
and danced the skies on Linux silvered wings.
http://pfrostie.freeservers.com/cad-tastrafy/
//www.freelists.org/list/cad-linux

Other related posts:

  • » [snafuu] kernel frustrations