qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] PPC* and Sparc32 crash
Date: Wed, 24 Aug 2011 21:20:10 +0300	[thread overview]
Message-ID: <4E5540DA.90704@redhat.com> (raw)
In-Reply-To: <CAAu8pHtUTvw+HxO79mGy-MbKYMJZSFP3R2D1fH6AptZso8MvPg@mail.gmail.com>

On 08/24/2011 08:48 PM, Blue Swirl wrote:
> On Wed, Aug 24, 2011 at 9:41 AM, Avi Kivity<avi@redhat.com>  wrote:
> >  On 08/23/2011 08:55 PM, Blue Swirl wrote:
> >>
> >>  qemu-system-ppc: /src/qemu/memory.c:1183:
> >>  memory_region_add_subregion_common: Assertion `!subregion->parent'
> >>  failed.
> >>  Aborted
> >>  qemu-system-ppc64: /src/qemu/memory.c:1183:
> >>  memory_region_add_subregion_common: Assertion `!subregion->parent'
> >>  failed.
> >>  Aborted
> >>  qemu-system-sparc: /src/qemu/hw/sysbus.c:156:
> >>  sysbus_register_withprop: Assertion `info->qdev.size>=
> >>  sizeof(SysBusDevice)' failed.
> >>  Aborted
> >>
> >>  This is with b861b7419c49ad53e786062b4fbf6da53468f130. Other targets
> >>  seem to work.
> >
> >  Please provide disk images and command line options, and I will investigate.
>
> Most legitimate command lines even without any images will do:
> $ ./obj-amd64/ppc-softmmu/qemu-system-ppc
> qemu-system-ppc: /src/qemu/memory.c:1183:
> memory_region_add_subregion_common: Assertion `!subregion->parent'
> failed.
> Aborted
>

Here the issue is that escc is both a sysbus device at 0x80013000 and a 
a PCI device.  Is this really correct?

In any case, I will post a patch making it behave like it did before the 
conversion, and leave any extra fixes to someone who knows the device.


-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

  reply	other threads:[~2011-08-24 18:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 17:55 [Qemu-devel] PPC* and Sparc32 crash Blue Swirl
2011-08-23 17:59 ` Peter Maydell
2011-08-23 19:19   ` Edgar E. Iglesias
2011-08-24 17:49     ` Blue Swirl
2011-08-24 18:14       ` Edgar E. Iglesias
2011-08-24 18:16       ` Edgar E. Iglesias
2011-08-24 18:39         ` Edgar E. Iglesias
2011-08-24 19:09           ` [Qemu-devel] [PATCH] gt64xxx: fix crash in gt64120_pci_mapping() Avi Kivity
2011-08-24 19:17             ` Edgar E. Iglesias
2011-08-24 17:54   ` [Qemu-devel] PPC* and Sparc32 crash Blue Swirl
2011-08-24 18:05     ` Peter Maydell
2011-08-24  9:41 ` Avi Kivity
2011-08-24 17:48   ` Blue Swirl
2011-08-24 18:20     ` Avi Kivity [this message]
2011-08-24 18:40     ` [Qemu-devel] [PATCH] ppc_oldworld, ppc_newworld: fix escc BAR related crash Avi Kivity
2011-08-24 18:43     ` [Qemu-devel] PPC* and Sparc32 crash Avi Kivity
2011-08-24 19:43       ` Blue Swirl
2011-08-24 19:59         ` Avi Kivity
2011-08-24 20:02           ` Blue Swirl
2011-08-25  4:43             ` Avi Kivity
2011-08-25 17:33               ` Blue Swirl
2011-08-25 19:31                 ` Avi Kivity
2011-08-25 20:17                   ` 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=4E5540DA.90704@redhat.com \
    --to=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --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).