From: William Lee Irwin III <wli@holomorphy.com>
To: Yun Zhou <sraphim@mofd.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HD access sluggish in 2.6.0
Date: Fri, 19 Dec 2003 00:09:40 -0800 [thread overview]
Message-ID: <20031219080940.GG31393@holomorphy.com> (raw)
In-Reply-To: <200312181957.05917.sraphim@mofd.net>
On Thu, Dec 18, 2003 at 07:57:05PM -0600, Yun Zhou wrote:
> I'm using a system with 1HD (DC WD600BB-00CAA1 60 GB) using kernel 2.6.0.
> Whenever the system uses the disk extensively (copying a file, untarring,
> etc.), it grinds to a near halt, with the CPU usage at about 100%, even for a
> simple copying operation.
> This problem is not present when using 2.4.22, nor any of the 2.4 series
> kernels that I've tried. Does anyone know what is causing this?
> Thanks in advance!
This is typical of IDE disks where the driver is pessimistically using
PIO. A dmesg and .config would help, plus maybe readprofile(1) results
(you'll have to boot with profile=1 on the kernel command-line.) just
in case it's actually something else.
-- wli
prev parent reply other threads:[~2003-12-19 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 1:57 HD access sluggish in 2.6.0 Yun Zhou
2003-12-19 7:18 ` bert hubert
2003-12-19 8:09 ` William Lee Irwin III [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=20031219080940.GG31393@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sraphim@mofd.net \
/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