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 12:16:54 +0300 Message-ID: <4E254B86.5080004@redhat.com> References: <4E254895.4020606@redhat.com> <20110719091317.GP2400@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Stefan Hajnoczi , "Berg, Johannes" , kvm , Intel Linux Wireless To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:37069 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752460Ab1GSJRA (ORCPT ); Tue, 19 Jul 2011 05:17:00 -0400 In-Reply-To: <20110719091317.GP2400@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 07/19/2011 12:13 PM, Gleb Natapov wrote: > > Preemption is still disabled at this point. Where does the > > "scheduling while atomic" come from? Nothing in this area attempts > > to schedule. > > > 0x10000000 in preemption counter is PREEMPT_ACTIVE, so this looks like > preemptable kernel tries to preempt itself. > Yes, it's the wlan interrupt comming after local_irq_enable(). But it still doesn't make sense. We're in a preempt_disable() section, so the scheduler shouldn't have been called in the first place. -- error compiling committee.c: too many arguments to function