From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <andi@firstfloor.org>,
venkatesh.pallipadi@intel.com, suresh.b.siddha@intel.com,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: ACPI early ioremap problems II
Date: Mon, 21 Jan 2008 03:59:11 +0100 [thread overview]
Message-ID: <20080121025911.GA2675@one.firstfloor.org> (raw)
In-Reply-To: <20080120235000.GA23512@elte.hu>
On Mon, Jan 21, 2008 at 12:50:00AM +0100, Ingo Molnar wrote:
>
> * Andi Kleen <andi@firstfloor.org> wrote:
>
> > As a followup I see this problem on three different 64bit machines
> > now. Symptom is usually that only one core is active because ACPI
> > doesn't see the other processors in its tables.
>
> to be able to have a chance to fix it we need you meet the minimum
> threshold for bugreports: please send the failing .config and a full
> boot message of the incident as well. (Please also check latest x86.git,
> maybe it's something that got fixed today.)
The other crash seems to have gone away on git tip
28a0fcd6b38e247200bd857996375aee91eae8ce now. I also don't see the missing
nodes or missing cores anymore. Also the extended memory on AMD
seems to be detected correctly gain.
Thanks,
-Andi
prev parent reply other threads:[~2008-01-21 2:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080119030843.GA2028@basil.nowhere.org>
[not found] ` <20080119150328.GA32370@elte.hu>
[not found] ` <20080119152649.GA1375@one.firstfloor.org>
2008-01-19 15:30 ` ACPI early ioremap problems Ingo Molnar
2008-01-19 15:46 ` Andi Kleen
2008-01-19 18:45 ` Ingo Molnar
2008-01-19 19:16 ` Andi Kleen
2008-01-20 16:48 ` ACPI early ioremap problems II Andi Kleen
2008-01-20 23:50 ` Ingo Molnar
2008-01-21 2:59 ` Andi Kleen [this message]
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=20080121025911.GA2675@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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