Opened 14 years ago
Last modified 11 years ago
#6425 closed defect
"CPU stuck" in 3.1.6 Linux 2.6.32-3 — at Initial Version
| Reported by: | Kyle Smith | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 3.1.6 |
| Keywords: | cpu | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
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.
