linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Axel Siebenwirth <axel@pearbough.net>
To: "Mudama, Eric" <eric_mudama@maxtor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.4.22-pre8-bk] dma_timer_expiry: dma status == 0x64
Date: Fri, 25 Jul 2003 21:48:45 +0200	[thread overview]
Message-ID: <20030725194845.GA723@neon> (raw)
In-Reply-To: <785F348679A4D5119A0C009027DE33C102E0D6B8@mcoexc04.mlm.maxtor.com>

Hi Eric!

On Fri, 25 Jul 2003, Mudama, Eric wrote:

> 0x64 has the seek complete, write fault, and corrected data bits set...
> 
> you get the short stalls, does the drive then keep functioning, or are the
> stalls fatal/permanent?  The error recovery paths in our disk are generally
> configured to be "heroic", as in "do everything possible to try to get that
> data safely on the media"... this can take several seconds at least,
> depending on the type of error.

At least no reported loss of data. Filesystem is reiserfs.

> Do these same errors happen with other kernels?

It's ok with 2.4.21-pre6-ac1 and 2.6.0-test1-bk. So I go for the kernel
problem. But my knowledge of IDE and harddisks is about null.

> I'd suggest that your drive appears to be having trouble writing to the
> media... I'd back up your data if you can and do a full-pack zeroing/write
> of the drive.  If that completes with no issues, then it's probably fine, if
> that has problems the drive ought to be RMA'd for a replacement... it could
> be one of those few out of a million that dies in the field within a year.
> 
> --eric
> 
> 
> -----Original Message-----
> From: Axel Siebenwirth [mailto:axel@pearbough.net]
> Sent: Friday, July 25, 2003 1:08 PM
> To: linux-kernel@vger.kernel.org
> Subject: [2.4.22-pre8-bk] dma_timer_expiry: dma status == 0x64
> 
> 
> hi,
> 
> this is a bug report?!
> 
> with the linux kernel 2.4.22-pre8 from bk as of this day I get short stalls
> about 5 to 8 seconds resulting in nothing happening with my machine at all.
> (right now it happenend, but I can still type this)
> 
> the kernel reports the following two messages:
> 
> hda: dma_timer_expiry: dma status == 0x64
> hda: DMA interrupt recovery
> hda: lost interrupt
> ...
> hda: dma_timer_expiry: dma status == 0x64
> hda: DMA interrupt recovery
> hda: lost interrupt
> hda: dma_timer_expiry: dma status == 0x64
> hda: DMA interrupt recovery
> hda: lost interrupt
> hda: dma_timer_expiry: dma status == 0x64
> hda: DMA interrupt recovery
> hda: lost interrupt
> 
> and so on.
> 
> so maybe this helps you find an error in the kernel.
> 
> best wishes,
> axel siebenwirth
> 
> P.S. I attached gzipped dmesg and .config

       reply	other threads:[~2003-07-25 19:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <785F348679A4D5119A0C009027DE33C102E0D6B8@mcoexc04.mlm.maxtor.com>
2003-07-25 19:48 ` Axel Siebenwirth [this message]
2003-07-25 19:08 Axel Siebenwirth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030725194845.GA723@neon \
    --to=axel@pearbough.net \
    --cc=eric_mudama@maxtor.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [2.4.22-pre8-bk] dma_timer_expiry: dma status == 0x64' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).