From: Bill Davidsen <davidsen@tmr.com>
To: "Steven E. Woolard" <tuxq@tuxq.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem: 2.4.26/27 & 2.6.9 Audio CD Burning
Date: Mon, 15 Nov 2004 15:51:22 -0500 [thread overview]
Message-ID: <419916CA.8060805@tmr.com> (raw)
In-Reply-To: <41960FC8.3040004@tuxq.com>
Steven E. Woolard wrote:
> I've reproduced this problem on my system with 2.4.26, 2.4.27, and
> 2.6.9. When trying to burn an audio CD with cdrecord, the system load
> average will skyrocket (relitively speaking) up to 4 or 5 sometimes
> reaching 10 or higher. This does not happen with data CD's or at all
> with 2.6.7 kernel. I used scsi emulation (of course) on 2.4.26 and
> 2.4.27--not 2.6.9.
>
> Side Notes:
> DMA is enabled, I have tried downgrading cdrtools, and if
> I remember correctly it has the same problem in 2.6.8(.1).
>
> Hardware:
> AMD Athlon XP 2400+
> 1024MB RAM
> VIA VT82C686 Southbridge (IDE Controller)
> LITE-ON LTR48246S CDRW Drive
My understanding based on experience is that with a 2.4 kernel you will
get a high load average burning audio, and the quickest fix is to use
speed= to slow the burn.
With 2.6 you should get DMA using the ATAPI:/dev/hdX interface, and in
fact I do see only a few percent CPU burning at 40x (max) and a lowly
2.0GHz Celeron.
If none of this helps, do run "vmstat 1" to a file while running, and
post your command line used to start the burn. You might try "ATA:" as
well for comparison. I don't know if "-dummy" will allow you to test
without actually burning or not.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2004-11-15 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 13:44 Problem: 2.4.26/27 & 2.6.9 Audio CD Burning Steven E. Woolard
[not found] ` <41961AC9.2070902@comcast.net>
2004-11-14 4:00 ` Steven E. Woolard
2004-11-15 20:51 ` Bill Davidsen [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=419916CA.8060805@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tuxq@tuxq.com \
/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