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 a

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 4.10.0-1077

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 and

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 exhi

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 di

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 > > di

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
ting full-duplex based on MII#1 link partner capability of 45e1 [1.280014] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [1.280110] NFSD: starting 90-second grace period (net c158b340) [1.295055] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0 [1.

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 fi

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

2017-03-01 Thread Meelis Roos
t-ro [1.634004] loop: module loaded [1.639004] perf: interrupt took too long (2537 > 2500), lowering kernel.perf_event_max_sample_rate to 78800 [1.639004] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0 [1.639004] Modules linked in: msr cpuid loop evdev snd_cmipci snd_mpu401_uart snd_opl3_lib snd_hwdep s

Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0

2015-10-09 Thread Rafael J. Wysocki
On 10/10/2015 12:52 AM, Al Stone wrote: On 10/09/2015 03:02 PM, Rafael J. Wysocki wrote: On Thursday, October 08, 2015 05:05:00 PM Al Stone wrote: On 10/08/2015 04:50 PM, Rafael J. Wysocki wrote: On Thursday, October 08, 2015 02:32:15 PM Al Stone wrote: On 10/08/2015 02:41 PM, Rafael J. Wysoc

Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0

2015-10-09 Thread Al Stone
On 10/09/2015 03:02 PM, Rafael J. Wysocki wrote: > On Thursday, October 08, 2015 05:05:00 PM Al Stone wrote: >> On 10/08/2015 04:50 PM, Rafael J. Wysocki wrote: >>> On Thursday, October 08, 2015 02:32:15 PM Al Stone wrote: On 10/08/2015 02:41 PM, Rafael J. Wysocki wrote: > On Thursday, Oct

Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0

2015-10-09 Thread Rafael J. Wysocki
On Thursday, October 08, 2015 05:05:00 PM Al Stone wrote: > On 10/08/2015 04:50 PM, Rafael J. Wysocki wrote: > > On Thursday, October 08, 2015 02:32:15 PM Al Stone wrote: > >> On 10/08/2015 02:41 PM, Rafael J. Wysocki wrote: > >>> On Thursday, October 08, 2015 10:37:55 PM Rafael J. Wysocki wrote: >

Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0

2015-10-08 Thread Al Stone
On 10/08/2015 04:50 PM, Rafael J. Wysocki wrote: > On Thursday, October 08, 2015 02:32:15 PM Al Stone wrote: >> On 10/08/2015 02:41 PM, Rafael J. Wysocki wrote: >>> On Thursday, October 08, 2015 10:37:55 PM Rafael J. Wysocki wrote: On Thursday, October 08, 2015 10:36:40 AM Al Stone wrote:

Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0

2015-10-08 Thread Rafael J. Wysocki
On Thursday, October 08, 2015 02:32:15 PM Al Stone wrote: > On 10/08/2015 02:41 PM, Rafael J. Wysocki wrote: > > On Thursday, October 08, 2015 10:37:55 PM Rafael J. Wysocki wrote: > >> On Thursday, October 08, 2015 10:36:40 AM Al Stone wrote: > >>> On 10/08/2015 05:44 AM, Hanjun Guo wrote: > O

Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0

2015-10-08 Thread Al Stone
On 10/08/2015 02:41 PM, Rafael J. Wysocki wrote: > On Thursday, October 08, 2015 10:37:55 PM Rafael J. Wysocki wrote: >> On Thursday, October 08, 2015 10:36:40 AM Al Stone wrote: >>> On 10/08/2015 05:44 AM, Hanjun Guo wrote: On 10/08/2015 11:21 AM, kernel test robot wrote: > FYI, we notice

Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0

2015-10-08 Thread Rafael J. Wysocki
On Thursday, October 08, 2015 10:37:55 PM Rafael J. Wysocki wrote: > On Thursday, October 08, 2015 10:36:40 AM Al Stone wrote: > > On 10/08/2015 05:44 AM, Hanjun Guo wrote: > > > On 10/08/2015 11:21 AM, kernel test robot wrote: > > >> FYI, we noticed the below changes on > > >> > > >> https://git.k

Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0

2015-10-08 Thread Rafael J. Wysocki
On Thursday, October 08, 2015 10:36:40 AM Al Stone wrote: > On 10/08/2015 05:44 AM, Hanjun Guo wrote: > > On 10/08/2015 11:21 AM, kernel test robot wrote: > >> FYI, we noticed the below changes on > >> > >> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > >> commit 7494b

Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0

2015-10-08 Thread Al Stone
On 10/08/2015 05:44 AM, Hanjun Guo wrote: > On 10/08/2015 11:21 AM, kernel test robot wrote: >> FYI, we noticed the below changes on >> >> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master >> commit 7494b07ebaae2117629024369365f7be7adc16c3 ("ACPI: add in a >> bad_madt_entry

Re: [lkp] [ACPI] 7494b07eba: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0

2015-10-08 Thread Hanjun Guo
On 10/08/2015 11:21 AM, kernel test robot wrote: FYI, we noticed the below changes on https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit 7494b07ebaae2117629024369365f7be7adc16c3 ("ACPI: add in a bad_madt_entry() function to eventually replace the macro") [0.0

Re: Watchdog detected hard LOCKUP on cpu 0 on FITPC2

2014-01-12 Thread Juha Luoma
Stefan Beller wrote: I noticed a machine to hang after a few days of uptime, i.e. the USB, networking etc are all gone, but the machine is still up and displaying the login screen. I am running $ uname -a Linux sd 3.12.5-302.fc20.i686 #1 SMP Tue Dec 17 21:01:18 UTC 2013 i686 i686 i386 G

Watchdog detected hard LOCKUP on cpu 0 on FITPC2

2013-12-28 Thread Stefan Beller
I got these messages: [108655.024413] [ cut here ] [108655.024413] WARNING: CPU: 0 PID: 0 at kernel/watchdog.c:272 watchdog_overflow_callback+0xac/0xd0() [108655.024413] Watchdog detected hard LOCKUP on cpu 0 [108655.024413] Modules linked in: [108655.024413] fuse

Watchdog detected hard LOCKUP on cpu

2013-08-13 Thread Martin Stoilov
quadpc kernel: [263676.682565] WARNING: at /build/buildd/linux-3.5.0/kernel/watchdog.c:242 watchdog_overflow_callback+0x9a/0xc0() Aug 13 15:42:12 quadpc kernel: [263676.682566] Hardware name: System Product Name Aug 13 15:42:12 quadpc kernel: [263676.682567] Watchdog detected hard LOCKUP on cpu 2