From: Heitzso <heitzso@growthmodels.com>
To: sparclinux@vger.kernel.org
Subject: Re: ss20/ross/smp
Date: Thu, 05 May 2005 12:53:50 +0000 [thread overview]
Message-ID: <427A175E.5010709@growthmodels.com> (raw)
In-Reply-To: <4279EFEB.2070705@growthmodels.com>
Then you're better off than me. Mine dies hard during init, 2.4.30
I don't know a lot about this. Guessing that the gentoo
specific ross optimizations may be helping me. What setup
or distro are you running. I threw out my email to 3 lists
that cover the gamut. Are you running gentoo? If so, I
can give you my USE and other flags from make.conf to see
what the diff is. Any other of the sparc distros will have a
slightly different setup for gcc, libraries, etc. I wanted
gentoo to get a sun4m optimized ssl setup. Otherwise
gentoo takes an incredibly long time to compile.
Related to that, I did a series of emerges (gentoo speak)
to insure that gcc/libs/kernel were sort-of in sync as I settled
in the environment. You may be fighting some variation of a
kernel/lib problem.
I also have a keyboard attached and that may make a diff.
Again, don't really know.
>from kernel.org, SMP enabled. UP runs OK, though. But we seem to have
>similar hardware:
>
>The only thing I've noticed is that my prom counts the CPUs as 0 and 2:
>
>CPU_#0 HyperSPARC ROSS RT620/RT626 0x00080000 Bytes ECache
>CPU_#2 HyperSPARC ROSS RT620/RT626 0x00080000 Bytes ECache
>
>CPU_#1 ******* NOT installed *******
>CPU_#3 ******* NOT installed *******
>
>Does that hurt?
>
>
No. Usual way it numbers the cpus (believe, not expert).
>I'd like to do some debugging, but I don't know where to start. I have
>no idea where my sparc dies. Cache flushing (these routines are totally
>different for UP and SMP on Hypersparc, as I found out)? Forking and
>context changes? Being a kernel newbie doesn't really help, but I am
>willing to learn,
>
The one kernel that is sort-of guaranteed sparc32 smp
for ross is 2.2 series. May be possible for you to compile
latest 2.2 kernel SMP and try that out. Though I believe
interest is in getting SMP smoothed out and working 2.6.x
next prev parent reply other threads:[~2005-05-05 12:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 10:05 ss20/ross/smp Heitzso
2005-05-05 12:15 ` ss20/ross/smp Ulrich Teichert
2005-05-05 12:53 ` Heitzso [this message]
2005-05-05 13:08 ` ss20/ross/smp Stephen P. Becker
2005-05-05 13:22 ` ss20/ross/smp Ulrich Teichert
2005-05-05 14:50 ` ss20/ross/smp Heitzso
2005-05-05 18:04 ` ss20/ross/smp Ulrich Teichert
2005-05-06 0:42 ` [gentoo-sparc] ss20/ross/smp Keith M Wesolowski
2005-05-06 12:14 ` Heitzso
2005-05-06 14:50 ` Bob Breuer
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=427A175E.5010709@growthmodels.com \
--to=heitzso@growthmodels.com \
--cc=sparclinux@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.