All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: BuraphaLinux Server <buraphalinuxserver@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: random crash in post_kvm_run()
Date: Tue, 29 Jun 2010 15:16:53 +0300	[thread overview]
Message-ID: <4C29E435.1040201@redhat.com> (raw)
In-Reply-To: <AANLkTil8Fp0C-z6HnyRNaenAfPkPnf3i-KAe4HWbuo3X@mail.gmail.com>

On 06/28/2010 08:28 PM, BuraphaLinux Server wrote:
> Hello,
>
>      I have tried qemu_kvm 0.12.4 release and also git from about 1/2
> an hour ago.  In both cases, I crash in the post_kvm_run() function on
> the line about:
>
> pthread_mutex_lock(&qemu_mutex);
>
> The command I use to run qemu worked great with
> glibc-2.11.1,linux-2.6.32.14,and gcc-4.4.3,
> but I have upgraded to glibc-2.11.2, linux-2.6.34, and gcc-4.4.4 and get this:
>
>    

Can you downgrade the kernel to a known good one to see which component 
causes the failure?

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


  parent reply	other threads:[~2010-06-29 12:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 17:28 random crash in post_kvm_run() BuraphaLinux Server
2010-06-28 18:38 ` Brian Jackson
2010-06-30 17:57   ` BuraphaLinux Server
2010-06-29 12:16 ` Avi Kivity [this message]
2010-06-30 18:25   ` BuraphaLinux Server
2010-07-01 11:44     ` Avi Kivity
2010-07-02 19:08       ` BuraphaLinux Server
2010-07-03 10:28         ` Avi Kivity
2010-07-03 14:23           ` BuraphaLinux Server
2010-07-05  7:42             ` Avi Kivity
2010-07-05  8:52               ` BuraphaLinux Server
2010-07-05 10:15                 ` Avi Kivity
2010-07-06  7:46               ` Avi Kivity
2010-07-06  8:37                 ` Avi Kivity
2010-07-06 15:58                   ` BuraphaLinux Server
2010-07-07  9:12                     ` Avi Kivity
2010-06-30 18:06 ` Anthony Liguori
2010-06-30 18:32   ` BuraphaLinux Server

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=4C29E435.1040201@redhat.com \
    --to=avi@redhat.com \
    --cc=buraphalinuxserver@gmail.com \
    --cc=kvm@vger.kernel.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.