All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith M Wesolowski <wesolows@foobazco.org>
To: sparclinux@vger.kernel.org
Subject: Re: Sun4d progress
Date: Wed, 18 Aug 2004 21:39:18 +0000	[thread overview]
Message-ID: <20040818213918.GA9328@foobazco.org> (raw)
In-Reply-To: <Pine.LNX.4.53.0408182135050.391@mailgate.netunix.com>

On Wed, Aug 18, 2004 at 02:33:28PM -0700, William Lee Irwin III wrote:

> > I get a bootable UP system but SMP locks up after
> > ioremap: done with statics, switching to malloc.
> > Does anyone know what is happening ?
> 
> I won't know for a while, no. I'll work on explaining what each of

I don't remember whether this applies to 2.4 (I think it does), but
certainly in 2.6 the problem is the sbus ranges munging.  I explained
this very briefly to Will at some point, but the gist of it is,
there's a comment that says something to the effect that "How is this
supposed to work?  Ask Dave."  At one point, I traced this out and
found that some crucial ranges fixup that happened in 2.2 wasn't
happening in 2.6.  This is triggered by the SCSI init, BTW.

Bearing in mind that this worked on 2.2, it shouldn't be hard to fix
up.

-- 
Keith M Wesolowski

  parent reply	other threads:[~2004-08-18 21:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 21:28 Sun4d progress Chris Newport
2004-08-18 21:33 ` William Lee Irwin III
2004-08-18 21:39 ` Keith M Wesolowski [this message]
2004-08-18 21:41 ` William Lee Irwin III
2004-08-18 21:57 ` C.Newport
2004-08-18 22:00 ` William Lee Irwin III
2004-08-19 12:47 ` Thomas Bogendoerfer
2004-08-19 14:12 ` William Lee Irwin III
2004-08-19 14:28 ` Meelis Roos
2004-08-19 16:18 ` Keith M Wesolowski
2004-08-19 17:12 ` C.Newport
2004-08-19 17:16 ` William Lee Irwin III
2004-08-19 17:53 ` C.Newport
2004-08-19 17:56 ` William Lee Irwin III

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=20040818213918.GA9328@foobazco.org \
    --to=wesolows@foobazco.org \
    --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.