From: "Broadfoot, KenX" <kenx.broadfoot@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] uni-processor kernel on SMP machine
Date: Tue, 17 Oct 2000 21:51:31 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205584@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205576@msgid-missing>
In my case I am having problems with the B0 stepping procs...
Should the B-step and the A-step kernel choices BOTH be set?
--ken
> -----Original Message-----
> From: Jun Nakajima [SMTP:jun@sco.com]
> Sent: Tuesday, October 17, 2000 1:34 PM
> To: Pat O'Rourke
> Cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] uni-processor kernel on SMP machine
>
> Both UP and SMP kernels (2.4.0-test9) work fine on at least two 4-way
> Lions (A2-stepping CPUs each with latest and a bit old firmware) at our
> site. Can you be more specific about the problem you are seeing?
>
> Pat O'Rourke wrote:
> >
> > I attempted to boot a 2.4.0-test9 kernel compiled without SMP support
> > on an MP Lion, but it would not boot. I did the same experiemnt with
> > older kernels and it appears this broke between test7 and test8. Has
> > anyone else noticed this? Is there a work around / solution?
> >
> > I noticed the problem on both a 2-way lion w/ B1 cpus and a 4-way lion
> > with A2 cpus.
> >
> > Thanks,
> >
> > Pat
> >
>
> --
> Jun U Nakajima
> Core OS Development
> SCO/Murray Hill, NJ
> Email: jun@sco.com, Phone: 908-790-2352 Fax: 908-790-2426
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
next prev parent reply other threads:[~2000-10-17 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-17 16:44 [Linux-ia64] uni-processor kernel on SMP machine Pat O'Rourke
2000-10-17 20:34 ` Jun Nakajima
2000-10-17 21:51 ` Broadfoot, KenX [this message]
2000-10-18 13:22 ` Pat O'Rourke
2000-10-18 19:30 ` Ahna, Christopher J
2000-10-18 19:59 ` Pat O'Rourke
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=marc-linux-ia64-105590678205584@msgid-missing \
--to=kenx.broadfoot@intel.com \
--cc=linux-ia64@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 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.