Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-06 Thread Meelis Roos
> On Sun, Mar 05, 2017 at 10:48:50PM +0200, Meelis Roos wrote: > > Added some CC-s because of bisect find. Whole context should be still > > here. > > > > > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked > > > > > > > > fine, > > > > > > > > 4.10.0-09686-g9e314890292c

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-06 Thread Meelis Roos
> On Sun, Mar 05, 2017 at 10:48:50PM +0200, Meelis Roos wrote: > > Added some CC-s because of bisect find. Whole context should be still > > here. > > > > > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked > > > > > > > > fine, > > > > > > > > 4.10.0-09686-g9e314890292c

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-05 Thread Frederic Weisbecker
On Sun, Mar 05, 2017 at 10:48:50PM +0200, Meelis Roos wrote: > Added some CC-s because of bisect find. Whole context should be still > here. > > > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked > > > > > > > fine, > > > > > > > 4.10.0-09686-g9e314890292c and

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-05 Thread Frederic Weisbecker
On Sun, Mar 05, 2017 at 10:48:50PM +0200, Meelis Roos wrote: > Added some CC-s because of bisect find. Whole context should be still > here. > > > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked > > > > > > > fine, > > > > > > > 4.10.0-09686-g9e314890292c and

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-05 Thread Meelis Roos
Added some CC-s because of bisect find. Whole context should be still here. > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > > > > > problem. Ocassionally NMI watchdog kicks in

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-05 Thread Meelis Roos
Added some CC-s because of bisect find. Whole context should be still here. > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > > > > > problem. Ocassionally NMI watchdog kicks in

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-03 Thread Thomas Gleixner
On Thu, 2 Mar 2017, Thomas Gleixner wrote: > On Wed, 1 Mar 2017, Thomas Gleixner wrote: > > On Thu, 2 Mar 2017, Meelis Roos wrote: > > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > >

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-03 Thread Thomas Gleixner
On Thu, 2 Mar 2017, Thomas Gleixner wrote: > On Wed, 1 Mar 2017, Thomas Gleixner wrote: > > On Thu, 2 Mar 2017, Meelis Roos wrote: > > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > >

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-03 Thread Meelis Roos
> On Thu, 2 Mar 2017, Thomas Gleixner wrote: > > On Wed, 1 Mar 2017, Thomas Gleixner wrote: > > > On Thu, 2 Mar 2017, Meelis Roos wrote: > > > > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-03 Thread Meelis Roos
> On Thu, 2 Mar 2017, Thomas Gleixner wrote: > > On Wed, 1 Mar 2017, Thomas Gleixner wrote: > > > On Thu, 2 Mar 2017, Meelis Roos wrote: > > > > > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-02 Thread Meelis Roos
> > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > > > > problem. Ocassionally NMI watchdog kicks in and discovers one of the > > > > > CPUs in LOCKUP. The system keeps running fine. The

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-02 Thread Meelis Roos
> > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > > > > problem. Ocassionally NMI watchdog kicks in and discovers one of the > > > > > CPUs in LOCKUP. The system keeps running fine. The

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-02 Thread Thomas Gleixner
On Wed, 1 Mar 2017, Thomas Gleixner wrote: > On Thu, 2 Mar 2017, Meelis Roos wrote: > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > > > problem. Ocassionally NMI watchdog kicks in and

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-02 Thread Thomas Gleixner
On Wed, 1 Mar 2017, Thomas Gleixner wrote: > On Thu, 2 Mar 2017, Meelis Roos wrote: > > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > > > problem. Ocassionally NMI watchdog kicks in and

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-01 Thread Meelis Roos
> > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > problem. Ocassionally NMI watchdog kicks in and discovers one of the > > CPUs in LOCKUP. The system keeps running fine. The first lockup was > >

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-01 Thread Meelis Roos
> > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > problem. Ocassionally NMI watchdog kicks in and discovers one of the > > CPUs in LOCKUP. The system keeps running fine. The first lockup was > >

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-01 Thread Thomas Gleixner
On Thu, 2 Mar 2017, Meelis Roos wrote: > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > > problem. Ocassionally NMI watchdog kicks in and discovers one of the > > > CPUs in LOCKUP. The system

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-01 Thread Thomas Gleixner
On Thu, 2 Mar 2017, Meelis Roos wrote: > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > > problem. Ocassionally NMI watchdog kicks in and discovers one of the > > > CPUs in LOCKUP. The system

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-01 Thread Meelis Roos
> > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > problem. Ocassionally NMI watchdog kicks in and discovers one of the > > CPUs in LOCKUP. The system keeps running fine. The first lockup was > >

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-01 Thread Meelis Roos
> > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > > problem. Ocassionally NMI watchdog kicks in and discovers one of the > > CPUs in LOCKUP. The system keeps running fine. The first lockup was > >

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-01 Thread Thomas Gleixner
On Wed, 1 Mar 2017, Meelis Roos wrote: > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > problem. Ocassionally NMI watchdog kicks in and discovers one of the > CPUs in LOCKUP. The system keeps running

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-01 Thread Thomas Gleixner
On Wed, 1 Mar 2017, Meelis Roos wrote: > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a > problem. Ocassionally NMI watchdog kicks in and discovers one of the > CPUs in LOCKUP. The system keeps running

PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-01 Thread Meelis Roos
This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a problem. Ocassionally NMI watchdog kicks in and discovers one of the CPUs in LOCKUP. The system keeps running fine. The first lockup was different, all the

PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

2017-03-01 Thread Meelis Roos
This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a problem. Ocassionally NMI watchdog kicks in and discovers one of the CPUs in LOCKUP. The system keeps running fine. The first lockup was different, all the