Greeting, FYI, we noticed the following commit (built with gcc-9): commit: a315354f66cc3285810ec2562756eb584bab902c ("net/scm: Regularize compat handling of scm_detach_fds()") https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git for-next/seccomp in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace): +-------------------------------+------------+------------+ | | 59a4c5d523 | a315354f66 | +-------------------------------+------------+------------+ | boot_successes | 5 | 3 | | boot_failures | 0 | 3 | | BUG:kernel_hang_in_test_stage | 0 | 3 | +-------------------------------+------------+------------+ If you fix the issue, kindly add following tag Reported-by: kernel test robot [ 2104.179326] systemd-journald[1641]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 2204.179442] systemd-journald[1641]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 2284.179253] systemd-journald[1641]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 2384.179456] systemd-journald[1641]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 2464.179370] systemd-journald[1641]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected BUG: kernel hang in test stage Elapsed time: 2520 qemu-img create -f qcow2 disk-vm-snb-ssd-59-0 256G qemu-img create -f qcow2 disk-vm-snb-ssd-59-1 256G To reproduce: # build kernel cd linux cp config-5.8.0-rc1-00024-ga315354f66cc3 .config make HOSTCC=gcc-9 CC=gcc-9 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage git clone https://github.com/intel/lkp-tests.git cd lkp-tests bin/lkp qemu -k job-script # job-script is attached in this email Thanks, lkp