From: Mikael Pettersson <mikpe@csd.uu.se>
To: Hendrik Fehr <s4248297@rcs.urz.tu-dresden.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Full CPU-usage on sis5513-chipset disc input/output-operations
Date: Fri, 3 Sep 2004 16:23:32 +0200 [thread overview]
Message-ID: <16696.32356.734435.383921@alkaid.it.uu.se> (raw)
In-Reply-To: <1094216504.41386b383000b@rmc60-231.urz.tu-dresden.de>
Hendrik Fehr writes:
> Mikael Pettersson writes:
> > [...]
> > These are "received illegal vector" errors. They indicate
> > a serious problem, either with the local APIC bus itself,
> > or with how the ACPI/MP tables cause us to program the local
> > and I/O APICs.
> >
> > Do the errors persist if you disable ACPI?
> >
> I just tried the following two things:
> Boot option "acpi=off" (made the cusour switching faster on and off). And when
> it came to ide setup i get lots of "hda lost interrupt". The system is
> unbootable with that option.
>
> With boot option "noapic" there are no more APIC error messages. Should i add
> that boot option to my defaults in /etc/lilo.conf?
Try pci=noacpi (or however that option which prevents ACPI PCI
IRQ routing is spelled) first.
noapic is a workaround for breakage in other subsystems.
You'll lose interrupt vectors, but that may be preferable
to instability.
next prev parent reply other threads:[~2004-09-03 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 13:01 Hendrik Fehr
2004-09-03 14:07 ` Alan Cox
2004-09-03 15:52 ` Daniel Egger
2004-09-03 14:23 ` Mikael Pettersson [this message]
[not found] <Pine.GSO.4.10.10409080011370.6828-100000@rcs54.urz.tu-dresden.de>
2004-09-07 23:15 ` Hendrik Fehr
[not found] <fa.lcmvbgi.1m1iepk@ifi.uio.no>
[not found] ` <fa.fc3clr3.71gar9@ifi.uio.no>
2004-09-04 3:25 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2004-09-03 13:16 Hendrik Fehr
2004-09-03 10:22 Hendrik Fehr
2004-09-03 10:54 ` Mikael Pettersson
2004-09-03 10:55 ` Alan Cox
2004-09-02 17:11 Hendrik Fehr
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=16696.32356.734435.383921@alkaid.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=s4248297@rcs.urz.tu-dresden.de \
/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
all inboxes | Powered by JetHome®