From: Bart Samwel <bart@samwel.tk>
To: andrea gelmini <andrea.gelmini@linux.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DMA problem with kernel >2.6.10
Date: Sun, 21 Aug 2005 16:47:28 +0200 [thread overview]
Message-ID: <43089400.1060603@samwel.tk> (raw)
In-Reply-To: <20050807164824.GA3312@gelma.net>
andrea gelmini wrote:
> Hardware: Toshiba Satellite P20 (P4-3200 MHz, 512MB RAM) [1]
> Software: Debian Unstable
> GCC: 3.4.5 [2]
> Memtest86+: v.1.60 (stress tools, CPU/RAM and so on, are all happy)
> Problem: with kernel <=2.6.10 everything is all right...
> but with any kernel released after 2.6.10 (pre, rc, stable, mm, and
> so on), I've got this:
>
> hda: dma_timer_expiry: dma status == 0x21
> hda: DMA timeout error
> hda: dma timeout error: status=0xd0 { Busy }
[...]
> It happen quickly if I do also something like this:
>
> cd /proc/sys/vm
> echo 100 > dirty_background_ratio
> echo 1000000 > dirty_expire_centisecs
> echo 100 > dirty_ratio
> echo 1000000 > dirty_writeback_centisecs
I've had a report about this before, from someone who was using laptop
mode -- same error message. Funny thing is, the laptop mode tools
scripts also modify the above values, so it's probably the same problem.
Until now I thought it was a Thinkpad hardware problem, because I only
heard about these problems on Thinkpads, but apparently it's a kernel
problem after all. Don't know anything about the causes though.
--Bart
prev parent reply other threads:[~2005-08-21 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 16:48 DMA problem with kernel >2.6.10 andrea gelmini
2005-08-21 14:47 ` Bart Samwel [this message]
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=43089400.1060603@samwel.tk \
--to=bart@samwel.tk \
--cc=andrea.gelmini@linux.it \
--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