From: Marc Haber <mh+linux-kernel@zugschlus.de>
To: linux-kernel@vger.kernel.org
Subject: Kernel configuration influence on local APIC
Date: Thu, 16 Sep 2010 20:54:48 +0200 [thread overview]
Message-ID: <20100916185448.GA25947@torres.zugschlus.de> (raw)
Hi,
I have a system that needs the "lapic" option on the kernel command
line when I run the system with the 2.6.35.4 kernel that I use on most
of my servers. However, when I use grml as a rescue system on the box,
the system runs fine without this kernel command line.
The daily grml image that I have been trying is from last week and
uses a 2.6.35.4 image as well. The grml system has
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x84] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x85] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x86] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x87] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
in its dmesg, but CONFIG_X86_LOCAL_APIC=y is set - does that mean that
the lapic is disabled on grml?
What do I lose when I run the server without the lapic, and which
kernel setting should I play with to get the productive kernel to work
with the lapic enabled?
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
reply other threads:[~2010-09-16 18:54 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=20100916185448.GA25947@torres.zugschlus.de \
--to=mh+linux-kernel@zugschlus.de \
--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
all inboxes | Powered by JetHome®