public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: antiwire-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: kvm-45 possible bug report
Date: Mon, 08 Oct 2007 18:22:20 +0200	[thread overview]
Message-ID: <470A593C.4020904@qumranet.com> (raw)
In-Reply-To: <ebbe6c180710080916p78378142p10d4b5279978d0ee-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

antiwire-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> Hello,
> I have attached documentation for a segfault that happens on my system
> using kvm-45 but does not happen with kvm-44. I included what I
> thought was relevant.
> Using modules that were built during kernel build.
> I have gcc3.4 compatibility tools installed that are along side my
> distro's gcc4 setup. The gcc3.4 compat package came from a known good
> package build that was located my distro's main server ftp.
> This probably complicates the whole situation but I felt that it would
> be best to at least submit something in case I'm not the only one.
>
> Attached:
> My kernel config, make output (make > make.log 2>&1) ; modules info,
> /proc/cpuinfo, commands used to execute.
>
> Thanks for your time and for your work on the kvm tools.


Please generate a core ('ulimit -c unlimited' is usually needed) and a
backtrace with gdb, and post that.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

      parent reply	other threads:[~2007-10-08 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 16:16 kvm-45 possible bug report antiwire-Re5JQEeQqe8AvxtiuMwx3w
     [not found] ` <ebbe6c180710080916p78378142p10d4b5279978d0ee-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-08 16:22   ` Avi Kivity [this message]

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=470A593C.4020904@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=antiwire-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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