From: Brad Boyer <flar@cegt201.bradley.edu>
To: ranga@CSUA.Berkeley.EDU (Sriranga Veeraraghavan)
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Question about SMP
Date: Fri, 7 May 1999 16:36:55 -0500 (CDT) [thread overview]
Message-ID: <199905072136.QAA18422@cegt201.bradley.edu> (raw)
In-Reply-To: <199905071754.KAA09699@soda.CSUA.Berkeley.EDU> from "Sriranga Veeraraghavan" at May 7, 99 10:54:03 am
> >From you post, I take it that my SMP kernel didn't work for you. What
> was the exact problem you had?
Well, the 2.2.0pre6 kernel I downloaded didn't even boot. Not from OF
when I downloaded it in Linux, and not from BootX when I downloaded it
in the MacOS. And I downloaded different ones each time, to get the
appropriate compression for the OS. In BootX, it just printed the
"Welcome to Linux" line and hung. It didn't do much better in OF, as
I recall. I also downloaded a 2.2.7 kernel from someone at MIT who
gave me a URL, but while it worked better, it still wasn't actually
useable. It did the same thing as the one I compiled from the 2.2.7
source. It did all the initial stuff, started init, printed the
message about swap, and then started printing the spinlock errors. I
hope someone has some idea what's happening here. I know my second
processor works, because I've used it in the MacOS and BeOS...
Brad Boyer
flar@cegt201.bradley.edu
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-05-07 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-07 4:42 Question about SMP Brad Boyer
1999-05-07 4:19 ` Charles E. Leiserson, Jr.
1999-05-07 17:54 ` Sriranga Veeraraghavan
1999-05-07 21:36 ` Brad Boyer [this message]
1999-05-08 2:36 ` LinuxPPC/iMac instabilities Derek Moeller
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=199905072136.QAA18422@cegt201.bradley.edu \
--to=flar@cegt201.bradley.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=ranga@CSUA.Berkeley.EDU \
/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;
as well as URLs for NNTP newsgroup(s).