All of lore.kernel.org
 help / color / mirror / Atom feed
From: Meng Xu <xumengpanda@gmail.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Wei Liu <wei.liu2@citrix.com>
Subject: Question about Xen reboot on panic
Date: Wed, 11 Nov 2015 17:49:10 -0500	[thread overview]
Message-ID: <CAENZ-+n8P-msTZPFvddGYyS7EhCmTUyjt4vCMsp=KQh5JJUaTQ@mail.gmail.com> (raw)

Hi all,

I'm trying to work remotely with the machine I have. So I want Xen
automatically reboot if it experiences a panic.

When Xen panic, it says " Reboot in five seconds...". However, it does
not reboot. :-(

*** The xen boot command line on my machine is ***
multiboot   /boot/xen-4.6-unstable.gz placeholder
dom0_mem=8192M,max:8192M dom0_max_vcpus=8 sched=credit
com1=115200,8n1,pci console=com1,vga reboot=k panic=2 panic_on_oops=1

*** The dom0's boot command line on my machine is ***
 module  /boot/vmlinuz-3.8.0-44-generic placeholder root=/dev/sda5 ro
panic=10 panic_on_oops=1 console=hvc0,115200n8 earlyprintk=xen quiet
splash

I'm actually not quite sure if I should add "reboot=k panic=2
panic_on_oops=1" into both command lines. But if I remove them, Xen
still won't reboot on some panic.

For example, if I boot into modified RTDS scheduler on Xen 4.6
unstable, it experiences panic as follows:

(XEN) Xen call trace:

(XEN)    [<ffff82d080128479>] rt_vcpu_remove+0x87/0xf9

(XEN)    [<ffff82d08012ab06>] sched_destroy_vcpu+0x98/0xed

(XEN)    [<ffff82d08010571f>] complete_domain_destroy+0x52/0x17f

(XEN)    [<ffff82d0801360d8>] rcu_process_callbacks+0x149/0x1a6

(XEN)    [<ffff82d08012d243>] __do_softirq+0x133/0x147

(XEN)    [<ffff82d08012d28f>] process_pending_softirqs+0x38/0x3a

(XEN)    [<ffff82d0801afbff>] mwait_idle+0x10a/0x2fb

(XEN)    [<ffff82d0801640c2>] idle_loop+0x51/0x6b

(XEN)

(XEN)

(XEN) ****************************************

(XEN) Panic on CPU 5:

(XEN) GENERAL PROTECTION FAULT

(XEN) [error_code=0000]

(XEN) ****************************************

(XEN)

(XEN) Reboot in five seconds...

***It says  "Reboot in five seconds", but I want for 1 min and nothing
happened. :-(


Did anyone happen to know why Xen does not reboot under this situation?
(Xen could reboot if it fails on an ASSERT())

Thank you very much for your time and help!

Best regards,

Meng

-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/

             reply	other threads:[~2015-11-11 22:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 22:49 Meng Xu [this message]
2015-11-11 22:54 ` Question about Xen reboot on panic Andrew Cooper
2015-11-11 23:21   ` Meng Xu
2015-11-11 23:34     ` Andrew Cooper
2015-11-12  2:10       ` Meng Xu
2015-11-12 12:52         ` Andrew Cooper
2015-11-12 12:57           ` Wei Liu
2015-11-12 13:16             ` Ian Campbell
2015-11-12 15:09               ` Meng Xu
2015-11-12 15:07           ` Meng Xu
2015-11-12 16:13             ` Meng Xu
2015-11-12 16:57               ` Meng Xu
2015-11-12 17:08                 ` Jan Beulich
2015-11-12 19:54                   ` Meng Xu
2015-11-13  7:39                     ` Jan Beulich
2015-11-19  3:58                       ` Meng Xu
2015-11-19  7:26                         ` Jan Beulich

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='CAENZ-+n8P-msTZPFvddGYyS7EhCmTUyjt4vCMsp=KQh5JJUaTQ@mail.gmail.com' \
    --to=xumengpanda@gmail.com \
    --cc=wei.liu2@citrix.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.