Hello Vignesh- I never explicitly asked...have you tried a similar test on a non-RT kernel? Does it exhibit the same behavior? The linked moby github issue would seem to indicate this isn't RT specific... On Wed, Aug 22, 2018 at 01:38:49PM +0530, Vignesh Raman wrote: > Hi Julia, > > On Tuesday 21 August 2018 07:12 PM, Julia Cartwright wrote: > > That's annoying. When you are in this state can you trigger a dump via > > the magic sysrq sequence over serial? > > No. I'm not able to trigger a crash using sysrq (Alt+SysRq+c). Keyboard > 'caps lock' led light does not respond when caps lock key is pressed. > > Does it indicate a softlockup or hardlockup ? Not sure the distinction matters. You're locked up tight. > > Have you tried enabling the various lockup detectors? There is a > > software-driven one, and an NMI watchdog based one. Enabling both > > at the same time should be fine. > > The below config options are enabled, > CONFIG_HAVE_HARDLOCKUP_DETECTOR_PERF=y > # Debug Lockups and Hangs > CONFIG_LOCKUP_DETECTOR=y > CONFIG_SOFTLOCKUP_DETECTOR=y > CONFIG_HARDLOCKUP_DETECTOR_PERF=y > CONFIG_HARDLOCKUP_CHECK_TIMESTAMP=y > CONFIG_HARDLOCKUP_DETECTOR=y > # CONFIG_BOOTPARAM_HARDLOCKUP_PANIC is not set > CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=0 > # CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set > CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0 > CONFIG_HAVE_NMI=y > CONFIG_HAVE_PERF_EVENTS_NMI=y Can you send your full config? If I get some time to try it, I'd like to see if I can reproduce your issue. Julia
