All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hendrik Fehr <s4248297@rcs.urz.tu-dresden.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Full CPU-usage on sis5513-chipset disc input/output-operations
Date: Fri, 03 Sep 2004 15:07:55 +0100	[thread overview]
Message-ID: <1094220474.7975.11.camel@localhost.localdomain> (raw)
In-Reply-To: <1094216504.41386b383000b@rmc60-231.urz.tu-dresden.de>

On Gwe, 2004-09-03 at 14:01, Hendrik Fehr wrote:
> 
> With boot option "noapic" there are no more APIC error messages. Should i add
> that boot option to my defaults in /etc/lilo.conf?

For uniprocessor machines you should avoid building with APIC support in
general anyway. A lot of systems simply don't work with APIC
uniprocessor because nobody used to use the APIC in such a
configuration. 


  reply	other threads:[~2004-09-03 15:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03 13:01 PROBLEM: Full CPU-usage on sis5513-chipset disc input/output-operations Hendrik Fehr
2004-09-03 14:07 ` Alan Cox [this message]
2004-09-03 15:52   ` Daniel Egger
2004-09-03 14:23 ` Mikael Pettersson
     [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=1094220474.7975.11.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.