Ticket #1829 (closed defect: fixed)

Opened 10 years ago

Last modified 9 years ago

Kernel Bug "Scheduling with irqs disabled"

Reported by: bundabrg Owned by:
Priority: minor Component: other
Version: VirtualBox 1.6.2 Keywords:
Cc: Guest type: Linux
Host type: Linux


My Host: -

Quad Core 2.4Ghz Intel CPU 8 Gb Memory No Hard Drive (Diskless fat client) Ubuntu Hardy Heron 8.04 amd64 (Ubuntu Studio) Kernel: 2.6.24-19-rt

My Guests:

Ubuntu Hardy Heron 8.04 i386

I get this constantly in the hosts 'dmesg': -

[293528.625941] BUG: scheduling with irqs disabled: softirq-timer/2/0x00000000/32
[293528.625950] caller is rt_spin_lock_slowlock+0xae/0x1c0
[293528.625954] Pid: 32, comm: softirq-timer/2 Tainted: P        2.6.24-19-rt #1
[293528.625957] Call Trace:
[293528.625978]  [<ffffffff80478b00>] schedule+0xe0/0x110
[293528.625983]  [<ffffffff804793de>] rt_spin_lock_slowlock+0xae/0x1c0
[293528.626001]  [<ffffffff80249294>] lock_timer_base+0x34/0x70
[293528.626008]  [<ffffffff80249c77>] __mod_timer+0x37/0xe0
[293528.626021]  [<ffffffff88a3c7e0>] :vboxdrv:VBoxDrvLinuxGipTimer+0x0/0xf0
[293528.626028]  [<ffffffff88a3c859>] :vboxdrv:VBoxDrvLinuxGipTimer+0x79/0xf0
[293528.626035]  [<ffffffff80249616>] run_timer_softirq+0x296/0x520
[293528.626050]  [<ffffffff80245491>] ksoftirqd+0x121/0x2a0
[293528.626057]  [<ffffffff80245370>] ksoftirqd+0x0/0x2a0
[293528.626062]  [<ffffffff80245370>] ksoftirqd+0x0/0x2a0
[293528.626068]  [<ffffffff8025579b>] kthread+0x4b/0x80
[293528.626074]  [<ffffffff8020d308>] child_rip+0xa/0x12
[293528.626087]  [<ffffffff80255750>] kthread+0x0/0x80
[293528.626091]  [<ffffffff8020d2fe>] child_rip+0x0/0x12

Kernel is tainted with the NVidia Module.

The host is running a real-time kernel, which may be the reason its coming up. I'm sure I remember reading somewhere that the warning comes up when the calling program is doing something that _could_ be done a different (and thus more real-time) friendly way. Unfortunately I just can't find that link at the moment.

It doesn't break Virtualbox, and apart from dmesg being constantly filled with this, I havn't noticed any speed difference between a non-realtime and a realtime kernel so its really a FYI.

  • Brendan

Change History

comment:1 in reply to: ↑ description Changed 10 years ago by virtuser

Same here:

2.6.24-19-rt model name : Intel(R) Pentium(R) 4 CPU 2.80GHz 2G ram Nvidia tainted kernel also... Ubuntu 8.04 uptodate host windows XP guest

[601919.138641] BUG: scheduling with irqs disabled: softirq-timer/0/0x00000000/6
[601919.138655] caller is rt_spin_lock_slowlock+0x8e/0x170
[601919.138661] Pid: 6, comm: softirq-timer/0 Tainted: P        2.6.24-19-rt #1
[601919.138694]  [<c0326b55>] schedule+0xf5/0x130
[601919.138715]  [<c032740e>] rt_spin_lock_slowlock+0x8e/0x170
[601919.138780]  [<c01371f7>] lock_timer_base+0x27/0x60
[601919.138794]  [<f8f3d510>] VBoxDrvLinuxGipTimer+0x0/0x100 [vboxdrv]
[601919.138811]  [<c013792a>] __mod_timer+0x2a/0xb0
[601919.138837]  [<f8f3d5a9>] VBoxDrvLinuxGipTimer+0x99/0x100 [vboxdrv]
[601919.138877]  [<c01374da>] run_timer_softirq+0x21a/0x460
[601919.138883]  [<f8f3d510>] VBoxDrvLinuxGipTimer+0x0/0x100 [vboxdrv]
[601919.138908]  [<c01055e3>] common_interrupt+0x23/0x30
[601919.138944]  [<f8f3d510>] VBoxDrvLinuxGipTimer+0x0/0x100 [vboxdrv]
[601919.138958]  [<c0326ac0>] schedule+0x60/0x130
[601919.138984]  [<c0133a34>] ksoftirqd+0x134/0x290
[601919.139023]  [<c0133900>] ksoftirqd+0x0/0x290
[601919.139033]  [<c0141fc2>] kthread+0x42/0x70
[601919.139039]  [<c0141f80>] kthread+0x0/0x70
[601919.139051]  [<c0105857>] kernel_thread_helper+0x7/0x10
[601919.139077]  =======================

I only noticed this recently, perhaps related to all the updates in ubuntu lately...

comment:2 Changed 10 years ago by frank

To both of your: Did you enable the VT-x or AMD-V when running a VM? Please double check with your VBox.log as this special mode may fail to initialize even if enabled in the VM settings.

comment:3 Changed 10 years ago by bundabrg

Although my system is capable of VT-x, I don't have this enabled.

comment:4 Changed 10 years ago by virtuser

My cpu is not capable of VT-x or AMD-V ... However, the setting is ON.

No trace of VT-x or AMD-V in the log.

comment:5 Changed 10 years ago by frank

virtuser: Please make sure you enabled this setting in the BIOS. Please attach the VBox.log file of a session when you think you enabled VT-x/AMD-V.

comment:6 Changed 9 years ago by frank

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

No response, closing. Please reopen if this issue persists with version 2.1.0.

comment:7 Changed 9 years ago by virtuser

This bug is no longer present, the oldest logs I have do not contain the dump. I am now running 2.6.24-22-rt with 2.0.6-39765_Ubuntu_hardy.

Last time this occured it was on Aug 11 2008 while running kernel 2.6.24-19-rt.

Consider this closed.

comment:8 Changed 9 years ago by frank

Thanks for your feedback.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use