VirtualBox

Ticket #4891 (closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

Host Kernel: Scheduling while atomic errors (opensuse 11.1)

Reported by: mkromer Owned by:
Priority: major Component: host support
Version: VirtualBox 3.0.4 Keywords:
Cc: Guest type: other
Host type: Linux

Description

This here is a rather interesting bug I hav no idea what problems arise through this. Geusts stay up, and the machines are still running without visible problems. All machines use a bridging with a tap-device, so they are not using vboxnetX.

The host is running 4 VBoxHeadless Machines (opensolaris, win2k3, opensuse 11.1, debian 5.02a), and it happens occassionaly:

Aug 31 19:18:36 borg kernel: BUG: scheduling while atomic: VirtualBox/0x00000001/6489, CPU#1 Aug 31 19:30:20 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/6917, CPU#4 Aug 31 19:51:24 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/6977, CPU#4 Aug 31 19:51:24 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/6977, CPU#5 Aug 31 19:51:24 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/6977, CPU#5 Aug 31 20:05:56 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/6977, CPU#4 Aug 31 20:05:56 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/6977, CPU#4 Aug 31 22:30:14 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/7991, CPU#1 Aug 31 22:30:14 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/7991, CPU#1 Sep 1 04:06:04 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/7991, CPU#4 Sep 1 06:21:30 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/7991, CPU#2 Sep 1 06:29:58 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/7991, CPU#6 Sep 1 09:32:02 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/7991, CPU#4 Sep 1 09:32:02 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/7991, CPU#4 Sep 1 16:06:57 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/7991, CPU#6 Sep 1 16:06:57 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/7991, CPU#6

Sep 1 16:06:57 borg kernel: BUG: scheduling while atomic: VBoxHeadless/0x00000001/7991, CPU#6 Sep 1 16:06:57 borg kernel: Modules linked in: sit tunnel4 nfs nfsd lockd nfs_acl auth_rpcgss sunrpc vboxnetadp(N) vboxnetflt(N)

vboxdrv(N) af_packet tun cpufreq_conservative cpufreq_userspace cpufreq_powersave microcode f71882fg(N) acpi_cpufreq binfmt_misc edd xt_rt(N) ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables xt_quota2(N) xt_dscp iptable_mangle ipt_LOG xt_recent(N) x

t_DELUDE(N) xt_TARPIT(N) ipt_REJECT xt_CHAOS(N) compat_xtables(N) xt_geoip(N) xt_hashlimit xt_multiport xt_conntrack iptable_filt er xt_tcpudp xt_mark iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4(N) ip_tables x_tables ipv6 fuse nls_utf8 is ofs(N) nls_base(N) ext3 jbd mbcache loop dm_mod psmouse(N) thermal rtc_cmos processor rtc_core thermal_sys iTCO_wdt i2c_i801 iTCO _vendor_support evdev(N) wmi rtc_lib pcspkr hwmon kvm_intel(N+) button r8169 i2c_core sg kvm(N) raid456 async_xor async_memcpy as ync_tx xor raid0 ehci_hcd sd_mod uhci_hcd crc_t10dif usbcore raid1 md_mod(N) xfs exportfs ahci libata scsi_mod Sep 1 16:06:57 borg kernel: Supported: Yes Sep 1 16:06:57 borg kernel: Pid: 7991, comm: VBoxHeadless Tainted: G D N 2.6.29.6-jen82-rt #1 Sep 1 16:06:57 borg kernel: Call Trace: Sep 1 16:06:57 borg kernel: [<ffffffff802401ed>] schedule_bug+0x65/0x6a Sep 1 16:06:57 borg kernel: [<ffffffff804c4f9f>] schedule+0x80/0x672 Sep 1 16:06:57 borg kernel: [<ffffffff804c589f>] schedule+0x10/0x2b Sep 1 16:06:57 borg kernel: [<ffffffff804c650f>] rt_spin_lock_slowlock+0x169/0x259 Sep 1 16:06:57 borg kernel: [<ffffffff804c6f23>] rt_spin_lock+0x73/0x78 Sep 1 16:06:57 borg kernel: [<ffffffffa044f89f>] RTSpinlockAcquire+0xd/0xf [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa0447618>] SUPR0ObjRelease+0xa0/0x1d7 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa0447bce>] SUPSemEventSignal+0x6e/0x92 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa048ebcc>] g_abExecMemory+0x3870c/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa04a9cbc>] ? g_abExecMemory+0x537fc/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa046b3a9>] g_abExecMemory+0x14ee9/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa046b46c>] g_abExecMemory+0x14fac/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa046f3fa>] g_abExecMemory+0x18f3a/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa0470460>] ? g_abExecMemory+0x19fa0/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa048a5be>] g_abExecMemory+0x340fe/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa0471d29>] ? g_abExecMemory+0x1b869/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa0465ed2>] g_abExecMemory+0xfa12/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa04641b3>] g_abExecMemory+0xdcf3/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa04629aa>] ? g_abExecMemory+0xc4ea/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa045d8d7>] g_abExecMemory+0x7417/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa0499451>] g_abExecMemory+0x42f91/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa04671fb>] g_abExecMemory+0x10d3b/0x180000 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffff8026be03>] ? futex_wake_op+0x3fc/0x41f Sep 1 16:06:57 borg kernel: [<ffffffffa0446447>] supdrvIOCtlFast+0x3f/0x51 [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffffa044617f>] VBoxDrvLinuxIOCtl+0x3f/0x19f [vboxdrv] Sep 1 16:06:57 borg kernel: [<ffffffff802ea944>] vfs_ioctl+0x2a/0x78 Sep 1 16:06:57 borg kernel: [<ffffffff802eaead>] do_vfs_ioctl+0x26b/0x286 Sep 1 16:06:57 borg kernel: [<ffffffff802de65b>] ? fget_light+0x93/0xa9 Sep 1 16:06:57 borg kernel: [<ffffffff802eaf1d>] sys_ioctl+0x55/0x77 Sep 1 16:06:57 borg kernel: [<ffffffff8020bf02>] system_call_fastpath+0x16/0x1b

If there is anything I can provide to track down this problem, let me know. I just don't have an idea where to look at.

Change History

comment:1 Changed 4 years ago by frank

Still relevant with VBox 3.1.2?

comment:2 Changed 4 years ago by mkromer

Can be closed - confirmed to work in 3.2.4

comment:3 Changed 4 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Thanks for the feedback.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use