2003-08-06 11:00:28

by Nick Sanders

[permalink] [raw]
Subject: IDE DMA problem with 2.6.0-test1

Hi,

I got the following from my logs this morning, any ideas whats happening.
Both hda and hdb are IDE hard drives. hdb is only used for backups and wasn't being
used at the time.

Aug 6 08:30:52 gandalf -- MARK --
Aug 6 08:31:37 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 6 08:31:37 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 6 08:31:40 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 6 08:31:40 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 6 08:32:16 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 6 08:32:16 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 6 08:32:24 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 6 08:32:24 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 6 08:32:26 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 6 08:32:26 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 6 08:32:26 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 6 08:32:26 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 6 08:32:26 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 6 08:32:26 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 6 08:32:26 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Aug 6 08:32:26 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Aug 6 08:32:26 gandalf kernel: hdb: DMA disabled
Aug 6 08:32:26 gandalf kernel: ide0: reset: success
Aug 6 08:50:52 gandalf -- MARK --

If you need anymore info then just say

Nick


Subject: Re: IDE DMA problem with 2.6.0-test1


Check your IDE cables.

On Wed, 6 Aug 2003, Nick Sanders wrote:

> Hi,
>
> I got the following from my logs this morning, any ideas whats happening.
> Both hda and hdb are IDE hard drives. hdb is only used for backups and wasn't being
> used at the time.
>
> Aug 6 08:30:52 gandalf -- MARK --
> Aug 6 08:31:37 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Aug 6 08:31:37 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> Aug 6 08:31:40 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Aug 6 08:31:40 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> Aug 6 08:32:16 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Aug 6 08:32:16 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> Aug 6 08:32:24 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Aug 6 08:32:24 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> Aug 6 08:32:26 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Aug 6 08:32:26 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> Aug 6 08:32:26 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Aug 6 08:32:26 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> Aug 6 08:32:26 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Aug 6 08:32:26 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> Aug 6 08:32:26 gandalf kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Aug 6 08:32:26 gandalf kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> Aug 6 08:32:26 gandalf kernel: hdb: DMA disabled
> Aug 6 08:32:26 gandalf kernel: ide0: reset: success
> Aug 6 08:50:52 gandalf -- MARK --
>
> If you need anymore info then just say
>
> Nick

2003-08-06 14:51:08

by Nick Sanders

[permalink] [raw]
Subject: Re: IDE DMA problem with 2.6.0-test1

On Wednesday 06 August 2003 3:07 pm, Bartlomiej Zolnierkiewicz wrote:
> Check your IDE cables.
>

As long as its not the drive that's great.

I'll get a new cable.

Thanks

Nick



Subject: Re: IDE DMA problem with 2.6.0-test1


You can also install smartmontools (http://smartmontools.sf.net/)
and check your drives (if they support SMART of course).

On Wed, 6 Aug 2003, Nick Sanders wrote:

> On Wednesday 06 August 2003 3:07 pm, Bartlomiej Zolnierkiewicz wrote:
> > Check your IDE cables.
>
> As long as its not the drive that's great.
>
> I'll get a new cable.
>
> Thanks
>
> Nick

2003-08-07 17:43:44

by Mike Castle

[permalink] [raw]
Subject: Re: IDE DMA problem with 2.6.0-test1

In article <[email protected]>,
Bartlomiej Zolnierkiewicz <[email protected]> wrote:
>
>You can also install smartmontools (http://smartmontools.sf.net/)
>and check your drives (if they support SMART of course).


Point of interest: I just had a Maxtor drive go bad on me recently. Their
diag tools caught it, as did my ear (made a nice clunking noise :-). But
SMART didn't report a thing, and I looked hard too. :-/

mrc

--
Mike Castle [email protected] http://www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc

Subject: Re: IDE DMA problem with 2.6.0-test1


Can be buggy drive's firmware or bug in smartmontools (unlikely)...

--bartlomiej

On Thu, 7 Aug 2003, Mike Castle wrote:

> In article <[email protected]>,
> Bartlomiej Zolnierkiewicz <[email protected]> wrote:
> >
> >You can also install smartmontools (http://smartmontools.sf.net/)
> >and check your drives (if they support SMART of course).
>
>
> Point of interest: I just had a Maxtor drive go bad on me recently. Their
> diag tools caught it, as did my ear (made a nice clunking noise :-). But
> SMART didn't report a thing, and I looked hard too. :-/
>
> mrc


2003-08-08 10:27:34

by Wes Janzen

[permalink] [raw]
Subject: Re: IDE DMA problem with 2.6.0-test1

I don't know, I've had a few SMART capable Maxtor drives go bad to the
point I knew it without a warning. Eventually, when things got really
bad though, they would report SMART errors. The errors were at first
intermittent, and then got to the point the warning wouldn't go away.
In their defense, two of them (I've had 5) had smart errors and I never
encountered any noticeable defects (still, I replaced them when they
were doing the upgrade program so I could get a new 3 year warranty).

All of those are several generations old though, the newer ones I have
now don't seem to want to die ;-)

--Wes--

Bartlomiej Zolnierkiewicz wrote:

>Can be buggy drive's firmware or bug in smartmontools (unlikely)...
>
>--bartlomiej
>
>On Thu, 7 Aug 2003, Mike Castle wrote:
>
>
>
>>In article <[email protected]>,
>>Bartlomiej Zolnierkiewicz <[email protected]> wrote:
>>
>>
>>>You can also install smartmontools (http://smartmontools.sf.net/)
>>>and check your drives (if they support SMART of course).
>>>
>>>
>>Point of interest: I just had a Maxtor drive go bad on me recently. Their
>>diag tools caught it, as did my ear (made a nice clunking noise :-). But
>>SMART didn't report a thing, and I looked hard too. :-/
>>
>>mrc
>>
>>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to [email protected]
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>