From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Hypervisor error messages after xl block-detach with linux 3.18-rc5
Date: Mon, 24 Nov 2014 16:09:30 +0100 [thread overview]
Message-ID: <54734A2A.9000301@suse.com> (raw)
In-Reply-To: <54730F8F.7080905@suse.com>
On 11/24/2014 11:59 AM, Juergen Gross wrote:
> On 11/24/2014 11:20 AM, Jan Beulich wrote:
>>>>> On 24.11.14 at 10:55, <JGross@suse.com> wrote:
>>> - Sometimes I see only NMI watchdog messages, looking into hanging cpu
>>> state via xen debug keys I can see the cpu(s) in question are
>>> spinning
>>> in _raw_spin_lock():
>>> __handle_mm_fault()->__pte_alloc()->pmd_lock()->_raw_spin_lock()
>>> The hanging cpus were executing some random user processes (cron,
>>> bash, xargs), cr2 contained user addresses.
>>
>> Is this perhaps what
>> http://lists.xenproject.org/archives/html/xen-devel/2014-11/msg02135.html
>> appears to be about?
>
> Hmm, I'm not sure.
>
> I'll try a 3.17 kernel to verify.
Still seeing the issue, but less frequent. OTOH I just found in above
thread in lkml that 3.17 is showing that issue, too. :-(
I'll try to setup a pv-variant of Linus' patch and test it...
Juergen
next prev parent reply other threads:[~2014-11-24 15:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 8:42 Hypervisor error messages after xl block-detach with linux 3.18-rc5 Juergen Gross
2014-11-21 13:57 ` Konrad Rzeszutek Wilk
2014-11-24 9:55 ` Juergen Gross
2014-11-24 10:02 ` Ian Campbell
2014-11-25 16:10 ` Juergen Gross
2014-11-25 16:18 ` Ian Campbell
2014-11-25 16:48 ` Juergen Gross
2014-11-25 17:01 ` Juergen Gross
2014-11-24 10:20 ` Jan Beulich
[not found] ` <5473147C020000780004A3D5@suse.com>
2014-11-24 10:59 ` Juergen Gross
2014-11-24 15:09 ` Juergen Gross [this message]
2014-11-24 17:27 ` Juergen Gross
2014-11-25 7:50 ` Jan Beulich
2014-11-25 4:47 ` Juergen Gross
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=54734A2A.9000301@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.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.