From: Zack Brown <zbrown@tumblerings.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problems getting SMP to work with vanilla 2.4.26
Date: Sun, 4 Jul 2004 19:32:13 -0700 [thread overview]
Message-ID: <20040705023213.GA1557@tumblerings.org> (raw)
In-Reply-To: <20040705002305.GA20847@logos.cnet>
Hi,
On Sun, Jul 04, 2004 at 09:23:05PM -0300, Marcelo Tosatti wrote:
> On Sun, Jul 04, 2004 at 11:14:38AM -0700, Zack Brown wrote:
> > Hi Marcelo, folks,
> >
> > On Sun, Jul 04, 2004 at 11:13:36AM -0300, Marcelo Tosatti wrote:
> > > On Sat, Jul 03, 2004 at 07:05:43PM -0700, 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:
> > >
> > > I can't help much really. Tried CONFIG_ACPI_BOOT=n ?
> > >
> > I did a 'make dep' and 'make bzImage', and got the following error. It
> > looks like the kernel really wants that option enabled.
>
> Hi Zack,
>
> Silly me, its not possible to compile SMP image without CONFIG_ACPI_BOOT (a lot of
> SMP detection code is linked to basic ACPI infrastructure).
>
> Can you please try the nolapic/noapic boot options? They should disable the APIC, and
> if APIC is the "root" of your crashes, we will find out that way.
>
> Sorry for the noise.
It turns out I tried 2.6.6 and got it working. Thanks for the help though!
I'm assuming the 2.4 thing is probably just a configuration problem at my
end, and not an actual kernel bug. If you think it might be a real bug,
I'm happy to keep trying other stuff to root it out.
Many thanks!
Zack
--
Zack Brown
next prev parent reply other threads:[~2004-07-05 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
[not found] <A6974D8E5F98D511BB910002A50A6647615FF683@hdsmsx403.hd.intel.com>
2004-07-05 19:07 ` Len Brown
2004-07-06 16:48 ` 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
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=20040705023213.GA1557@tumblerings.org \
--to=zbrown@tumblerings.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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
all inboxes | Powered by JetHome®