Re: [LKP] [lkp] [spi] 2baed30cb3: BUG: scheduling while atomic: systemd-udevd/134/0x00000002

From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Sudip Mukherjee <sudip@vectorindia.org>,
	Mark Brown <broonie@kernel.org>,
	lkp@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [lkp] [spi] 2baed30cb3: BUG: scheduling while atomic: systemd-udevd/134/0x00000002
Date: Thu, 21 Jan 2016 11:03:10 +0530	[thread overview]
Message-ID: <20160121053310.GA4782@sudip-pc> (raw)
In-Reply-To: <87a8o0yhdz.fsf@yhuang-dev.intel.com>

On Wed, Jan 20, 2016 at 01:00:40PM +0800, Huang, Ying wrote:
> Sudip Mukherjee <sudipm.mukherjee@gmail.com> writes:
> 
> > On Wed, Jan 20, 2016 at 08:44:37AM +0800, kernel test robot wrote:
> >> FYI, we noticed the below changes on
> >> 
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> >> commit 2baed30cb30727b2637d26eac5a8887875a13420 ("spi: lm70llp: use new parport device model")
> >> 
> >> 
> >> +----------------+------------+------------+
> >> |                | 74bdced4b4 | 2baed30cb3 |
> >> +----------------+------------+------------+
> >> | boot_successes | 0          | 0          |
> >> +----------------+------------+------------+
> >> 
> >> 
> >> 
> >> [    6.358390] i6300esb: Intel 6300ESB WatchDog Timer Driver v0.05
> >> [    6.358540] i6300esb: cannot register miscdev on minor=130 (err=-16)
> >> [    6.358555] i6300ESB timer: probe of 0000:00:06.0 failed with error -16
> >> [    6.363357] BUG: scheduling while atomic: systemd-udevd/134/0x00000002
> >> [ 6.363366] Modules linked in: crc32c_intel pcspkr evdev i6300esb
> >> ide_cd_mod cdrom intel_agp intel_gtt i2c_piix4 i2c_core virtio_pci
> >> virtio virtio_ring agpgart rtc_cmos(+) parport_pc(+) autofs4
> >> [    6.363369] CPU: 1 PID: 134 Comm: systemd-udevd Not tainted 4.4.0-rc1-00006-g2baed30 #1
> >> [    6.363370] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Debian-1.8.2-1 04/01/2014
> >
> > Can you please let me know how do i reproduce this on qemu? what command
> > line you used?
> 
> The command line can be found in the last line of dmesg file, as below.
> 
> qemu-system-x86_64 -enable-kvm -cpu host -kernel /pkg/linux/x86_64-randconfig-a0-01191454/gcc-5/2baed30cb30727b2637d26eac5a8887875a13420/vmlinuz-4.4.0-rc1-00006-g2baed30 -append 'root=/dev/ram0 user=lkp job=/lkp/scheduled/vm-lkp-wsx03-2G-2/bisect_boot-1-debian-x86_64-2015-02-07.cgz-x86_64-randconfig-a0-01191454-2baed30cb30727b2637d26eac5a8887875a13420-20160119-71002-198dtgm-0.yaml ARCH=x86_64 kconfig=x86_64-randconfig-a0-01191454 branch=linux-devel/devel-spot-201601191442 commit=2baed30cb30727b2637d26eac5a8887875a13420 BOOT_IMAGE=/pkg/linux/x86_64-randconfig-a0-01191454/gcc-5/2baed30cb30727b2637d26eac5a8887875a13420/vmlinuz-4.4.0-rc1-00006-g2baed30 max_uptime=600 RESULT_ROOT=/result/boot/1/vm-lkp-wsx03-2G/debian-x86_64-2015-02-07.cgz/x86_64-randconfig-a0-01191454/gcc-5/2baed30cb30727b2637d26eac5a8887875a13420/0 LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0 console=ttyS0,115200 console=tty0 vga=normal rw ip=::::vm-lkp-wsx03-2G-2::dhcp'  -initrd /fs/sda1/initrd-vm-lkp-wsx03-2G-2 -m 2048 -smp 2 -device e1000,netdev=net0 -netdev user,id=net0,hostfwd=tcp::23621-:22 -boot order=nc -no-reboot -watchdog i6300esb -rtc base=localtime -drive file=/fs/sda1/disk0-vm-lkp-wsx03-2G-2,media=disk,if=virtio -drive file=/fs/sda1/disk1-vm-lkp-wsx03-2G-2,media=disk,if=virtio -pidfile /dev/shm/kboot/pid-vm-lkp-wsx03-2G-2 -serial file:/dev/shm/kboot/serial-vm-lkp-wsx03-2G-2 -daemonize -display none -monitor null

I am not able to reproduce this. Tested just with the kernel and
yocto-minimal-i386.cgz filesystem and it booted properly.

I guess I need atleast your job file to reproduce this.

regards
sudip