From: Stefan Cars <stefan@snowfall.se>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ICH5 SATA high interrupt/system load again...
Date: Mon, 28 Jul 2003 11:49:27 +0200 (CEST) [thread overview]
Message-ID: <20030728114850.F22307@guldivar.globalwire.se> (raw)
In-Reply-To: <3F187DB1.1040309@pobox.com>
What also is interesting is that when I configure my kernel to use APIC it
hangs during boot just as it found the SATA drives...
/ Stefan
On Fri, 18 Jul 2003, Jeff Garzik wrote:
> Stefan Cars wrote:
> > Hi!
> >
> > I've seen the discussion regarding high interrupt / system load on the
> > ICH5 SATA and I'm asking what todo about it if I can't put my BIOS into
> > "normal" mode. This machine is an Dell Precision 360 and for some stupid
> > reason they have for this model removed the possibility in the BIOS to
> > change this sort of things (you can't change much really). I'm using
> > 2.4.21-ac4. Just to extract a simple tar file brings the system load up
> > and the computer is slow...
> >
> >
> > Here is some info:
> > tjatte:/import# cat /proc/interrupts
> > CPU0
> > 0: 557725 XT-PIC timer
> > 1: 102 XT-PIC keyboard
> > 2: 0 XT-PIC cascade
> > 5: 0 XT-PIC ehci_hcd
> > 9: 16409116 XT-PIC libata, usb-uhci, eth0
>
>
> Hum... interesting. I had seen reports of this before, but they were of
> the variety "drivers/ide has high load, libata doesn't". So it seems
> intrinsic of the hardware, which is a useful data point.
>
> Have you tried messing around with interrupt routing in BIOS setup?
> Since ATA, USB, and eth0 are all on the same interrupt, changing that
> may affect the situation positively.
>
> Jeff
>
>
>
next prev parent reply other threads:[~2003-07-28 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 21:44 ICH5 SATA high interrupt/system load again Stefan Cars
2003-07-18 23:07 ` Jeff Garzik
2003-07-19 8:27 ` Stefan Cars
2003-07-28 9:49 ` Stefan Cars [this message]
2003-07-28 10:04 ` Andrew de Quincey
2003-07-28 10:06 ` Stefan Cars
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=20030728114850.F22307@guldivar.globalwire.se \
--to=stefan@snowfall.se \
--cc=jgarzik@pobox.com \
--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;
as well as URLs for NNTP newsgroup(s).