"CPU stuck" in 3.1.6 Linux 2.6.32-3 => Fixed in SVN

[Kyle Smith]

After updating my debian unstable guest to 2.6.32-3, I found that the system did not boot. I saw a lockup during kernel output at roughly 4 seconds. 61 seconds later I would see a stack trace that ran off the screen.

Adding 'quiet', I could see: [ 66.572793] BUG: soft lockup - CPU#0 stuck for 61s! [modprobe :92]

This happens every 61 seconds.

I found a strange post here about a workaround: ​http://crunchbanglinux.org/forums/topic/6463/problem-running-debian-inside-virtualbox/

Interestingly, as he said, lowering my RAM allocation from 1024MB to 512MB worked.

I tried:

• Upgrading to kernel 2.6.32-4
• Upgrading to virtualbox 3.1.6 (originally 3.1.4)

Attached are my VBox.log files, though I didn't see anything too helpful - I really don't know what I'm looking at.

[Frank Mehnert]

Ok, so this happens with both VBox 3.1.4 and 3.1.6, right?

[Kyle Smith]

Frank,

Yes, that is correct. 3.1.4 with any 2.6.32 kernel is what I am seeing.

[Kyle Smith]

Replying to askreet:

Frank,

Yes, that is correct. 3.1.4 with any 2.6.32 kernel is what I am seeing.

*3.1.4 or 3.1.6 with any 2.6.32 kernel -- it's been a long day.

[arand]

I'm seeing this on guest: Linux debian 2.6.32-3-686 i686

(host Ubuntu 9.10 32bit, virtualbox 3.0.8_OSE)

If lowering the RAM to ~620mb booting seems to work (although X/kdm won't start, but that may be unrelated). Also, increasing the RAM of the guest to 1819Mb seems to enable booting (and X).

So strangely enough there seems to be a range of ~600-1800Mb RAMB where things go wrong.

I've also seen this similar issue on Fedora 13 alpha.

[Frank Mehnert]

Sounds like related to ​this thread. Will be fixed with the next release.

[arand]

Changeset 28090 for trunk/src/VBox/VMM/VMMAll/PGMAllBth.h applied with a bit of fuzz to virtualbox-ose (3.0.8-dfsg-1ubuntu1) karmic

...Solves the issue seemingly completely.

Attaching dpatch created, might be useful for others.

[Frank Mehnert]

Fixed in VBox 3.1.8.

[mattn]

debian stable - kernel 2.6.26-2-amd64 and virtualbox 3.2.6 r63112

same error as mentioned above: "BUG: soft lockup - CPU#0 stuck for 61s!"

VM has 10GB ram and 7CPUs - setting this to 640MB RAM works and the machine boots again

[mattn]

oh - forgot to mention - host system is "SunOS 5.10 Generic_142901-11 i86pc i386 i86pc"

[Frank Mehnert]

Still relevant with VBox 4.1.6?

[Frank Mehnert]

No response, closing.

[lipixx]

The problem continues.

Host: uname -a Linux terminator2 3.2.0-2-amd64 #1 SMP Mon Jun 11 17:24:18 UTC 2012 x86_64 GNU/Linux Debian GNU/Linux wheezy/sid Virtualbox 4.1.16_Debian r78094

Guest: Windows 7 64 bit, 1024MB Ram, 27MB video, 1monitor, 1x100Gb VDI HD, 1 LiveCD. The crash was in the grub of the live cd, waiting for me to choose an option => doing nothing.

I added a kern.log.dump file with the stack trace.

[Frank Mehnert]

lipixx, still relevant with VBox 4.1.22 / 4.2.0? If so, please add a VBox.log file of such a VM session.

[Frank Mehnert]

No response, closing.