From: Takashi Oe <toe@unlserve.unl.edu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Crash on BenH's latest rsync (2.4.6-pre3)
Date: Tue, 26 Jun 2001 16:29:13 -0500 [thread overview]
Message-ID: <20010626162913.3dc483d8.toe@unlserve.unl.edu> (raw)
In-Reply-To: <20010626205147.26310@smtp.wanadoo.fr>
Hi,
BootX support on your rsync tree and linuxppc_2_4_devel tree is
broken. I guess no one with BootX bothered to try
linuxppc_2_4_devel..
Takashi Oe
--- linux-2.4-benh/arch/ppc/kernel/setup.c.ORIG Wed Jun 20 17:49:30 2001
+++ linux-2.4-benh/arch/ppc/kernel/setup.c Tue Jun 26 16:24:06 2001
@@ -480,6 +480,11 @@
if ( ppc_md.progress ) ppc_md.progress("id mach(): start", 0x100);
#ifdef CONFIG_ALL_PPC
+ /* prom_init has already been called from __start */
+ /* relocate_nodes() must be called before intuit_machine_type() */
+ if (boot_infos)
+ relocate_nodes();
+
/* if we didn't get any bootinfo telling us what we are... */
if ( _machine == 0 )
{
@@ -494,10 +499,6 @@
if ( have_of )
{
- /* prom_init has already been called from __start */
- if (boot_infos)
- relocate_nodes();
-
/* _machine must be defined by now, so this is safe. */
finish_device_tree();
/*
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-06-26 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 20:29 Crash on BenH's latest rsync (2.4.6-pre3) Michel Lanners
2001-06-26 19:10 ` Tom Rini
2001-06-26 20:38 ` Michel Lanners
2001-06-26 20:51 ` Benjamin Herrenschmidt
2001-06-26 21:29 ` Takashi Oe [this message]
2001-06-26 22:13 ` Tom Rini
2001-06-26 22:31 ` Takashi Oe
2001-06-26 22:43 ` Tom Rini
2001-06-27 16:25 ` Stephen R Marenka
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=20010626162913.3dc483d8.toe@unlserve.unl.edu \
--to=toe@unlserve.unl.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).