From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Ben Guthro <benjamin.guthro@citrix.com>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: [BUG?] Interrupts enabled after xen_acpi_processor_resume+0x0/0x34 [xen_acpi_processor]
Date: Tue, 28 Jan 2014 16:08:49 +0100 [thread overview]
Message-ID: <20140128150848.GA1428@redhat.com> (raw)
Hi,
We have this bug report on our bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1058268
In short:
WARNING: CPU: 0 PID: 6733 at drivers/base/syscore.c:104 syscore_resume+0x9a/0xe0()
Interrupts enabled after xen_acpi_processor_resume+0x0/0x34 [xen_acpi_processor]
Perhaps I'm wrong, but I think sysops->resume() callback should be
atomic i.e. can not use mutexes or kmalloc(,GFP_KERNEL), what is not
true regarding xen_acpi_processor_resume(). That callback was introduced
by commit 3fac10145b766a2244422788f62dc35978613fd8. Fixing that will
not be easy IMHO, but maybe you have some ideas ? :-)
Stanislaw
next reply other threads:[~2014-01-28 15:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 15:08 Stanislaw Gruszka [this message]
2014-01-28 16:04 ` [BUG?] Interrupts enabled after xen_acpi_processor_resume+0x0/0x34 [xen_acpi_processor] Konrad Rzeszutek Wilk
2014-01-29 5:24 ` David Rientjes
2014-01-29 8:25 ` Stanislaw Gruszka
2014-01-31 14:04 ` Stanislaw Gruszka
2014-01-31 16:01 ` Konrad Rzeszutek Wilk
2014-02-03 10:12 ` Stanislaw Gruszka
2014-02-03 14:14 ` Konrad Rzeszutek Wilk
2014-02-10 14:37 ` Konrad Rzeszutek Wilk
2014-02-26 10:26 ` Stanislaw Gruszka
2014-02-26 10:30 ` [PATCH] xen/acpi-processor: fix enabling interrupts on syscore_resume Stanislaw Gruszka
2014-03-14 17:14 ` [BUG?] Interrupts enabled after xen_acpi_processor_resume+0x0/0x34 [xen_acpi_processor] Konrad Rzeszutek Wilk
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=20140128150848.GA1428@redhat.com \
--to=sgruszka@redhat.com \
--cc=benjamin.guthro@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).