From: Olaf Hering <olaf@aepfle.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Niels Kristian Bech Jensen <nkbj@mail.tele.dk>
Subject: Re: booting with BootX corrupts memory
Date: Fri, 18 Aug 2006 09:01:13 +0200 [thread overview]
Message-ID: <20060818070113.GA28088@aepfle.de> (raw)
In-Reply-To: <1155873732.5803.16.camel@localhost.localdomain>
On Fri, Aug 18, 2006 at 02:02:12PM +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2006-08-09 at 06:00 +0200, Niels Kristian Bech Jensen wrote:
> > On Tue, Aug 1, Olaf Hering wrote:
> >
> > > Booting an old Mac with BootX corrupts memory, the kernel seldom gets
> > > into init. Even the built-in initramfs archive gets corrupted. So far I
> > > havent figured out where the corruption starts. The only data point so
> > > far is that a passed initrd gets overwritten with stuff that looks like
> > > part of the device-tree after the call to free_area_init_node() from
> > > paging_init(). Perhaps the virtual/real address mapping isnt handled
> > > correctly.
> >
> > > This is broken since at least 2.6.15, 2.6.14 dies very early, 2.6.13 was
> > > still ok.
> >
> > > Symptoms differ, depending on used .config and wether an initrd is passed.
> >
> > I think I've been hit by this bug on my beige G3 running Ubuntu Edgy.
> >
> > When booting with initrd the boot process stops before any kernel output (CONFIG_BOOTX_TEXT is not enabled).
> > Booting without initrd works fine - at least until it cannot find the root filesystem driver. ;-)
>
> Does this patch helps ?
No, now I dont even get console= output on serial console.
next prev parent reply other threads:[~2006-08-18 7:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 4:00 booting with BootX corrupts memory Niels Kristian Bech Jensen
2006-08-18 4:02 ` Benjamin Herrenschmidt
2006-08-18 7:01 ` Olaf Hering [this message]
2006-08-21 12:17 ` Olaf Hering
2006-08-21 21:31 ` Benjamin Herrenschmidt
2006-08-23 14:55 ` Olaf Hering
2006-08-18 12:10 ` Niels Kristian Bech Jensen
-- strict thread matches above, loose matches on Subject: below --
2006-07-31 17:46 Olaf Hering
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=20060818070113.GA28088@aepfle.de \
--to=olaf@aepfle.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nkbj@mail.tele.dk \
/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.