From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm-45 possible bug report Date: Mon, 08 Oct 2007 18:22:20 +0200 Message-ID: <470A593C.4020904@qumranet.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: antiwire-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.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/