Re: 4.4: INFO: rcu_sched self-detected stall on CPU

2016-05-03 Thread gre...@linuxfoundation.org
On Wed, May 04, 2016 at 01:11:46AM +1000, Steven Haigh wrote: > On 03/05/16 06:54, gre...@linuxfoundation.org wrote: > > On Wed, Mar 30, 2016 at 05:04:28AM +1100, Steven Haigh wrote: > >> Greg, please see below - this is probably more for you... > >> > >> On 03/29/2016 04:56 AM, Steven Haigh wrote:

Re: 4.4: INFO: rcu_sched self-detected stall on CPU

2016-05-03 Thread Steven Haigh
On 03/05/16 06:54, gre...@linuxfoundation.org wrote: > On Wed, Mar 30, 2016 at 05:04:28AM +1100, Steven Haigh wrote: >> Greg, please see below - this is probably more for you... >> >> On 03/29/2016 04:56 AM, Steven Haigh wrote: >>> >>> Interestingly enough, this just happened again - but on a diffe

Re: 4.4: INFO: rcu_sched self-detected stall on CPU

2016-05-02 Thread gre...@linuxfoundation.org
On Wed, Mar 30, 2016 at 05:04:28AM +1100, Steven Haigh wrote: > Greg, please see below - this is probably more for you... > > On 03/29/2016 04:56 AM, Steven Haigh wrote: > > > > Interestingly enough, this just happened again - but on a different > > virtual machine. I'm starting to wonder if this

Re: 4.4: INFO: rcu_sched self-detected stall on CPU

2016-04-01 Thread Steven Haigh
On 30/03/2016 1:14 AM, Boris Ostrovsky wrote: > On 03/29/2016 04:56 AM, Steven Haigh wrote: >> >> Interestingly enough, this just happened again - but on a different >> virtual machine. I'm starting to wonder if this may have something to do >> with the uptime of the machine - as the system that th

Re: 4.4: INFO: rcu_sched self-detected stall on CPU

2016-03-30 Thread Boris Ostrovsky
On 03/29/2016 02:04 PM, Steven Haigh wrote: Greg, please see below - this is probably more for you... On 03/29/2016 04:56 AM, Steven Haigh wrote: Interestingly enough, this just happened again - but on a different virtual machine. I'm starting to wonder if this may have something to do with the

Re: 4.4: INFO: rcu_sched self-detected stall on CPU

2016-03-29 Thread Steven Haigh
Greg, please see below - this is probably more for you... On 03/29/2016 04:56 AM, Steven Haigh wrote: > > Interestingly enough, this just happened again - but on a different > virtual machine. I'm starting to wonder if this may have something to do > with the uptime of the machine - as the system

Re: 4.4: INFO: rcu_sched self-detected stall on CPU

2016-03-29 Thread Steven Haigh
On 30/03/2016 1:14 AM, Boris Ostrovsky wrote: > On 03/29/2016 04:56 AM, Steven Haigh wrote: >> >> Interestingly enough, this just happened again - but on a different >> virtual machine. I'm starting to wonder if this may have something to do >> with the uptime of the machine - as the system that th

Re: 4.4: INFO: rcu_sched self-detected stall on CPU

2016-03-29 Thread Boris Ostrovsky
On 03/29/2016 04:56 AM, Steven Haigh wrote: Interestingly enough, this just happened again - but on a different virtual machine. I'm starting to wonder if this may have something to do with the uptime of the machine - as the system that this seems to happen to is always different. Destroying it

Re: 4.4: INFO: rcu_sched self-detected stall on CPU

2016-03-29 Thread Steven Haigh
On 26/03/2016 8:07 AM, Steven Haigh wrote: > 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 >>> possib

Re: 4.4: INFO: rcu_sched self-detected stall on CPU

2016-03-25 Thread Steven Haigh
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 get