All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gerhard Wiesinger <lists@wiesinger.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Fix wide ioport access cracking
Date: Thu, 11 Aug 2011 11:29:43 +0300	[thread overview]
Message-ID: <4E4392F7.8020002@redhat.com> (raw)
In-Reply-To: <4E43927B.90606@redhat.com>

On 08/11/2011 11:27 AM, Avi Kivity wrote:
> On 08/11/2011 11:25 AM, Gerhard Wiesinger wrote:
>> Hello Avi,
>>
>> Thank for the fast fix. Unfortunatly it still doesn't work (but LSI 
>> BIOS is initialized correctly).
>>
>> I'm getting at boot time:
>> qemu-system-x86_64: /qemu-kvm-test/memory.c:1168: 
>> memory_region_del_subregion: Assertion `subregion->parent == mr' failed.
>
> What OS are you booting?  What is your qemu command line?  How early 
> is the failure?
>

Alternatively, build with debug information (./configure --enable-debug) 
enable core dumps ('ulimit -c unlimited'), and post a backtrace:

  gdb qemu-system-x86_64 /path/to/core
  (gdb) bt

It should be immediately apparent where the failure is.

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Gerhard Wiesinger <lists@wiesinger.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Fix wide ioport access cracking
Date: Thu, 11 Aug 2011 11:29:43 +0300	[thread overview]
Message-ID: <4E4392F7.8020002@redhat.com> (raw)
In-Reply-To: <4E43927B.90606@redhat.com>

On 08/11/2011 11:27 AM, Avi Kivity wrote:
> On 08/11/2011 11:25 AM, Gerhard Wiesinger wrote:
>> Hello Avi,
>>
>> Thank for the fast fix. Unfortunatly it still doesn't work (but LSI 
>> BIOS is initialized correctly).
>>
>> I'm getting at boot time:
>> qemu-system-x86_64: /qemu-kvm-test/memory.c:1168: 
>> memory_region_del_subregion: Assertion `subregion->parent == mr' failed.
>
> What OS are you booting?  What is your qemu command line?  How early 
> is the failure?
>

Alternatively, build with debug information (./configure --enable-debug) 
enable core dumps ('ulimit -c unlimited'), and post a backtrace:

  gdb qemu-system-x86_64 /path/to/core
  (gdb) bt

It should be immediately apparent where the failure is.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2011-08-11  8:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11  7:40 [PATCH 0/2] Fix wide ioport access cracking Avi Kivity
2011-08-11  7:40 ` [Qemu-devel] " Avi Kivity
2011-08-11  7:40 ` [PATCH 1/2] memory: abstract cracking of write access ops into a function Avi Kivity
2011-08-11  7:40   ` [Qemu-devel] " Avi Kivity
2011-08-11  7:40 ` [PATCH 2/2] memory: crack wide ioport accesses into smaller ones when needed Avi Kivity
2011-08-11  7:40   ` [Qemu-devel] " Avi Kivity
2011-08-11  8:25 ` [PATCH 0/2] Fix wide ioport access cracking Gerhard Wiesinger
2011-08-11  8:25   ` [Qemu-devel] " Gerhard Wiesinger
2011-08-11  8:27   ` Avi Kivity
2011-08-11  8:27     ` [Qemu-devel] " Avi Kivity
2011-08-11  8:29     ` Avi Kivity [this message]
2011-08-11  8:29       ` Avi Kivity
2011-08-11  9:01       ` Gerhard Wiesinger
2011-08-11  9:01         ` [Qemu-devel] " Gerhard Wiesinger
2011-08-11  9:44         ` Avi Kivity
2011-08-11 16:08           ` Gerhard Wiesinger
2011-08-11 16:20             ` Avi Kivity
2011-08-11 16:22               ` Avi Kivity
2011-08-11 19:01                 ` Gerhard Wiesinger
2011-08-22 10:46                   ` Avi Kivity
2011-08-11 16:11           ` Gerhard Wiesinger
2011-08-11 16:15             ` Avi Kivity
2011-08-22 14:42 ` Anthony Liguori

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=4E4392F7.8020002@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=lists@wiesinger.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 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.