5.0RC2 on Linux generates many scheduling while atomic bugs

[lwfinger]

On an openSUSE 13.2 host, 5.0_RC2 host, all VMs generate many of the following bug reports:

Code: Select all

[85922.774454] BUG: scheduling while atomic: EMT-0/18880/0x00000003
[85922.774469] INFO: lockdep is turned off.
[85922.774474] Modules linked in: vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) mmc_block rfcomm cmac ecb btusb(O) fuse bnep bluetooth drbg ansi_cprng ctr ccm af_packet nfs fscache x86_pkg_temp_thermal kvm_intel kvm iwlmvm snd_hda_codec_generic arc4 snd_hda_intel rtl8821ae snd_hda_codec btcoexist crct10dif_pclmul rtl_pci snd_hwdep crc32_pclmul rtlwifi mac80211 crc32c_intel ghash_clmulni_intel snd_hda_core iwlwifi aesni_intel aes_x86_64 snd_pcm cfg80211 lrw snd_timer rtsx_pci_sdmmc mmc_core gf128mul rtsx_pci_ms memstick e1000e snd glue_helper rtsx_pci toshiba_acpi ablk_helper sparse_keymap cryptd xhci_pci xhci_hcd ptp soundcore acpi_cpufreq lpc_ich mfd_core pps_core microcode toshiba_bluetooth rfkill processor pcspkr battery serio_raw thermal ac wmi dm_mod i915 i2c_algo_bit drm_kms_helper drm sr_mod
[85922.774706]  cdrom video thermal_sys hwmon button sg autofs4 [last unloaded: btusb]
[85922.774736] CPU: 0 PID: 18880 Comm: EMT-0 Tainted: G        W  O    4.2.0-wd-next-wl+ #72
[85922.774742] Hardware name: TOSHIBA TECRA A50-A/TECRA A50-A, BIOS Version 4.20   04/17/2014
[85922.774749]  0000000000015ec0 ffff880211ff3c28 ffffffff81739f8f 0000000000000000
[85922.774763]  ffff8801fdb4a6c0 ffff880211ff3c48 ffffffff8173305f 0000000000000000
[85922.774776]  ffff88022f215ec0 ffff880211ff3ca8 ffffffff8173d230 0000000000000000
[85922.774790] Call Trace:
[85922.774805]  [<ffffffff81739f8f>] dump_stack+0x4c/0x6e
[85922.774816]  [<ffffffff8173305f>] __schedule_bug+0x60/0x70
[85922.774827]  [<ffffffff8173d230>] __schedule+0xcf0/0xe30
[85922.774837]  [<ffffffff8173d3ae>] schedule+0x3e/0x90
[85922.774847]  [<ffffffff8173d725>] schedule_preempt_disabled+0x15/0x20
[85922.774857]  [<ffffffff8173f6fb>] mutex_lock_nested+0x15b/0x3c0
[85922.774870]  [<ffffffff81180d9c>] ? static_key_slow_inc+0x7c/0xc0
[85922.774880]  [<ffffffff81180d9c>] static_key_slow_inc+0x7c/0xc0
[85922.774892]  [<ffffffff8108fb2d>] preempt_notifier_register+0x1d/0x60
[85922.774930]  [<ffffffffa08ec66f>] VBoxHost_RTThreadCtxHookEnable+0x2f/0x50 [vboxdrv]
[85922.774992]  [<ffffffffa08d95f1>] ? supdrvIOCtlFast+0x71/0x90 [vboxdrv]
[85922.775007]  [<ffffffffa08d640c>] ? VBoxDrvLinuxIOCtl_5_0_0+0x4c/0x270 [vboxdrv]
[85922.775021]  [<ffffffff810e210e>] ? rcu_irq_exit+0x4e/0x60
[85922.775027]  [<ffffffff817442fe>] ? retint_kernel+0x2d/0x2d
[85922.775034]  [<ffffffff810bc8bd>] ? trace_hardirqs_on+0xd/0x10
[85922.775043]  [<ffffffff812136fd>] ? do_vfs_ioctl+0x30d/0x580
[85922.775051]  [<ffffffff8121f1a3>] ? __fget_light+0x33/0x90
[85922.775058]  [<ffffffff812139e9>] ? SyS_ioctl+0x79/0x90
[85922.775066]  [<ffffffff81743757>] ? entry_SYSCALL_64_fastpath+0x12/0x6f

[frank]

Is this the normal openSUSE 13.2 kernel or did you compile the kernel yourself?

[frank]

Also, is a VBox.log file available and how easy to reproduce is this problem for you?

[Ramshankar]

Please also attach output of:

Code: Select all

cat /boot/config-`uname -r`

in addition to VBox.log that Frank mentioned.

[frank]

Fixed in VBox 5.0.2.