From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Juergen Lock <nox@jelal.kn-bremen.de>,
Aurelien Jarno <aurelien@aurel32.net>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] git head broken? (x86 softmmu w/o kvm)
Date: Tue, 23 Mar 2010 14:42:22 -0500 [thread overview]
Message-ID: <4BA9199E.1080206@codemonkey.ws> (raw)
In-Reply-To: <f43fc5581003231224q32ac024dsad421fb10869f5fe@mail.gmail.com>
Hi,
On 03/23/2010 02:24 PM, Blue Swirl wrote:
> On 3/23/10, Aurelien Jarno<aurelien@aurel32.net> wrote:
>
>> On Tue, Mar 23, 2010 at 03:27:26AM +0100, Aurelien Jarno wrote:
>> > On Mon, Mar 22, 2010 at 10:25:24PM +0100, Juergen Lock wrote:
>> > > Hi!
>> > >
>> > > I just wanted to make another FreeBSD qemu git head snaphot port update,
>> > > and found both i386-softmmu and x86_64-softmmu no longer boot, they seem
>> > > to hang early in the bios before it prints anything, last tb seems to be
>> > > this loop:
>> > >
>> >
>> > A quick bisect revealed it has been broken by this patch:
>> >
>>
>>
>> I have just pushed a patch to fix the problem.
>>
> Thanks, sorry for the trouble.
>
It would be nice to send a series like this to the list first in the
future to give people a heads up. It's a useful set of clean-ups but
it's nice to give people a chance to provide input.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-03-23 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 21:25 [Qemu-devel] git head broken? (x86 softmmu w/o kvm) Juergen Lock
2010-03-22 21:37 ` [Qemu-devel] " Juergen Lock
2010-03-23 2:27 ` [Qemu-devel] " Aurelien Jarno
2010-03-23 9:03 ` Aurelien Jarno
2010-03-23 10:06 ` Markus Armbruster
2010-03-23 10:21 ` Aurelien Jarno
2010-03-23 11:33 ` [Qemu-devel] " Paolo Bonzini
2010-03-23 19:24 ` [Qemu-devel] " Blue Swirl
2010-03-23 19:42 ` Anthony Liguori [this message]
2010-03-23 20:02 ` Markus Armbruster
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=4BA9199E.1080206@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=nox@jelal.kn-bremen.de \
--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 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).