🚀 go-pugleaf

Datagram from dj incoming on netlink socket
<3e9bfef1$0$22053$afc38c87@news.optusnet.com.au>. Dumping datagram.
> It is captured during system boot.......I have no idea what's going on with
> it.
> 
> Starting innd.
> 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

These look like ones you get when you try to enable DMA on buggy
chipset that can't properly support DMA... Especally if they only
come at boot, since I think Linux disables DMA if it seems to be
too dangerous to use. This causes slowdown, but one much rather
takes the slowdown than data corruption, which is the alternative.

This computer has motherboard with VIA chipset, right?

-Ilari
-- 
Quite frankly, I'd rather have no frogs at all in my blenders, thank 
you very much. -- Linus Torvalds
Linux LK_Perkele_IV9 2.4.20-lsm1 #7 Sun Jan 12 12:49:06 EET 2003 i686 unknown
  9:30pm  up 40 days,  1:26,  7 users,  load average: 0.11, 0.19, 0.20