From: "Blue Swirl" <blauwirbel@gmail.com>
To: Jakub Jermar <jakub@jermar.eu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [sparc64] qemu crashes after the "OpenBIOS for Sparc64" banner is printed
Date: Thu, 28 Aug 2008 22:05:11 +0300 [thread overview]
Message-ID: <f43fc5580808281205r5b3f1965l116584b60c7d5977@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580808281016j3e4b5a63s444bd8eeb7a73e8f@mail.gmail.com>
On 8/28/08, Blue Swirl <blauwirbel@gmail.com> wrote:
> On 8/28/08, Jakub Jermar <jakub@jermar.eu> wrote:
>
> > Blue Swirl wrote:
> >
> > >
> > > >
> > > > > What host? On my amd64 and using the latest OpenBIOS I get this:
> > > > >
> > > >
> > >
> >
> > It works on amd64 for me too, so it's an ia32 issue.
> > If I sent you an ia32 coredump, would that be of any help to you?
>
>
> No thanks, I can no reproduce it. Maybe the reason can be found with bisection.
f2bc7e7fa175b61a20c6f10c324d7c4d68af676f is first bad commit
commit f2bc7e7fa175b61a20c6f10c324d7c4d68af676f
Author: blueswir1 <blueswir1@c046a42c-6fe2-441c-8c8c-71466251a162>
Date: Tue May 27 17:35:30 2008 +0000
Move non-op functions from op_helper.c to helper.c and vice versa.
Rearrange interrupt handling to match other targets.
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@4590
c046a42c-6fe2-441c-8c8c-71466251a162
:100644 100644 65af9a6d879e922ad0e90bd110f087ac81032bcf
5e64fa43cae3b7fc12507621351cd4d0b82cb4b0 M cpu-exec.c
:040000 040000 f519a87338e29fd5d3a642698fd4dd405bf19024
adfd50c255dccdee1098c3131cca5c20453d19f9 M target-sparc
next prev parent reply other threads:[~2008-08-28 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 12:55 [Qemu-devel] [sparc64] qemu crashes after the "OpenBIOS for Sparc64" banner is printed Jakub Jermar
2008-08-28 15:57 ` Blue Swirl
2008-08-28 16:08 ` Jakub Jermar
2008-08-28 16:30 ` Blue Swirl
2008-08-28 16:59 ` Jakub Jermar
2008-08-28 17:16 ` Blue Swirl
2008-08-28 19:05 ` Blue Swirl [this message]
2008-08-29 18:37 ` Blue Swirl
2008-08-29 19:22 ` Paul Brook
2008-08-29 19:54 ` Blue Swirl
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=f43fc5580808281205r5b3f1965l116584b60c7d5977@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=jakub@jermar.eu \
--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).