Results 1 to 5 of 5

Thread: BUG: soft lockup

  1. #1
    Join Date
    May 2005
    Location
    Marlborough, UK
    Beans
    469
    Distro
    Ubuntu Karmic Koala (testing)

    [Solved] BUG: soft lockup

    Hi,

    I've been running Karmic on my server for over a month with no major problems until today when I tried to connect to the computer to find it wasn't responding. I rebooted it and it didn't come back up.

    Plugging in an external monitor showed GRUB was having issues and the Super GRUB CD didn't seem to be able to fix them (thinking about it I'm not sure it supports GRUB 2 yet).

    Eventually after resetting the BIOS it booted again and seemed to work okay until it started checking my drives. It seemed to finish but started giving errors saying the following:

    BUG: soft lockup - CPU#0 stuck for 61s [fsck.ext3]
    BUG: soft lockup - CPU#0 stuck for 61s [fsck.ext3]
    BUG: soft lockup - CPU#1 stuck for 61s [dhclient]
    ...

    This went on and I rebooted. The next time it booted it gave me errors about "Code: Bad RIP value." then told me it was fixing it but needed to reboot to fix it. This I did and was rewarded with it rebooting several times before it successfully booted to the login prompt with an error output and a call trace part way through the boot process.

    Logging in seemed possible but it never got to the shell prompt, instead it gave a BUG: soft lockup - CPU#1 stuck for 61s! [landscape-sysin:3209] error followed by another stack trace. This it repeated every 61 seconds. I rebooted. It soft locked even sooner.

    Does anyone have any idea of a) how I can fix this and get my system back in to a working state or b) why this is happening and what I can do to prevent it in the future? All the hardware is pretty new but the PC has been running 24/7 for about a month.
    Last edited by Haegin; September 13th, 2009 at 11:52 AM. Reason: Problem resolved.
    Regards,
    Haegin
    If all else fails curl up in bed with a good book.
    "<mc44> rob: every time you don’t read the topic, god kills a lolcat"

  2. #2
    Join Date
    May 2005
    Location
    Marlborough, UK
    Beans
    469
    Distro
    Ubuntu Karmic Koala (testing)

    Re: BUG: soft lockup

    Just an update with more symptoms/problems. Apt is segfaulting either at the end of the update process or as soon as I run another apt command. I believe this is when it is accessing the apt database. Running strace -c apt-get update shows the following failures:

    Code:
    Syscall        Errors
    ^^^^^^^^^^^^^^^^^^^^^
    open           22
    stat           25
    access         8
    unlink         5
    All other calls are fine. I'm now wondering if it could be the root partition which is having problems as the syscalls are all to do with reading files.
    Last edited by Haegin; September 13th, 2009 at 11:21 AM.
    Regards,
    Haegin
    If all else fails curl up in bed with a good book.
    "<mc44> rob: every time you don’t read the topic, god kills a lolcat"

  3. #3
    Join Date
    May 2005
    Location
    Marlborough, UK
    Beans
    469
    Distro
    Ubuntu Karmic Koala (testing)

    Re: BUG: soft lockup

    Sorry for the triple post but I removed the /var/cache/apt/*.bin files to sort out apt and have updated the BIOS on my motherboard and currently the system seems fine. I'll mark this as solved for now.
    Regards,
    Haegin
    If all else fails curl up in bed with a good book.
    "<mc44> rob: every time you don’t read the topic, god kills a lolcat"

  4. #4
    Join Date
    Dec 2008
    Location
    Isolated Digital Reign
    Beans
    151
    Distro
    Kubuntu Development Release

    Lightbulb Re: BUG: soft lockup

    ^^ Thanks for the BIOS update suggestion!

    That was the one that caused a similar issue with KVM at my machine.

    C]-[aoZ

  5. #5
    Join Date
    Apr 2008
    Location
    Southern California, USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: BUG: soft lockup

    Quote Originally Posted by Haegin View Post
    Sorry for the triple post but I removed the /var/cache/apt/*.bin files to sort out apt and have updated the BIOS on my motherboard and currently the system seems fine. I'll mark this as solved for now.
    Thanks for this. I ran across someone else removing the *.bin files after getting segmentation faults, and were then able to resume successful updates.
    boot_info_script | AMD64 Athlon X2 Dual-Core - nVidia Geforce 6150 SE - 4GB DDR3

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •