From: Len Brown <len.brown@intel.com>
To: Zack Brown <zbrown@tumblerings.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problems getting SMP to work with vanilla 2.4.26
Date: 05 Jul 2004 15:07:44 -0400 [thread overview]
Message-ID: <1089054464.15675.56.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615FF683@hdsmsx403.hd.intel.com>
On Sat, 2004-07-03 at 22:05, Zack Brown wrote:
> Hi folks,
>
> When booting vanilla 2.4.26 with SMP enabled, I get a lockup before
> the
> boot sequence is completed. The same kernel with SMP disabled boots
> and runs
> just fine. Both CPUs are detected by the system at bootup, before lilo
> takes
> over. Here's the error as I wrote it down from the screen, followed by
> the
> .config file:
>
> ------------------------------ cut here ------------------------------
> Using local APIC timer interrupts.
> Calibrating APIC timer...
> ..... CPU clock speed is 1004.4785 MHZ
> ..... hostbus clock speed is 133.9304 MHz
> cpu: 0, clocks: 1339304, slice: 446434
> CPU0<T0:1339296,T1:892848,D:14,S:446434,C:1339304>
> cpu: 1, clocks: 1339304, slice: 446434
> CPU1<T0:1339296,T1:446416,D:12,S:446434,C:1339304>
> ------------------------------ cut here ------------------------------
complete dmesg from success case would help,
but try booting with "acpi=off", as that will
disable ACPI for CPU enumeration, and if there
is a bug in your ACPI tables, it would avoid it.
-Len
next parent reply other threads:[~2004-07-05 19:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FF683@hdsmsx403.hd.intel.com>
2004-07-05 19:07 ` Len Brown [this message]
2004-07-06 16:48 ` problems getting SMP to work with vanilla 2.4.26 Zack Brown
2004-07-06 17:09 ` Len Brown
2004-07-06 17:15 ` Zack Brown
2004-07-06 20:07 ` Krzysztof Halasa
2004-07-07 20:53 ` Len Brown
2004-07-04 2:05 Zack Brown
2004-07-04 14:13 ` Marcelo Tosatti
2004-07-04 18:14 ` Zack Brown
2004-07-05 0:23 ` Marcelo Tosatti
2004-07-05 2:32 ` Zack Brown
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=1089054464.15675.56.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zbrown@tumblerings.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