[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4524862A.7080306@zytor.com>
Date: Wed, 04 Oct 2006 21:12:26 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
CC: Andrew Morton <akpm@...l.org>, vgoyal@...ibm.com,
linux kernel mailing list <linux-kernel@...r.kernel.org>,
Reloc Kernel List <fastboot@...ts.osdl.org>, ak@...e.de,
horms@...ge.net.au, lace@...kratochvil.net, magnus.damm@...il.com,
lwang@...hat.com, dzickus@...hat.com, maneesh@...ibm.com
Subject: Re: [PATCH 12/12] i386 boot: Add an ELF header to bzImage
Eric W. Biederman wrote:
>
> Ugh. I just tested this with a grub 0.97-5 from what I assume is a
> standard FC5 install (I haven't touched it) and the kernel boots.
> I only have a 64bit user space on that machine so init doesn't
> start but I get the rest of the kernel messages.
>
> There were several testers working at redhat so a pure redhat
> incompatibility would be a surprise.
>
> I don't think the formula is a simple grub+bzImage == death.
>
> There is something more subtle going on here.
>
> I'm not certain where to start looking. Andrew it might help if we
> could get the dying binary just in case some weird compile or
> processing problem caused insanely unlikely things like the multiboot
> binary to show up in your grub install. I don't think that is it,
> but it should allow us to rule out that possibility.
>
I would try running it in a more memory-constrained environment.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists