From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>
Subject: PV multiconsole bug during resume.
Date: Thu, 24 May 2012 15:37:14 -0400 [thread overview]
Message-ID: <20120524193714.GA29726@phenom.dumpdata.com> (raw)
So .. we used to have in the event.c a spin_lock to protect the
irq_mapping_update_lock, but with git commit 773659483685d652970583384a0294948e57f8b3
"xen/irq: Alter the locking to use a mutex instead of a spinlock."
I changed it to a mutex b/c we keept on getting WARNs.
But now I get this when I resume a PVHVM guest:
Grant tables using version 2 layout.
BUG: sleeping function called from invalid context at /home/konrad/ssd/linux/kernel/mutex.c:85
in_atomic(): 1, irqs_disabled(): 1, pid: 6, name: migration/0
Pid: 6, comm: migration/0 Tainted: G O 3.4.0upstream-00113-g598ff45-dirty #1
Call Trace:
[<ffffffff8109830a>] __might_sleep+0xda/0x100
[<ffffffff815a47f7>] mutex_lock+0x27/0x50
[<ffffffff81311ea6>] rebind_evtchn_irq+0x36/0x90
[<ffffffff81341bfc>] xen_console_resume+0x5c/0x60
[<ffffffff81313fea>] xen_suspend+0x8a/0xb0
[<ffffffff810d42f3>] stop_machine_cpu_stop+0xa3/0xf0
[<ffffffff810d4250>] ? stop_one_cpu_nowait+0x50/0x50
[<ffffffff810d3f81>] cpu_stopper_thread+0xf1/0x1c0
[<ffffffff815a5be6>] ? __schedule+0x3c6/0x760
[<ffffffff815a6bb9>] ? _raw_spin_unlock_irqrestore+0x19/0x30
[<ffffffff810d3e90>] ? res_counter_charge+0x150/0x150
[<ffffffff8108e636>] kthread+0x96/0xa0
[<ffffffff815aeb24>] kernel_thread_helper+0x4/0x10
[<ffffffff815a7138>] ? retint_restore_args+0x5/0x6
[<ffffffff815aeb20>] ? gs_change+0x13/0x13
PM: noirq restore of devices complete after 0.163 msecs
Any ideas?
next reply other threads:[~2012-05-24 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 19:37 Konrad Rzeszutek Wilk [this message]
2012-05-25 8:56 ` PV multiconsole bug during resume Ian Campbell
2012-05-25 9:31 ` Stefano Stabellini
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=20120524193714.GA29726@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.