From: Lars Brinkhoff <lars@nocrew.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Linux 2.4 on 2001 G4
Date: 10 Apr 2001 10:29:47 +0200 [thread overview]
Message-ID: <85puelrwck.fsf@junk.nocrew.org> (raw)
In-Reply-To: <20010409160621.12920@mailhost.mipsys.com>
Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> >How is the SMP support for the Dual 533MHz G4 in your tree?
> It should work but some of my latest stuffs were not tested on SMP
It seems to hang in smp_core99_kick_cpu(), probably when the CPU takes
the exception. I inserted some debug messages around the call to
mdelay() like so:
if (ppc_md.progress) ppc_md.progress("!", 0);
mdelay(1);
if (ppc_md.progress) ppc_md.progress("smp_core99_kick_cpu: after mdelay", 0);
When booting, "!" is printed, but the other message is not.
Is there anything else I can do to diagnose the problem?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2001-04-10 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <857l0utbu5.fsf@junk.nocrew.org>
[not found] ` <20010409160621.12920@mailhost.mipsys.com>
2001-04-10 8:29 ` Lars Brinkhoff [this message]
2001-04-10 8:54 ` Linux 2.4 on 2001 G4 Benjamin Herrenschmidt
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=85puelrwck.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.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.