All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Stack corruption problem with SeaBIOS/gPXE under QEMU
Date: Sun, 29 Nov 2009 12:58:27 +0200	[thread overview]
Message-ID: <4B1253D3.2040508@redhat.com> (raw)
In-Reply-To: <20091121004702.GA25435@morn.localdomain>

On 11/21/2009 02:47 AM, Kevin O'Connor wrote:
>
> Can you retry this with the latest seabios git.  If you are able to
> reproduce, can you set CONFIG_DEBUG_LEVEL to 8 and post the log?
> Maybe something in the log will help.
>    

With current seabios.git the problem is resolved.

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

  reply	other threads:[~2009-11-29 10:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 11:20 [Qemu-devel] Stack corruption problem with SeaBIOS/gPXE under QEMU Naphtali Sprei
2009-11-14 19:47 ` Kevin O'Connor
2009-11-15  9:43   ` Naphtali Sprei
2009-11-16 13:36   ` Avi Kivity
2009-11-16 14:02     ` Avi Kivity
2009-11-17  2:26       ` Kevin O'Connor
2009-11-17 13:23         ` Avi Kivity
2009-11-21  0:47           ` Kevin O'Connor
2009-11-29 10:58             ` Avi Kivity [this message]
2009-11-18  9:39         ` Gleb Natapov
2009-11-18  9:49           ` Alexander Graf
2009-11-18  9:53             ` Gleb Natapov
2009-11-18 12:58             ` Kevin O'Connor
2009-11-18 13:06           ` Kevin O'Connor
2009-11-18 14:22             ` Gleb Natapov
2009-11-18 15:38               ` [gPXE] " Joshua Oreman
2009-11-19  1:07               ` Kevin O'Connor
2009-11-18 13:50           ` Avi Kivity
2009-11-18 14:19             ` Gleb Natapov
2009-11-18 14:21               ` Avi Kivity
2009-11-20 22:39   ` Kevin O'Connor

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=4B1253D3.2040508@redhat.com \
    --to=avi@redhat.com \
    --cc=kevin@koconnor.net \
    --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.