From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Ilw] iwlagn and kvm related "BUG: scheduling while atomic" after resuming Date: Tue, 19 Jul 2011 19:51:09 +0300 Message-ID: <4E25B5FD.208@redhat.com> References: <4E254895.4020606@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Berg, Johannes" , kvm , Intel Linux Wireless To: Stefan Hajnoczi Return-path: Received: from mx1.redhat.com ([209.132.183.28]:9752 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751092Ab1GSQvQ (ORCPT ); Tue, 19 Jul 2011 12:51:16 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 07/19/2011 05:23 PM, Stefan Hajnoczi wrote: > > > > Can you post some disassembly around %rip? > > Here is the kvm.ko disassembly for %rip = kvm_arch_vcpu_ioctl_run+0x927. > > I think at runtime the pvops bit should be patched and we should just > have a sti instruction? Yes, it's a local_irq_enable() (followed by a 4-byte nop; %rip points past the nop due to interrupt shadow). > I don't understand the backtrace. It prints out the interrupt handler > stack frames but %rip appears to be down in kvm.ko. If there is an > interrupt handler running shouldn't %rip be in there? The interrupt handler finished running; just before returning it called the scheduler (which it shouldn't have, since we're in a preempt_disabled() section). > Unfortunately the full oops scrolled off the screen so I only have > panic1.jpg and panic2.jpg. We're missing earlier information. Is it > possible that there was another panic first and that kvm.ko is just > dying in the aftermath? It's possible. Is this reproducible? If so please set up netconsole or kdump. -- error compiling committee.c: too many arguments to function