Re: [next-20180517][ppc] watchdog: CPU 88 self-detected hard LOCKUP @ update_cfs_group+0x30/0x150

Ah, it's POWER8. I'm betting we have a bug with nohz timer offloading somewhere. I *think* we may have seen similar on P9 as well, but that may be related to problems with stop states. Can you reproduce it easily? I'm thinking maybe adding some tracepoints that track decrementer settings and

Re: [next-20180517][ppc] watchdog: CPU 88 self-detected hard LOCKUP @ update_cfs_group+0x30/0x150

Ah, it's POWER8. I'm betting we have a bug with nohz timer offloading somewhere. I *think* we may have seen similar on P9 as well, but that may be related to problems with stop states. Can you reproduce it easily? I'm thinking maybe adding some tracepoints that track decrementer settings and

[next-20180517][ppc] watchdog: CPU 88 self-detected hard LOCKUP @ update_cfs_group+0x30/0x150

Greeting's Offlate we are seeing hard hard lockup trace messages on our powerpc bare-metal machine for both linux-next and mainline kernel Machine Type: Power 8 Bare-metal (minsky) kernel: 4.17.0-rc5-next-20180517 gcc: 4.8.5 config: attached test: the exact scenario which is triggering these

[next-20180517][ppc] watchdog: CPU 88 self-detected hard LOCKUP @ update_cfs_group+0x30/0x150

Greeting's Offlate we are seeing hard hard lockup trace messages on our powerpc bare-metal machine for both linux-next and mainline kernel Machine Type: Power 8 Bare-metal (minsky) kernel: 4.17.0-rc5-next-20180517 gcc: 4.8.5 config: attached test: the exact scenario which is triggering these