All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Breuer <breuerr@mc.net>
To: sparclinux@vger.kernel.org
Subject: Re: Building a small sparc32 kernel
Date: Sun, 09 Apr 2006 15:05:23 +0000	[thread overview]
Message-ID: <443922B3.2080204@mc.net> (raw)
In-Reply-To: <20060404151927.GC2358@cassis>

Ludovic Courtès wrote:
> So, I now have a 2.6.14 SMP kernel I can boot from.  On my SS20, it
> doesn't even get to the point of spawning `init'.  I get a number of the
> following messages at boot time:
> 
>   esp0: Resetting scsi bus
>   esp0: SCSI bus reset interrupt
>   esp0: DMA error a4400302

Are you using multiple drives?  I've seen this problem before when using
multiple drives, even with a 2.6 UP kernel, but I've not had a problem
when only actively using one drive.

> And finally, I get spinlock debugging messages followed by a stack trace
> telling that something went wrong ("BUG: spinlock lockup on CPU#2",
> etc.), and nothing more.  I guess I'm going to have to capture the
> console output via a serial line in order to provide you with meaningful
> data.

Try configuring the kernel with spinlock debugging turned off.

> The machine has two SuperSPARC 390Z50.  In your original message you
> mentioned that support for SuperSPARC II was relatively stable, so maybe
> this just means that support for this older SuperSPARC flavor is not yet
> in such a good shape?  ;-)

I think you're almost there.  I don't see any reason why a pair of older
SuperSPARCs wouldn't work, but I don't have any to test against.

Bob

  parent reply	other threads:[~2006-04-09 15:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 15:20 Building a small sparc32 kernel Ludovic Courtès
2006-04-05 16:51 ` Bob Breuer
2006-04-08 14:24 ` Ludovic Courtès
2006-04-08 20:38 ` Wolfram Quester
2006-04-09 11:36 ` Ludovic Courtès
2006-04-09 15:05 ` Bob Breuer [this message]
2006-04-18 21:15 ` Ludovic Courtès
2006-04-18 21:20 ` David S. Miller

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=443922B3.2080204@mc.net \
    --to=breuerr@mc.net \
    --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.