public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Guido Guenther <agx-wGvLLbajjwFAfugRpC6u6w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Oops on 2.6.23.11 with KVM 57
Date: Sat, 22 Dec 2007 21:59:43 +0200	[thread overview]
Message-ID: <476D6CAF.2030009@qumranet.com> (raw)
In-Reply-To: <20071221132611.GA11812-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.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: 
>  [<f8d498d8>] pic_update_irq+0x68/0x80 [kvm] 
>  [<f8d49f8e>] 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/

  parent reply	other threads:[~2007-12-22 19:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 13:26 Oops on 2.6.23.11 with KVM 57 Guido Guenther
     [not found] ` <20071221132611.GA11812-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org>
2007-12-22 19:59   ` Avi Kivity [this message]
     [not found]     ` <476D6CAF.2030009-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-27  9:41       ` Guido Guenther
     [not found]         ` <20071227094136.GB824-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org>
2007-12-27 10:34           ` Avi Kivity
     [not found]             ` <47737FD2.1060802-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-28 20:25               ` Guido Guenther
     [not found]                 ` <20071228202510.GA2980-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org>
2007-12-28 20:53                   ` Izik Eidus
     [not found]                     ` <47756261.4000104-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-03  9:47                       ` [PATCH] use rtl8139 as default network adapter Guido Guenther
     [not found]                         ` <20080103094752.GA6778-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org>
2008-01-03 12:43                           ` Avi Kivity
2008-01-08 11:22                           ` [PATCH] use rtl8139 for bootp too and adjust docs accordingly Guido Guenther
     [not found]                             ` <20080108112255.GB6651-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org>
2008-01-08 13:51                               ` Avi Kivity
2007-12-28 22:43                   ` Oops on 2.6.23.11 with KVM 57 Yves Dorfsman

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=476D6CAF.2030009@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=agx-wGvLLbajjwFAfugRpC6u6w@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