From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [Ilw] iwlagn and kvm related "BUG: scheduling while atomic" after resuming Date: Tue, 19 Jul 2011 12:18:50 +0300 Message-ID: <20110719091850.GR2400@redhat.com> References: <4E254895.4020606@redhat.com> <20110719091317.GP2400@redhat.com> <4E254B86.5080004@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Stefan Hajnoczi , "Berg, Johannes" , kvm , Intel Linux Wireless To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:57448 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752332Ab1GSJSy (ORCPT ); Tue, 19 Jul 2011 05:18:54 -0400 Content-Disposition: inline In-Reply-To: <4E254B86.5080004@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Jul 19, 2011 at 12:16:54PM +0300, Avi Kivity wrote: > 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. > Yes, and soft irq depth count should prevent that too. Very strange. -- Gleb.