public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Artem S. Tashkinov" <birdie@permonline.ru>
To: B.Zolnierkiewicz@elka.pw.edu.pl
Subject: 100% CPU load on nforce2/3 motherboards with kernels >= 2.6.8
Date: Mon, 10 Jan 2005 18:20:21 +0500	[thread overview]
Message-ID: <41E28115.4010002@permonline.ru> (raw)

Good day, Bartlomiej Zolnierkiewicz!

I've got a severe problem with linux >= 2.6.9 kernels on my PC: any 
read/write HDD IO operations consume 100% of CPU. Kernel is compiled 
with nforce IDE support. Kernel is vanilla from kernel.org. No 
proprietary drivers are installed. My chipset is NForce3 250, CPU is 
Sempron 3100. My MB is GigaByte K8NS Pro.

My friend (who has an nforce2 based motherboard Asus A7N8X-X) has the 
same problem with >= 2.6.9 kernels. 2.6.7 at the same time works fine 
for him.

His and mine kernels say that the HDD is in UDMA5 mode. I tried 
switching off ACPI/IO APIC and even Plug'n'Play code with no success. 
Kernel 2.4.28 works perfectly

With respect, Artem

                 reply	other threads:[~2005-01-10 13:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41E28115.4010002@permonline.ru \
    --to=birdie@permonline.ru \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    /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