From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Steven Haigh <netwiz@crc.id.au>,
xen-devel <xen-devel@lists.xenproject.org>,
linux-kernel@vger.kernel.org
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [Xen-devel] 4.4: INFO: rcu_sched self-detected stall on CPU
Date: Fri, 25 Mar 2016 12:20:11 -0400 [thread overview]
Message-ID: <56F5653B.1090700@oracle.com> (raw)
In-Reply-To: <56F56172.9020805@crc.id.au>
On 03/25/2016 12:04 PM, Steven Haigh wrote:
>
> It may not actually be the full logs. Once the system gets really upset,
> you can't run anything - as such, grabbing anything from dmesg is not
> possible.
>
> The logs provided above is all that gets spat out to the syslog server.
>
> I'll try tinkering with a few things to see if I can get more output -
> but right now, that's all I've been able to achieve. So far, my only
> ideas are to remove the 'quiet' options from the kernel command line -
> but I'm not sure how much that would help.
>
> Suggestions gladly accepted on this front.
You probably want to run connected to guest serial console ("
serial='pty' " in guest config file and something like 'loglevel=7
console=tty0 console=ttyS0,38400n8' on guest kernel commandline). And
start the guest with 'xl create -c <cfg>' or connect later with 'xl
console <domainID>'.
-boris
next prev parent reply other threads:[~2016-03-25 16:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 2:53 4.4: INFO: rcu_sched self-detected stall on CPU Steven Haigh
2016-03-25 2:53 ` Steven Haigh
2016-03-25 12:23 ` Boris Ostrovsky
2016-03-25 12:23 ` [Xen-devel] " Boris Ostrovsky
2016-03-25 14:05 ` Steven Haigh
2016-03-25 14:05 ` [Xen-devel] " Steven Haigh
2016-03-25 14:44 ` Boris Ostrovsky
2016-03-25 14:44 ` [Xen-devel] " Boris Ostrovsky
2016-03-25 16:04 ` Steven Haigh
2016-03-25 16:04 ` [Xen-devel] " Steven Haigh
2016-03-25 16:20 ` Boris Ostrovsky
2016-03-25 16:20 ` Boris Ostrovsky [this message]
2016-03-25 21:07 ` Steven Haigh
2016-03-25 21:07 ` Steven Haigh
2016-03-29 8:56 ` Steven Haigh
2016-03-29 14:14 ` Boris Ostrovsky
2016-03-29 17:44 ` Steven Haigh
2016-03-29 17:44 ` Steven Haigh
2016-03-29 18:04 ` Steven Haigh
2016-03-29 18:32 ` Steven Haigh
2016-03-30 13:44 ` Boris Ostrovsky
2016-03-30 13:44 ` Boris Ostrovsky
2016-05-02 20:54 ` gregkh
2016-05-03 15:11 ` Steven Haigh
2016-05-03 15:46 ` gregkh
2016-05-02 20:54 ` gregkh
2016-03-29 18:04 ` Steven Haigh
2016-04-02 1:50 ` Steven Haigh
2016-04-02 1:50 ` Steven Haigh
2016-03-29 14:14 ` Boris Ostrovsky
2016-03-29 8:56 ` Steven Haigh
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=56F5653B.1090700@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netwiz@crc.id.au \
--cc=xen-devel@lists.xenproject.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.