From: Steven Haigh <netwiz@crc.id.au>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel <xen-devel@lists.xenproject.org>,
linux-kernel@vger.kernel.org
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: 4.4: INFO: rcu_sched self-detected stall on CPU
Date: Sat, 26 Mar 2016 08:07:06 +1100 [thread overview]
Message-ID: <56F5A87A.8000903__14139.954155735$1458940126$gmane$org@crc.id.au> (raw)
In-Reply-To: <56F5653B.1090700@oracle.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1555 bytes --]
On 26/03/2016 3:20 AM, Boris Ostrovsky wrote:
> 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>'.
Ok thanks, I've booted the DomU with:
$ cat /proc/cmdline
root=UUID=63ade949-ee67-4afb-8fe7-ecd96faa15e2 ro enforcemodulesig=1
selinux=0 fsck.repair=yes loglevel=7 console=tty0 console=ttyS0,38400n8
I've left a screen session attached to the console (via xl console) and
I'll see if that turns anything up. As this seems to be rather
unpredictable when it happens, it may take a day or two to get anything.
I just hope its more than the syslog output :)
--
Steven Haigh
Email: netwiz@crc.id.au
Web: https://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 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:[~2016-03-25 21:07 UTC|newest]
Thread overview: 14+ 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 12:23 ` Boris Ostrovsky
[not found] ` <56F52DBF.5080006@oracle.com>
2016-03-25 14:05 ` Steven Haigh
[not found] ` <56F545B1.8080609@crc.id.au>
2016-03-25 14:44 ` Boris Ostrovsky
[not found] ` <56F54EE0.6030004@oracle.com>
2016-03-25 16:04 ` Steven Haigh
[not found] ` <56F56172.9020805@crc.id.au>
2016-03-25 16:20 ` Boris Ostrovsky
[not found] ` <56F5653B.1090700@oracle.com>
2016-03-25 21:07 ` Steven Haigh [this message]
[not found] ` <56F5A87A.8000903@crc.id.au>
2016-03-29 8:56 ` Steven Haigh
[not found] ` <56FA4336.2030301@crc.id.au>
2016-03-29 14:14 ` Boris Ostrovsky
[not found] ` <56FA8DDD.7070406@oracle.com>
2016-03-29 17:44 ` Steven Haigh
[not found] ` <56FABF17.7090608@crc.id.au>
2016-03-29 18:04 ` Steven Haigh
[not found] ` <56FAC3AC.9050802@crc.id.au>
2016-03-30 13:44 ` Boris Ostrovsky
2016-05-02 20:54 ` gregkh
2016-04-02 1:50 ` 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='56F5A87A.8000903__14139.954155735$1458940126$gmane$org@crc.id.au' \
--to=netwiz@crc.id.au \
--cc=boris.ostrovsky@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).