BUG: scheduling while atomic: VirtualBox/0x00000001/5767, CPU#1

Same here, VirtualBox 3.0.10 / PUEL

I have the same problem with VB 3.0.8 on Kubuntu Karmic AMD64, kernel 2.6.31-9-rt.

VirtualBox started freezing for a few seconds intermittently after upgrading to Karmic. The host remained responsive during these freezes. I am using the realtime kernel per some tips given in this forum thread: http://forums.virtualbox.org/viewtopic.php?f=7&t=23978

(And thanks for those tips, qhartman, VB isn't freezing anymore. ;) )

What cpu are you using?

I have two machines with different cpus. Both Ubuntu 9.10 and VirtualBox 3.0.10. VirtualBox appears to work fine with the AMD cpu. On the Intel Xeon E5410, which still uses the "amd64" kernel, I have the exact problem reported here. I received three crash reports for the one virtual machine failure.

BUG: scheduling while atomic: VirtualBox/0x00000001/4183, CPU#1
BUG: scheduling while atomic: VirtualBox/0x00000001/4183, CPU#2
BUG: scheduling while atomic: VirtualBox/0x00000001/4183, CPU#3

The tips in the above forum post only partially worked for me. I am unable to install a new 64 bit guest.
A 32 bit guest install appears to have worked.

This may also be related to:
VBox 3.0.10 Ubuntu 9.10 64 Host Win 7 64 Guest Very Slow!
http://forums.virtualbox.org/viewtopic.php?f=7&t=23978&start=0

I'm using a Core 2 Duo in a Macbook Pro (version 5,4, late 2009 unibody). I'll try installing a 64-bit guest and see if it fails for me too.

I'm on this: AMD Turion(tm) 64 X2 Mobile Technology TL-52, 2.6.31-9-rt x86_64
I keep on getting kernel ooopses,
existing 32bit guests run OK, attempting a clean Windows 7 install hangs on "expanding files".
Most of the time, killing all VBox related processes & stop/starting vboxdrv allows VBox to run. On occasion, a reboot is definitely required.

Ok, installed an Ubuntu 64 guest w/o incident. First reboot of the
guest reported some FS inconsistency which seems odd. It was fixed
with a normal fsck and the guest has been running fine since. It seems
that your problems are not inherently 64-bit related, perhaps only
64-bit Windows.

aside: the kernel modules for 3.0.10 aren't loading themselves anymore
for some reason. I have to manually modprobe them, or I've added them
to my /etc/modules to get them to load. Odd. Never seen that before.

I am running my VirtualBox 3.0.10 (PUEL) on my Core 2 Duo in my MacBook2,1.

Running the guest 32-bit Windows 7 that I installed after upgrading to 64-bit Karmic produces these kernel errors. A 32-bit Windows XP guest that I had since 64-bit Hardy does not produce these errors.

I am running Ubuntu 9.10 64bit with the rt kernel to speed up my VM and my WIndows XP host will crash and this is displayed in my syslog

BUG: scheduling while atomic: VirtualBox/0x00000001/3065, CPU#1

A workaround for this is to disable the second CPU in VirtualBox

Exactly the information that I'm looking for!

I'll work on fix this weekend: I hope to have a package to test on Monday.

Thanks!

thanks!!

I was getting this error with only one Virtual CPU selected. I think the CPU# in the crash report refers to the core number in the host.

I have moved back to Ubuntu 9.04 with VirtualBox 3.0.10 and everything is working well.

By the way, the importance of this is listed as "low". I suggest it is higher importance as it appears to be affecting a lot of people and it prevents using VirtualBox on Ubuntu 9.10 in any productive environment.

This appears to be fixed. I am now using Ubuntu 9.10 with vmlinuz-2.6.31-16-generic kernel. Virtualbox 3.0.12 was working acceptably well, and VirtualBox 3.1.0 appears to be working better than ever.

Hi,

This bug was reported a while ago and there hasn't been any activity
in it recently. We were wondering if this is still an issue? Can you
try with the latest development release of Ubuntu (Lucid Lynx)? ISO CD
images are available from http://cdimage.ubuntu.com/releases/

Thanks!

I'm experiencing this bug with 2.6.33-29-realtime kernel on a single-core AMD Opteron 148 (no VirtualBox).
I'm using NVIDIA-Linux-x86_64-260.19.21 driver patched manually by these instructions: http://ubuntuforums.org/showpost.php?p=9233282&postcount=5

[21101.020190] BUG: scheduling while atomic: sirq-tasklet/0/0x00000001/10, CPU#0
[21101.020193] Modules linked in: binfmt_misc snd_emu10k1_synth snd_emux_synth drm snd_seq_virmidi snd_seq_midi_emul usbserial snd_emu10k1 dme1737 hwmon_vid snd_util_mem raw1394 snd_intel8x0 snd_ac97_codec snd_usb_audio ac97_bus snd_usb_lib snd_pcm_oss tuner snd_hwdep snd_mixer_oss snd_seq_dummy snd_pcm bttv snd_seq_oss snd_seq_midi v4l2_common snd_rawmidi ir_common i2c_algo_bit videobuf_dma_sg videobuf_core btcx_risc tveeprom ir_core snd_seq_midi_event gspca_zc3xx sbp2 snd_seq gspca_main xfs videodev amd64_edac_mod psmouse snd_timer emu10k1_gp exportfs lp v4l1_compat snd_seq_device edac_core ppdev v4l2_compat_ioctl32 serio_raw gameport nvidia(P) snd edac_mce_amd i2c_nforce2 k8temp soundcore snd_page_alloc parport_pc parport usbhid hid ohci1394 ieee1394 forcedeth sata_nv pata_amd
[21101.020237] Pid: 10, comm: sirq-tasklet/0 Tainted: P 2.6.33-29-realtime #1-Ubuntu
[21101.020240] Call Trace:
[21101.020249] [<ffffffff8104eaef>] __schedule_bug+0x6f/0x80
[21101.020254] [<ffffffff8154f48b>] __schedule+0x6cb/0x800
[21101.020260] [<ffffffff81096805>] ? task_blocks_on_rt_mutex+0x1a5/0x240
[21101.020263] [<ffffffff8154f73c>] schedule+0x2c/0x50
[21101.020266] [<ffffffff81550a56>] rt_spin_lock_slowlock+0x216/0x2f0
[21101.020270] [<ffffffff8155152b>] rt_spin_lock+0x3b/0x70
[21101.020273] [<ffffffff8104c1b1>] __wake_up+0x31/0x70
[21101.020722] [<ffffffffa05f7b90>] nv_post_event+0x100/0x1b0 [nvidia]
[21101.020938] [<ffffffffa05d0f54>] _nv021903rm+0xec/0x136 [nvidia]
[21101.021008] [<ffffffffa03327d8>] ? _nv010397rm+0xc0/0xe9 [nvidia]
[21101.021008] [<ffffffffa02edcda>] ? _nv009051rm+0xd4/0xfd [nvidia]
[21101.021008] [<ffffffffa02edca7>] ? _nv009051rm+0xa1/0xfd [nvidia]
[21101.021008] [<ffffffffa02f2702>] ? _nv009471rm+0xce/0x1f8 [nvidia]
[21101.021008] [<ffffffffa04aa26c>] ? _nv019001rm+0x325/0x826 [nvidia]
[21101.021008] [<ffffffffa04a1062>] ? _nv018982rm+0xc2/0x107 [nvidia]
[21101.021008] [<ffffffffa05d575d>] ? _nv002165rm+0x7d/0xae [nvidia]
[21101.021008] [<ffffffffa05db235>] ? rm_isr_bh+0x5a/0x8d [nvidia]
[21101.021008] [<ffffffffa05f63c3>] ? nv_kern_isr_bh+0x43/0x70 [nvidia]
[21101.021008] [<ffffffff81066f65>] ? __tasklet_action+0x75/0x130
[21101.021008] [<ffffffff810670ba>] ? tasklet_action+0x4a/0x50
[21101.021008] [<ffffffff8106816b>] ? run_ksoftirqd+0x1bb/0x350
[21101.021008] [<ffffffff81067fb0>] ? run_ksoftirqd+0x0/0x350
[21101.021008] [<ffffffff81067fb0>] ? run_ksoftirqd+0x0/0x350
[21101.021008] [<ffffffff81081cf6>] ? kthread+0x96/0xa0
[21101.021008] [<ffffffff8100c024>] ? kernel_thread_helper+0x4/0x10
[21101.021008] [<ffffffff81081c60>] ? kthread+0x0/0xa0
[21101.021008] [<ffffffff8100c020>] ? kernel_thread_helper+0x0/0x10