From: Anthony Liguori <anthony@codemonkey.ws>
To: Rob Landley <rob@landley.net>
Cc: Stefan Weil <sw@weilnetz.de>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Commit 5632ae46 broke the network on mips.
Date: Sun, 22 Jan 2012 19:48:06 -0600 [thread overview]
Message-ID: <4F1CBC56.4020508@codemonkey.ws> (raw)
In-Reply-To: <4F1C9EF5.9090105@landley.net>
On 01/22/2012 05:42 PM, Rob Landley wrote:
> On 01/22/2012 01:06 AM, Stefan Weil wrote:
>> Am 21.01.2012 20:04, schrieb Rob Landley:
>>> commit 5632ae46: "mips_malta: move i8259 initialization after piix4
>>> initialization" broke the network on mips. It still comes up, but
>>> doesn't pass packets.
>>>
>>> Try this:
>>>
>>> wget http://landley.net/aboriginal/bin/system-image-mips.tar.bz2
>>> tar xvjf system-image-mips.tar.bz2
>>> cd system-image-mips
>>> ./run-emulator.sh
>>>
>>> [ wait for shell prompt ]
>>>
>>> wget http://google.com
>>>
>>> Under 0.15.1 it works, under 1.0 it doesn't. Identical binary. I
>>> bisected it to the commit in question, it's still broken in -master.
>>>
>>> Rob
>>
>> This was fixed with commits e9b40fd34ceb23461083d505a444a389c094455b
>> and 0b23c5d40ea933cfece3b4f69427f79c8a23256d in master and stable-1.0.
>
> The git tag for v1.0 does not include that commit. Apparently the
> current 1.0 tarball on the website does, which is odd since e9b4 was
> only applied to the git tree _after_ a January 6th commit. So either
> "git log" is being weird, or you guys retroactively re-released the 1.0
> tarball without renumbering it?
>
> I'm confused...
>
>> My latest QEMU works with MIPS Malta running from an NFS root.
>
> I can confirm that current -master works for me.
>
> The 1.0 tarball includes the fix, the 1.0 git tag doesn't. I'll include
> a note to that effect in my release notes.
BTW, since you tag doesn't have this changeset (and it should), it's your tag
that's messed up.
Fortunately, for the 1.0 release, I started using a signed tag.
http://git.qemu.org/?p=qemu.git;a=tag;h=5e5e6d6c16e1742996d93e8f3e946cf544d0b146
So this should help you figure out where your bogus tag came from.
Regards,
Anthony Liguori
>
> Thanks,
>
> Rob
>
prev parent reply other threads:[~2012-01-23 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 19:04 [Qemu-devel] Commit 5632ae46 broke the network on mips Rob Landley
2012-01-22 7:06 ` Stefan Weil
2012-01-22 23:42 ` Rob Landley
2012-01-23 1:44 ` Anthony Liguori
2012-01-23 4:17 ` Rob Landley
2012-01-23 6:34 ` Stefan Weil
2012-01-23 12:34 ` Rob Landley
2012-01-23 1:48 ` Anthony Liguori [this message]
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=4F1CBC56.4020508@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
--cc=sw@weilnetz.de \
/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.