All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	"Berg, Johannes" <johannes.berg@intel.com>,
	kvm <kvm@vger.kernel.org>,
	Intel Linux Wireless <ilw@linux.intel.com>
Subject: Re: [Ilw] iwlagn and kvm related "BUG: scheduling while atomic" after resuming
Date: Tue, 19 Jul 2011 12:16:54 +0300	[thread overview]
Message-ID: <4E254B86.5080004@redhat.com> (raw)
In-Reply-To: <20110719091317.GP2400@redhat.com>

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


  reply	other threads:[~2011-07-19  9:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 19:14 iwlagn and kvm related "BUG: scheduling while atomic" after resuming Stefan Hajnoczi
2011-07-18 20:18 ` [Ilw] " Berg, Johannes
2011-07-18 21:51   ` Stefan Hajnoczi
2011-07-19  9:04     ` Avi Kivity
2011-07-19  9:13       ` Gleb Natapov
2011-07-19  9:16         ` Avi Kivity [this message]
2011-07-19  9:18           ` Gleb Natapov
2011-07-19 14:23       ` Stefan Hajnoczi
2011-07-19 16:51         ` Avi Kivity
2011-07-19 20:20           ` Stefan Hajnoczi
2011-07-19 20:27             ` Stefan Hajnoczi

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=4E254B86.5080004@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=ilw@linux.intel.com \
    --cc=johannes.berg@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=stefanha@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.