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. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
