From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Rushikesh Jadhav <2rushikeshj@gmail.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen host crash
Date: Thu, 29 Aug 2013 17:25:13 +0100 [thread overview]
Message-ID: <521F75E9.7060006@citrix.com> (raw)
In-Reply-To: <CAO9XypWGtbMLfuVC57kfuOHEjj1rWzGhiMcy_rEHS_xHLxQFQQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1602 bytes --]
On 29/08/13 17:22, Rushikesh Jadhav wrote:
> Hi People,
>
> I had a crash of Xen [ 3.4.2 ] host today and the crash log was dumped
> in /var/crash/
>
> While analyzing the crash log & call trace on this 24 PCPU host, I
> found that some of PCPUs were in idle state & many were having same
> call trace as
>
> PCPU7
> Call Trace:
> [ffff828c8010e310] dump_domains+0x4d0
> ffff828c80175b7c crash_nmi_callback+0x2c
> ffff828c8015f2f9 do_nmi+0x39
> ffff828c801d6877 handle_ist_exception+0x52
> ffff828c801787b2 acpi_safe_halt+0x2
>
>
> Only one PCPU has got call trace as
>
> PCPU6
> Call Trace:
> [ffff828c8010e310] dump_domains+0x4d0
> ffff828c8010eeb7 kexec_crash+0x57
> ffff828c80127b36 panic+0x136
> ffff828c8011b7da __print_symbol+0x8a
> ffff828c8019b4ab vmx_asm_vmexit_handler+0x6b
> ffff828c80100000 __per_cpu_shift+0x800ffff4
> ffff828c8015eb75 show_stack+0x155
> ffff828c8015eeba fatal_trap+0x6a
> ffff828c801567a1 nmi_watchdog_tick+0x131
> ffff828c8015f37f do_nmi+0xbf
> ffff828c801d6877 handle_ist_exception+0x52
> ffff828c8011ab02 _spin_lock+0x12
>
> Can anyone please help me understand this & try to find out crash cause ?
> There are no error logs in messages or kernel at the time of crash.
>
> I checked for C-States and it is set to 2.
>
> Thanks.
This is a spinlock deadlock, resulting in the NMI watchdog timing out
and killing the host. Do you have Stack and register dump for PCPU6 ?
~Andrew
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 4755 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-08-29 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 16:22 Xen host crash Rushikesh Jadhav
2013-08-29 16:25 ` Andrew Cooper [this message]
2013-08-29 16:38 ` Rushikesh Jadhav
2013-08-29 17:02 ` Andrew Cooper
2013-08-29 19:10 ` Rushikesh Jadhav
2013-08-29 19:15 ` Andrew Cooper
2013-08-29 19:46 ` Rushikesh Jadhav
2013-08-30 9:51 ` Andrew Cooper
-- strict thread matches above, loose matches on Subject: below --
2019-03-02 18:28 Xen Host Crash Rishi
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=521F75E9.7060006@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=2rushikeshj@gmail.com \
--cc=xen-devel@lists.xen.org \
/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.