From: Adam Williams <broadcast@earthling.net>
To: linux-kernel@vger.kernel.org
Subject: crash in smp_core99_kick_cpu
Date: Wed, 31 Oct 2001 16:29:29 -0800 [thread overview]
Message-ID: <3BE09769.2060703@earthling.net> (raw)
This is a dual CPU G4. Startup freezes after
smp_core99_kick_cpu done
is displayed. Commenting out the
KL_GPIO_OUT(reset_io, KEYLARGO_GPIO_OUTPUT_ENABLE);
line in feature_core99_kick_cpu allows the boot process to
continue but with only CPU #0 and a "Processor 1 is stuck"
message.
MacOS 9.2 booted fine and detected both CPUs.
Compiler gcc 2.96
Kernel 2.4.13
Kernels compiled with gcc 3.0.2 just crash and go into
open firmware.
cat /proc/cpuinfo displays
processor : 0
cpu : 7450, altivec supported
temperature : 1-76 C (uncalibrated)
clock : 799MHz
revision : 2.1 (pvr 8000 0201)
bogomips : 797.90
total bogomips : 797.90
zero pages : total: 0 (0Kb) current: 0 (0Kb) hits: 0/0 (0%)
machine : PowerMac3,5
motherboard : PowerMac3,5 MacRISC2 MacRISC Power Macintosh
L2 cache : 256K unified
memory : 256MB
pmac-generation : NewWorld
next reply other threads:[~2001-11-01 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 0:29 Adam Williams [this message]
2001-11-01 3:48 ` crash in smp_core99_kick_cpu Tom Rini
2001-11-02 8:48 ` 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=3BE09769.2060703@earthling.net \
--to=broadcast@earthling.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox