All of lore.kernel.org
 help / color / mirror / Atom feed
From: Meng Xu <xumengpanda@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Question about Xen reboot on panic
Date: Wed, 11 Nov 2015 21:10:54 -0500	[thread overview]
Message-ID: <CAENZ-+n2krrv8LCOFK8GqAcsqOrrGPtM=vyBeaB4jthDWX8GGg@mail.gmail.com> (raw)
In-Reply-To: <5643D091.7090503@citrix.com>

Hi Andrew,

2015-11-11 18:34 GMT-05:00 Andrew Cooper <andrew.cooper3@citrix.com>:
> On 11/11/2015 23:21, Meng Xu wrote:
>>
>>> Finally, I can't tell from your paste below, but ensure that you are
>>> always using a debug hypervisor.
>> The source file Config.mk under the xen folder has
>> debug ?= y
>>
>> In addition,  "xl dmesg |grep debug" gives me:
>>
>> (XEN) Xen version 4.6-unstable (root@) (gcc (Ubuntu/Linaro
>> 4.6.3-1ubuntu5) 4.6.3) debug=y Wed Nov 11 17:06:30 EST 2015
>>
>> So I guess I'm using the debug hypervisor.
>
> You are
>
>>
>> I reboot the system after removing all of those useless options (that
>> is, no more "reboot=k panic=2 panic_on_oops=1" in the Xen boot command
>> line.)
>>
>> Is there anything else I can do to force Xen always reboot at panic or oops?
>
> Unless you specify noreboot, Xen will try its hardest to reboot the
> system.  It is possible that you have a dodgy firmware which interacts
> poorly with the default methods.
>
> Does normal reboot from dom0 work as intended?

Yes. Before Xen crashes, I can reboot the machine dom0 or from a serial port.

>
> If not, debug in the following order:
>
> * `reboot` from the dom0 shell
> * `echo b > /proc/sysrq-trigger` from the dom0 shell
> * `xl debug-keys R` from the dom0 shell

All of these three approaches can reboot the machine successfully.


> * CTRL-A x3, R from the serial console
I think "Ctrl-A" means that I should press "Ctrl + A" three times. Am I correct?
When I press Ctrl-A twice, it shows "No other window"; after I press
"Ctrl-A" for three consecutive times, and press R (or r), it shows
"+wrap" in the serial port.

>From the serial console, I can press "Ctrl+o, b" to reboot the machine
when Xen hasn't crashed. But when Xen crashed, serial port won't work.

BTW, the serial port is an PCI serial port instead of the legacy
serial port on the motherboard. Is the PCI serial port a problem? On
another machine with the legacy serial port, I can use "Ctrl - o, b"
to reboot even when system crashes. :-(

>
> Those are the reboot options.  It is also possible that a kexec kernel
> is being loaded and that is getting stuck.
>
> The crash options are:
> * `kexec -p`
> * `echo c > /proc/sysrq-trigger`
> * `xl debug-keys C`

The "xl debug-keys c" will not reboot the system, but it will print
out the crash message in the serial console.

>
> If those don't work then you will need to start instrumenting Xen to
> work out where stuff is going wrong.

It seems all of the above commands work on my machine (except for the
Ctrl-A x3, R). Is there anything else I can do to force the system
reboot at panic?

Thank you very much for your time and help in this problem!

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-12  2:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 22:49 Question about Xen reboot on panic Meng Xu
2015-11-11 22:54 ` Andrew Cooper
2015-11-11 23:21   ` Meng Xu
2015-11-11 23:34     ` Andrew Cooper
2015-11-12  2:10       ` Meng Xu [this message]
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-+n2krrv8LCOFK8GqAcsqOrrGPtM=vyBeaB4jthDWX8GGg@mail.gmail.com' \
    --to=xumengpanda@gmail.com \
    --cc=andrew.cooper3@citrix.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.