Thread (7 messages) flat view 7 messages, 3 authors, 2006-08-23

Re: booting with BootX corrupts memory

From: Olaf Hering <hidden>
Date: 2006-08-21 12:23:10

On Fri, Aug 18, 2006 at 09:01:13AM +0200, Olaf Hering wrote:
On Fri, Aug 18, 2006 at 02:02:12PM +1000, Benjamin Herrenschmidt wrote:
quoted
On Wed, 2006-08-09 at 06:00 +0200, Niels Kristian Bech Jensen wrote:
quoted
 On Tue, Aug  1, Olaf Hering wrote:
quoted
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.
quoted
This is broken since at least 2.6.15, 2.6.14 dies very early, 2.6.13 was
still ok.
quoted
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.
It doesnt work on a 7200, butit works on a beige G3.
But later it locks up in 'PM: Adding info for No Bus:target0:0',
after mesh init. This one is likely unrelated.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help