public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric <eric@cisu.net>
To: Lasse Bang Mikkelsen <lbm-list@fatalerror.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange DMA timeouts
Date: Sun, 4 Jul 2004 11:55:26 -0500	[thread overview]
Message-ID: <200407041155.26042.eric@cisu.net> (raw)
In-Reply-To: <1088958931.3205.8.camel@slaptop>

On Sunday 04 July 2004 11:35 am, you wrote:
> Hi
>
> I keep getting these DMA timeouts under heavy harddrive load, ex. when
> unpacking big tarballs, transfering from USB harddrive etc.

More info needed. Please provide kernel version, dmesg, lspci,lsmod to start. 
You most certainly wont get any help without this info. Provide harddrive 
manufacturer USB 2.0? USB 1.1? 

> hda: dma_timer_expiry: dma status == 0x21
> hda: DMA timeout error
> hda: dma timeout error: status=0xd0 { Busy }
>
> hda: DMA disabled
> ide0: reset: success
>
> Is this a sign of harddisk failure or could this be a kernel problem?

If it would help the maintainers I also had this problem, or a related 
problem, with 2.6.5-gentoo-r1. Whenever I was ripping CD's to MP3 via KDE's 
copy paste from the audiocd ioslave, I could get a few CD's in before this 
would happen. However, if I did two CD's at a time it would almost always 
happen before either CD was done.

Furthermore I think there may be a memory leak on that codepath, because 
whenever it would reset the bus, my free memory would drop to about 69M (of 
1GB, usually 700-800 free) and my system would swap alot. A little bit after 
the DMA Disabled and ATAPI reset my machine would hang hard. However, if I 
didnt rip CD's that day and it didnt go into swapping, my machine runs 
perfectly fine.

Since I have switched to 2.6.7-gentoo-r8 and have no more CD's to rip 
unfortunatly so I don't know if an upgrade has solved my problem.

	 If this sounds like a kernel bug  or related to the original poster I can 
try to reproduce it and give more info. Sorry if its unrelated or has been 
fixed, then just ignore my message.

> Thanks.

  parent reply	other threads:[~2004-07-04 16:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-04 16:35 Strange DMA timeouts Lasse Bang Mikkelsen
2004-07-04 16:52 ` bert hubert
2004-07-04 16:55 ` Eric [this message]
2004-07-04 16:59   ` Eric
2004-07-04 17:49 ` Lasse Bang Mikkelsen
2004-07-04 20:52   ` Andrew Walrond
2004-07-05 11:58     ` Lasse Bang Mikkelsen
2004-07-05 13:11       ` Andrew Walrond
2004-07-05 15:41         ` Lasse Bang Mikkelsen
2004-07-05 18:00           ` Mario 'BitKoenig' Holbe
2004-07-05 20:37             ` Lasse Bang Mikkelsen

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=200407041155.26042.eric@cisu.net \
    --to=eric@cisu.net \
    --cc=lbm-list@fatalerror.dk \
    --cc=linux-kernel@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox