All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: sparc32 SMP for 2.6
Date: Mon, 14 Feb 2005 14:40:50 +0000	[thread overview]
Message-ID: <20050214144050.GT13009@holomorphy.com> (raw)
In-Reply-To: <420F070B.8010000@mc.net>

On Sun, Feb 13, 2005 at 01:51:39AM -0600, Bob Breuer wrote:
> I've been poking at the sparc32 SMP code and I have it to the point
> where it will run a minimal userland.  It is still far from being
> stable though.
> For reference, I started with the SMP patch [0] that wli sent to
> the list last July.  To go along with the attached SMP patch, it
> needs the spinlock fix [1] from Art Haas, and the attached
> DEBUGSPINLOCK patch from Tom Callaway.
> Here's a list of problems I have seen with it so far:
> - the scsi driver must be compiled in or it has problems.
> - when I compiled with gcc 3.3.4, it drops back to the prom with
>     a level 15 interrupt.
> - from a serial console, init hangs
> - /proc/interrupts shows 0 interrupts for the 2nd cpu
> - sun4d still needs fixing
> Testing with gcc 3.2.2 and 2 150 MHz HyperSPARCs, if I compile
> in scsi and leave out all of the networking, I am able to pass
> "init=/bin/bash" and get a shell everytime.
> I am sure there are still areas of bitrot and neglect that remain,
> so if anyone has any ideas, feel free to share them.

Between networking and serial it sounds as if this is a partial
explanation as to why I'm having trouble here.


-- wli

  parent reply	other threads:[~2005-02-14 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-13  7:51 sparc32 SMP for 2.6 Bob Breuer
2005-02-13 12:27 ` Jiri Gaisler
2005-02-14 14:40 ` William Lee Irwin III [this message]
2005-02-14 15:12 ` Bob Breuer
2005-02-14 18:05 ` Krzysztof Helt
2005-02-28  0:47 ` 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=20050214144050.GT13009@holomorphy.com \
    --to=wli@holomorphy.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.