From: Anthony Liguori <anthony@codemonkey.ws>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Jan Kiszka <jan.kiszka@web.de>, Beth Kon <eak@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Gleb Natapov <gleb@redhat.com>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: PC machine types switched to SeaBIOS/gPXE
Date: Tue, 03 Nov 2009 19:55:01 -0600 [thread overview]
Message-ID: <4AF0DEF5.6020805@codemonkey.ws> (raw)
In-Reply-To: <20091104013804.GA24215@morn.localdomain>
Kevin O'Connor wrote:
> I traced this down, and it looks like there is a series of subtle bugs
> that led to this situation.
>
> The bug causing the boot to fail is that gPXE didn't update its
> checksum. This was supposed to be fixed in gPXE commit f16668d, but
> it looks like gPXE either regressed or the e1000 driver is special in
> some way.
>
> The reason SeaBIOS commit a5826b5a exposes this issue, is that commit
> a5826b5a broke SeaBIOS' PMM support - the gPXE bug only shows up when
> PMM is not available.
>
> So, why did commit a5826b5a break PMM? This appears to be some weird
> interaction with gcc and its "-fwhole-program -combine" options. One
> of the variables (ZoneTmpHigh) is incorrectly marked by gcc as being
> local instead of global after commit a5826b5a. Unfortunately, instead
> of getting an error, the build proceeded and had a bogus reference to
> the ZoneTmpHigh variable - which caused PMM allocations to fail even
> when there was memory.
>
> I've reorganized the build slightly to work around this problem with
> "-combine". I've also updated the SeaBIOS linker scripts so that they
> will cause a build failure if a similar issue arises in the future.
> The latest SeaBIOS git should have this all working again (even with
> the current e1000 gPXE).
>
Thanks for tracking this down Kevin!
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-11-04 1:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 14:54 [Qemu-devel] PC machine types switched to SeaBIOS/gPXE Anthony Liguori
2009-10-30 19:37 ` [Qemu-devel] " Jan Kiszka
2009-10-30 19:45 ` Anthony Liguori
2009-10-31 12:42 ` Stefan Weil
2009-10-31 13:10 ` Jan Kiszka
2009-11-02 23:09 ` Beth Kon
2009-11-02 23:22 ` Anthony Liguori
2009-11-03 4:16 ` Kevin O'Connor
2009-11-03 14:11 ` Beth Kon
2009-11-04 1:38 ` Kevin O'Connor
2009-11-04 1:55 ` Anthony Liguori [this message]
2009-10-31 11:07 ` [Qemu-devel] " Stefan Weil
2009-10-31 12:02 ` [Qemu-devel] " Jan Kiszka
2009-11-02 12:51 ` [Qemu-devel] " Alexander Graf
2009-11-02 13:08 ` Avi Kivity
2009-11-02 13:15 ` Alexander Graf
2009-11-02 13:32 ` Avi Kivity
2009-11-02 13:51 ` Kevin O'Connor
2009-11-02 13:56 ` Avi Kivity
2009-11-02 14:06 ` Alexander Graf
2009-11-02 14:39 ` Avi Kivity
2009-11-09 18:41 ` Glauber Costa
2009-11-10 13:02 ` Avi Kivity
2009-11-10 13:03 ` Alexander Graf
2009-11-10 13:07 ` Avi Kivity
2009-11-10 13:09 ` Alexander Graf
2009-11-03 4:50 ` Kevin O'Connor
2009-11-03 4:57 ` Alexander Graf
2009-11-03 5:01 ` Avi Kivity
2009-11-03 6:02 ` Kevin O'Connor
2009-11-03 6:08 ` Avi Kivity
2009-11-03 13:42 ` Kevin O'Connor
2009-11-03 4:58 ` Avi Kivity
2009-11-02 14:51 ` Gleb Natapov
2009-11-02 14:54 ` Gleb Natapov
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=4AF0DEF5.6020805@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=eak@us.ibm.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.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 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.