Bug 59631 - BUG: scheduling while atomic: swapper/3/0/0x00010002
Summary: BUG: scheduling while atomic: swapper/3/0/0x00010002
Status: RESOLVED INVALID
Alias: None
Product: Process Management
Classification: Unclassified
Component: Scheduler (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Thomas Gleixner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-12 00:19 UTC by Arie Setiawan
Modified: 2013-07-30 19:30 UTC (History)
4 users (show)

See Also:
Kernel Version: linux 3.8.13-rt10-1-rt
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Arie Setiawan 2013-06-12 00:19:35 UTC 
i get this in dmesg log.

[    7.369355] BUG: scheduling while atomic: swapper/3/0/0x00010002
[    7.369368] Modules linked in: vboxdrv(O+) ext4 crc16 mbcache jbd2 hid_generic usbhid hid sr_mod sd_mod cdrom ahci libahci ehci_pci libata sdhci_pci xhci_hcd ehci_hcd sdhci scsi_mod mmc_core usbcore usb_common i915 video button i2c_algo_bit intel_agp intel_gtt drm_kms_helper drm i2c_core
[    7.369370] Pid: 0, comm: swapper/3 Tainted: G           O 3.8.13-rt10-1-rt #1
[    7.369371] Call Trace:
[    7.369379]  <IRQ>  [<ffffffff814b927f>] __schedule_bug+0x4d/0x59
[    7.369381]  [<ffffffff814bf3ed>] __schedule+0x97d/0x990
[    7.369384]  [<ffffffff8109477c>] ? update_curr+0xcc/0x1e0
[    7.369387]  [<ffffffff810b40e4>] ? task_blocks_on_rt_mutex+0xf4/0x260
[    7.369388]  [<ffffffff814bf429>] schedule+0x29/0x70
[    7.369390]  [<ffffffff814c0051>] rt_spin_lock_slowlock+0x177/0x2a6
[    7.369393]  [<ffffffff8108b401>] ? check_preempt_curr+0x21/0xa0
[    7.369405]  [<ffffffffa032ce30>] ? VBoxHost_RTMpIsCpuWorkPending+0x10/0x10 [vboxdrv]
[    7.369407]  [<ffffffff814c06b5>] rt_spin_lock+0x25/0x30
[    7.369418]  [<ffffffffa032e9d6>] VBoxHost_RTSpinlockAcquire+0x36/0x50 [vboxdrv]
[    7.369430]  [<ffffffffa031fa66>] supdrvGipMpEventOnline+0x66/0x220 [vboxdrv]
[    7.369440]  [<ffffffffa032ce30>] ? VBoxHost_RTMpIsCpuWorkPending+0x10/0x10 [vboxdrv]
[    7.369449]  [<ffffffffa031fc35>] supdrvGipInitOnCpu+0x15/0x20 [vboxdrv]
[    7.369458]  [<ffffffffa032ce58>] rtmpLinuxWrapper+0x28/0x30 [vboxdrv]
[    7.369460]  [<ffffffff810b5651>] generic_smp_call_function_interrupt+0xa1/0x1d0
[    7.369463]  [<ffffffff81386100>] ? show_available_freqs+0xa0/0xa0
[    7.369466]  [<ffffffff810393f7>] smp_call_function_interrupt+0x27/0x40
[    7.369468]  [<ffffffff814c949d>] call_function_interrupt+0x6d/0x80
[    7.369471]  <EOI>  [<ffffffff81386d11>] ? cpuidle_wrap_enter+0x41/0x80
[    7.369473]  [<ffffffff81386130>] cpuidle_enter_tk+0x10/0x20
[    7.369474]  [<ffffffff813868d3>] cpuidle_idle_call+0xb3/0x3d0
[    7.369476]  [<ffffffff8101f0af>] cpu_idle+0x10f/0x160
[    7.369478]  [<ffffffff814afa5c>] start_secondary+0x25a/0x25c

why i get this ?
Comment 1 John Kacur 2013-07-22 12:52:45 UTC 
what is vboxdrv?
Comment 2 John Kacur 2013-07-26 10:21:05 UTC 
What is vboxdrv? - this is not in the standard kernel. If this isn't an GPL module, we won't be able to help you.
Comment 3 Dolan Murvihill 2013-07-28 23:21:13 UTC 
vboxdrv is the VirtualBox Linux Kernel Driver. This is a VirtualBox issue - somewhere, it sleeps while inside a critical region, which is a no-no. See https://www.virtualbox.org/ticket/9748
Comment 4 Darren Hart 2013-07-30 19:30:21 UTC 
I think with that we can close this as INVALID. Only VirtualBox can fix this and there appears to be a ticket open on their end.
Note You need to log in before you can comment on or make changes to this bug.