From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "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 19:51:09 +0300 [thread overview]
Message-ID: <4E25B5FD.208@redhat.com> (raw)
In-Reply-To: <CAJSP0QV7sKV0pZo_8Ur3_c1k37U0UBwPLLiSPC5=jT7=Qrcf+Q@mail.gmail.com>
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
next prev parent reply other threads:[~2011-07-19 16:51 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
2011-07-19 9:18 ` Gleb Natapov
2011-07-19 14:23 ` Stefan Hajnoczi
2011-07-19 16:51 ` Avi Kivity [this message]
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=4E25B5FD.208@redhat.com \
--to=avi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox