From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: oops in sched_init() on E3000
Date: Wed, 25 Feb 2004 05:08:11 +0000 [thread overview]
Message-ID: <20040225050811.GI693@holomorphy.com> (raw)
In-Reply-To: <20040222043448.GG703@holomorphy.com>
On Tue, Feb 24, 2004 at 10:09:13PM -0500, Ben Collins wrote:
> I had a feeling this whole problem with the IRQ's was another
> smp_processor_id() issue.
> Dave, the first time that init_irqwork_curcpu() gets called from head.S
> for the boot cpu, smp_processor_id() is returning 0, so the __irq_work
> isn't getting setup properly. Hopefully this is the last issue with
> this.
> The attached patch fixes it. It's in my repo, so you can pull it along
> with the debug rwlock fix I sent you earlier.
This gets 2.6.x-bk-CURRENT booting and running with flying colors here.
Thanks!
-- wli
next prev parent reply other threads:[~2004-02-25 5:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 4:34 oops in sched_init() on E3000 William Lee Irwin III
2004-02-22 4:42 ` William Lee Irwin III
2004-02-22 7:25 ` David S. Miller
2004-02-22 9:11 ` William Lee Irwin III
2004-02-22 9:57 ` William Lee Irwin III
2004-02-22 18:03 ` David S. Miller
2004-02-22 21:51 ` William Lee Irwin III
2004-02-22 21:57 ` David S. Miller
2004-02-22 22:00 ` David S. Miller
2004-02-22 22:01 ` David S. Miller
2004-02-22 22:06 ` William Lee Irwin III
2004-02-22 22:10 ` William Lee Irwin III
2004-02-22 23:17 ` David S. Miller
2004-02-22 23:57 ` Ben Collins
2004-02-23 0:34 ` William Lee Irwin III
2004-02-23 5:41 ` David S. Miller
2004-02-23 10:02 ` William Lee Irwin III
2004-02-23 12:04 ` Ben Collins
2004-02-23 12:11 ` Ben Collins
2004-02-23 12:27 ` William Lee Irwin III
2004-02-24 7:37 ` William Lee Irwin III
2004-02-24 15:13 ` Ben Collins
2004-02-24 18:29 ` Ben Collins
2004-02-25 3:09 ` Ben Collins
2004-02-25 5:08 ` William Lee Irwin III [this message]
2004-02-25 6:59 ` 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=20040225050811.GI693@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.