From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Oops on 2.6.23.11 with KVM 57 Date: Sat, 22 Dec 2007 21:59:43 +0200 Message-ID: <476D6CAF.2030009@qumranet.com> References: <20071221132611.GA11812@bogon.ms20.nix> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Guido Guenther Return-path: In-Reply-To: <20071221132611.GA11812-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org> 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 Guido Guenther wrote: > Hi, > I got the Oops below on an Dual CPU Dual-Core AMD Opteron(tm) Processor > 2220 running a 32bit kernel. Kernel is 2.6.23.11, kvm version 57. > Doesn't happen all the time but usually right at VM startup. Seems to be > easier to trigger when starting up several VMs in row. What guest are you running? smp or uni? > Call Trace: > [] pic_update_irq+0x68/0x80 [kvm] > [] kvm_pic_read_irq+0x6e/0xe0 [kvm] > Please do gdb /path/to/kvm.ko disassemble pic_update_irq and post the results. If you recompiled the module since getting the oops, please generate a fresh oops. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/