soft lockup - CPU#0 stuck for 61s

[Angelic]

I recently installed 10.4 on my laptop and I love it, so I wanted to install it on my desktop. It's a somewhat older computer, AMD3000+ nForce 2, 1.5 gigs of Ram and a Radeon x1650. Whenever I try to start the Live CD I get the error soft lockup - CPU#0 stuck for 61s and it doesn't continue. Anyone know what could cause this?

[carbonrobin]

I also have this problem on an older desktop. AMD Athlong XP 1800+ 1GB RAM ATI Radeon 9550 Currently dual boot Ubuntu 9.04 and Windows XP Pro SP3.

[tgalati4]

First, clean out the machine and reseat the RAM. Run memtest for 30 complete cycles. This will take overnight. If you pass with no errors, then we can start looking at other things.

Also, reseat the power connectors to the motherboard and reseat all ribbon cables and any other cards in the system.

[greg_stager]

I also had this issue.

My solution to this was to install 9.10 and then run the upgrade from within the program.

I know it is a bit of a work around but the 9.10 install CD worked where the 10.04 didn't. I suppose it could have been a problem with the disk I created but I did not look at that yet. I will try it on a different system when I get a chance and replace it if necessary.

Hope this was a help to someone.

Stags

[Havokdan]

I am with this problem, do not start the live cd, but when I press F6 and mark the option "nodemoset," the live cd starts, but when I do I install the screen is black and so I tried various solutions here, but as not had success yet, I'll wait for version 10.10 to try again, for the record is the first time I have problems installing ubuntu, always tried every version that was released since 7:04 with no problem, I was waiting for this release to effect a full exchange of windows xp to ubuntu. I hope I have better luck next version.

* I can read English, but what I write here is with the help of google translator.

[carbonrobin]

First, clean out the machine and reseat the RAM. Run memtest for 30 complete cycles. This will take overnight. If you pass with no errors, then we can start looking at other things.

Also, reseat the power connectors to the motherboard and reseat all ribbon cables and any other cards in the system.

I'll try that tonight. I do have a question about this, why would Ubuntu 9.04 and previous Live CDs work?

[tgalati4]

It could be related to the PAE kernel in Lucid. PAE--Physical Address Extension allows your 32-bit distro to see more than 4 GB. It affects how RAM is addressed. It's possible that your machine's CPU can't handle PAE--causing a lockup.

I don't know how to turn PAE off in Lucid. The older, Live CD's use the normal kernel, which presumably works with your hardware.

The cleanout procedure is just to give you something to do until I can come up with a more creative solution.

[MyotisSI]

I have the same problem, I've installed 10.04. with alternate CD, I normally worked in ubuntu, but after restart I got a black screen and after a sea of code the line:
soft lockup - CPU#0 stuck for 61s!

I think I'll revert to 9.10.


Update: 7. may 2010
I installed 9.10 and then upgraded via network to 10.04.
The install went smooth, but after the restart, there was again soft lockup - CPU#0 stuck for ...

I reinstalled 9.10. For now that is the only solution I found.

[WolfGero]

I think I may have had the same problem:

BUG: soft lockup - CPU#0 stuck for 61s! [plymouthd:401]

I've got no solution but a workaround, adding

nomodeset

to the kernel parameters.

To temporarily add a kernel parameter:

• press 'Esc/Escape' for selecting a kernel at early boot time
• select your kernel and press e
• add nomodeset to the line and press enter, then b

Even using

radeon.modeset=0

is enough for me to get rid of the hanging boot. Hope this helps some other people, too, since I only registered with ubuntu forums to leave this comment.
Wolf
---
(VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE])

[gary987]

I don't think is has anything to do with 4G+ memory, or to do with bad memory.

My computer just started doing the bug...on Linux Mint as well. It wasn't there a couple of days after the install, but now it is.


Is everyone running an ATI card on a nforce2 board?

I just pulled my radeon 8500 out and tryed running the onboard Nvidia gforce and so far the bug hasn't come up again.