Failure to boot

[Darren]

After doing the latest updates my computer failes to boot.It would appear to get 3/4 throught the kubuntu indicator boot line then freeze.
After several boot attempts I got this message.
Starting up...
Loading,please wait...
Kinit: name_to_dev_t(/dev/disk/by-uuid/d769fa13-3487-4bf3-8c03-19f5733837381)=h
da5(3,5)
Kinit:trying to resume from /dev/disk/by-uuid
Knit: no resume image, doing normal boot...
ubuntu feisty (development branch) kubuntudesttop tty1
kubuntudesktop login: [55.120000] Bug: Soft lockup detected on CPU#0!

Well that all I can give you.

[oddaolse (oddaolse)]

I have similar experience. Installed Feisty beta. Upgraded. After that I get the same messages as Darren. Except for the last bit. I do not get "Bug: Soft lockup detected on CPU#0". I get a login prompt an can log onto the console. I think I might be able to provide you with logs. (I will probably be able to get them by booting up the XP partition).

What information do you need?

Regards

[Edward Morgan (marenghi)]

Same problem aswell with feisty beta although the last part i haven't got (about the cpu)

i'm not sure what logs you'd need but heres 2 that may help

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[Darren (dcottrell)]

Hi since I sent in that bug I did a reinstall again.
Was having an iffy time rebooting got another error report at boot up I
tried
to report it on launchpad but gave up after half an hour of trying.
After the last set of updates my computer boots up most of the time but it's
learned some new tricks.
If I turn it on and leave it alone it will boot up most times some times on
boot up it will reboot itself before finishing the boot, if I let it alone
it will reboot
all by itself after it's up and running,or after boot up if I'm working on
it, it will freeze up.
I ran the 'uname -a' and got this.
Linux desktop 2.6.20-15-generic #2 smp sun apr 15 07:36:31 utc 2007 i 686
gnu/linux
I then tried to run the 'dmesg > dmesg.log' got nothing just my command
line.
I then tried to run the 'sudo 1spci -vvnn > 1spci-vvnn.log'got bad command
line.
Sorry that's all I got wish that I could be of more help.
Keep up the great work.
Darren
----- Original Message -----
From: "Brian Murray" <email address hidden>
To: <email address hidden>
Sent: Wednesday, April 18, 2007 5:07 PM
Subject: [Bug 105316] Re: Failure to boot

Thanks for taking the time to report this bug and helping to make Ubuntu
better. Unfortunately we can't fix it, because your description doesn't yet
have enough information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's additional options), as required by
the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next
response. It should be one, long line of text which includes the exact
kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file
'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the
resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related
bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies .
Thanks in advance!

** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.20
     Assignee: (unassigned) => Brian Murray
       Status: Unconfirmed => Needs Info

--
Failure to boot
https://bugs.launchpad.net/bugs/105316
You received this bug notification because you are a direct subscriber
of the bug.

[Brian Murray (brian-murray)]

'dmesg > dmesg.log' puts the output of the dmesg command into a file called dmesg.log. That should be added to you bug report as an attachment. The correct command for the second thing we need is 'sudo lspci -vvnn' where it is a lower case 'L' not a '1'. Thanks.

[zebda (thierry-mandon)]

Hi

I have the same problem . I give you the output of the dmesg command
have you an idea ?

thanks

[zebda (thierry-mandon)]

boot file

[zebda (thierry-mandon)]

please forgot th first sent because i boot the computer with livecd and dmesg command give a output for the livecd distribution .
i make a mount of the hard drive in order to retrieve dmesg log
thanks for help

[oddaolse (oddaolse)]

Please find attached dmesg,txt, lsci-vnn.txt uname.txt

[zebda (thierry-mandon)]

i have solve my problem : the error come after the message Kinit
it's due to udev script : all script in /etc/init.d with extension .new_pkg must be renamed without .new_pkg
and the filesystem / is mount with readonly right
so i issue the command : mount -o remount,rw /
and now gnome starts ...

[oddaolse (oddaolse)]

I do not have any files in /etc/init.d with extension .new_pkg

I have dual boot on this machine (XP) - so I am still able to use it. But if I do not get this solved soon I will have to reinstall...

[zebda (thierry-mandon)]

sorry !!
all corrupts files are in /etc/event.d

[oddaolse (oddaolse)]

Actually I think I was hit by another bug.

I found https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/89853, followed the instructions and now the machine boots ok.

Thanks for all assistance!

[ScdGigi (scdgigi)]

I cant solve this problem yet..
I haven't found any .new_pkg files in /etc/event.d
what can i do?
 :(

thanks

[noktan (noktan)]

I found this solution on this page as Bug #66637 in util-linux (Ubuntu):

1, determine your swap with 'fdisk -l'
2, do mkswap on your swap partition - RECORD THE UUID WHICH THIS COMMAND
OUTPUTS
3, now use this UUID to put into fstab and resume
files...(RESUME=UUID=<the-swap-partition-uuid-from-vol_ID
should go in /etc/initramfs-tools/conf.d/resume
4, update-initramfs -u
5, reboot normally after this finishes

when the system has restarted again - do 'swapon -s' to check if your
swap is active

Obviously, disk UUID in output from 'mkswap' is different from the one you find with 'ls -la /dev/disk/by-uuid/'

[jan37 (dotjan-msn)]

noktan: i did your 5 steps on a gutsy machine (Fujitsu Siemens Amilo Pi 1536 with ati x1400 mobility) and i have still these "no resume image...." errors when i typ ctrl+alt+f1

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

If anyone is still wishing to progress this bug report they need to take note of Brian Murray's instructions above.
Only two people have responded to Brian's instructions and it seems that they had different issues to that originally reported in this commentary.

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!