Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1364764
| From | Boris Ostrovsky <boris.ostrovsky@oracle.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [Xen-devel] 4.4: INFO: rcu_sched self-detected stall on CPU |
| Date | 2016-03-25 17:30 +0100 |
| Message-ID | <rgCMx-4r7-9@gated-at.bofh.it> (permalink) |
| References | <rgqim-3Lz-5@gated-at.bofh.it> <rgz2i-1z4-25@gated-at.bofh.it> <rgAB4-2Mv-19@gated-at.bofh.it> <rgBdM-339-13@gated-at.bofh.it> <rgCtb-4bi-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
4.4: INFO: rcu_sched self-detected stall on CPU Steven Haigh <netwiz@crc.id.au> - 2016-03-25 04:10 +0100
Re: [Xen-devel] 4.4: INFO: rcu_sched self-detected stall on CPU Boris Ostrovsky <boris.ostrovsky@oracle.com> - 2016-03-25 13:30 +0100
Re: [Xen-devel] 4.4: INFO: rcu_sched self-detected stall on CPU Steven Haigh <netwiz@crc.id.au> - 2016-03-25 15:10 +0100
Re: [Xen-devel] 4.4: INFO: rcu_sched self-detected stall on CPU Boris Ostrovsky <boris.ostrovsky@oracle.com> - 2016-03-25 15:50 +0100
Re: [Xen-devel] 4.4: INFO: rcu_sched self-detected stall on CPU Steven Haigh <netwiz@crc.id.au> - 2016-03-25 17:10 +0100
Re: [Xen-devel] 4.4: INFO: rcu_sched self-detected stall on CPU Boris Ostrovsky <boris.ostrovsky@oracle.com> - 2016-03-25 17:30 +0100
Re: 4.4: INFO: rcu_sched self-detected stall on CPU Steven Haigh <netwiz@crc.id.au> - 2016-03-25 22:10 +0100
Re: 4.4: INFO: rcu_sched self-detected stall on CPU Steven Haigh <netwiz@crc.id.au> - 2016-03-29 11:00 +0200
Re: 4.4: INFO: rcu_sched self-detected stall on CPU Boris Ostrovsky <boris.ostrovsky@oracle.com> - 2016-03-29 16:20 +0200
Re: 4.4: INFO: rcu_sched self-detected stall on CPU Steven Haigh <netwiz@crc.id.au> - 2016-03-29 19:50 +0200
Re: 4.4: INFO: rcu_sched self-detected stall on CPU Steven Haigh <netwiz@crc.id.au> - 2016-03-29 20:10 +0200
Re: 4.4: INFO: rcu_sched self-detected stall on CPU Boris Ostrovsky <boris.ostrovsky@oracle.com> - 2016-03-30 15:50 +0200
Re: 4.4: INFO: rcu_sched self-detected stall on CPU Steven Haigh <netwiz@crc.id.au> - 2016-04-02 04:00 +0200
csiph-web