On Tue, 2018-03-13 at 16:59 +0200, Jaco Kroon wrote: > I quickly checked my dmesg logs and I'm not seeing that particular > message, could be that newer kernels only started warning about it?
Hello Jaco, That message only appears if CONFIG_DEBUG_ATOMIC_SLEEP (sleep inside atomic) is enabled in the kernel config. The kernel configuration options I enable to test kernel code can be found below. Please note that some of these options slow down the kernel significantly, so these options should probably not be enabled on a production system. CONFIG_BLK_DEBUG_FS CONFIG_DEBUG_ATOMIC_SLEEP CONFIG_DEBUG_BOOT_PARAMS CONFIG_DEBUG_BUGVERBOSE CONFIG_DEBUG_FS CONFIG_DEBUG_INFO CONFIG_DEBUG_INFO_DWARF4 CONFIG_DEBUG_INFO_REDUCED CONFIG_DEBUG_KERNEL CONFIG_DEBUG_KMEMLEAK CONFIG_DEBUG_LIST CONFIG_DEBUG_LOCK_ALLOC CONFIG_DEBUG_MUTEXES CONFIG_DEBUG_OBJECTS CONFIG_DEBUG_OBJECTS_RCU_HEAD CONFIG_DEBUG_PAGEALLOC CONFIG_DEBUG_PER_CPU_MAPS CONFIG_DEBUG_PI_LIST CONFIG_DEBUG_PREEMPT CONFIG_DEBUG_PREEMPT_VOLUNTARY CONFIG_DEBUG_SG CONFIG_DEBUG_SPINLOCK CONFIG_DEBUG_STACKOVERFLOW CONFIG_DEBUG_STACK_USAGE CONFIG_DETECT_HUNG_TASK CONFIG_DYNAMIC_DEBUG CONFIG_HARDLOCKUP_DETECTOR CONFIG_KASAN CONFIG_MAGIC_SYSRQ CONFIG_PREEMPT CONFIG_PROVE_LOCKING CONFIG_PROVE_RCU CONFIG_SCHED_DEBUG CONFIG_SLUB CONFIG_SLUB_DEBUG_ON CONFIG_WQ_WATCHDOG Bart.
