From: Jiri Slaby <jirislaby@gmail.com>
To: S K <nospamnoham@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem activating multiple cores ONLY if I press any key before kernel is loaded
Date: Mon, 26 May 2008 10:06:44 +0200 [thread overview]
Message-ID: <483A6F94.5070901@gmail.com> (raw)
In-Reply-To: <514e099a0805252039r68f88ac1wbdd1b4de77a9af94@mail.gmail.com>
On 05/26/2008 05:39 AM, S K wrote:
> and Fedora 9 with kernel 2.6.25.3-18.fc9.i686.
[...]
> I see this in dmesg:
> CPU 1 irqstacks, hard=c07ba000 soft=c079a000
> Not responding.
> Inquiring remote APIC #1...
> ... APIC #1 ID: failed
> ... APIC #1 VERSION: failed
> ... APIC #1 SPIV: failed
> CPU #1 not responding - cannot use it.
> Booting processor 1/2 ip 4000
> Not responding.
> Inquiring remote APIC #2...
> ... APIC #2 ID: failed
> ... APIC #2 VERSION: failed
> ... APIC #2 SPIV: failed
> CPU #2 not responding - cannot use it.
> Booting processor 1/3 ip 4000
> Not responding.
> Inquiring remote APIC #3...
> ... APIC #3 ID: failed
> ... APIC #3 VERSION: failed
> ... APIC #3 SPIV: failed
> CPU #3 not responding - cannot use it.
> Total of 1 processors activated (5015.39 BogoMIPS).
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> Brought up 1 CPUs
Does it work with vanilla? If yes, contact your kernel provider (redhat bugzilla).
next prev parent reply other threads:[~2008-05-26 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 3:39 Problem activating multiple cores ONLY if I press any key before kernel is loaded S K
2008-05-26 8:06 ` Jiri Slaby [this message]
2008-05-28 18:35 ` Dave Jones
2008-05-29 2:53 ` S K
2008-05-31 7:25 ` Pavel Machek
2008-06-01 21:29 ` S K
2008-06-01 22:10 ` Pavel Machek
[not found] <fa.1PYS+TVcu/Wo5ZK/nT3I4Ox2814@ifi.uio.no>
2008-05-30 3:37 ` Robert Hancock
2008-05-30 4:33 ` S K
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=483A6F94.5070901@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nospamnoham@gmail.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 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.