> 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
> 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
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
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
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
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
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
> >
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
> >
> 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
> 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
> > > > > 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
> > > > > 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
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
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
> > 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
> >
> > 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
> >
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
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
> > 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
> >
> > 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
> >
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
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
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
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
24 matches
Mail list logo