From: Siju George <sgeorge.ml@gmail.com>
To: linux-smp@vger.kernel.org
Subject: LAPCI disabled for second Processor in 2.6.8-11-amd64-k8-smp kernel - need help reading source code
Date: Wed, 28 Dec 2005 20:41:19 +0530 [thread overview]
Message-ID: <b713df2c0512280711o7f2b3afo8784d8f5ba12f79f@mail.gmail.com> (raw)
In-Reply-To: <b713df2c0512200246p32b5bad7nc9668fbd955a332b@mail.gmail.com>
Hi,
I need some help to sort out this :-)
The following lines appear in the dmesg of my Dual Opteron Server
running on 2.6.8-11-amd64-k8-smp kernel
--------------
Processor #0 15:5 APIC version 16
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:5 APIC version 16
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
---------------------------------
What is LAPIC?
Why is it disabled for the second processor?
Is it normal beavior?
I have posted to several mailinglist and got no reply on this :-(
I have traced to the kernel code at
http://fxr.watson.org/fxr/source/drivers/acpi/tables.c?v=linux-2.6.11.8#L121
From lines 121-127 I find this.
-----------------------------
case ACPI_MADT_LAPIC:
{
struct acpi_table_lapic *p =
(struct acpi_table_lapic*) header;
printk(KERN_INFO PREFIX "LAPIC (acpi_id[0x%02x]
lapic_id[0x%02x] %s)\n",
p->acpi_id, p->id,
p->flags.enabled?"enabled":"disabled");
}
----------------------------------
Could some one who works on the kernel or who knows C please interpret
this for me?
The code version is differrent but I hope it does not affect.
Please let me know if you need the full dmesg
Thankyou so much :-)
Kind Regards
Siju
next parent reply other threads:[~2005-12-28 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b713df2c0512200246p32b5bad7nc9668fbd955a332b@mail.gmail.com>
2005-12-28 15:11 ` Siju George [this message]
2005-12-29 14:53 ` LAPCI disabled for second Processor in 2.6.8-11-amd64-k8-smp kernel - need help reading source code cerise
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=b713df2c0512280711o7f2b3afo8784d8f5ba12f79f@mail.gmail.com \
--to=sgeorge.ml@gmail.com \
--cc=linux-smp@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 read-only IMAP folder(s) and NNTP newsgroup(s).