The system hangs on startup

Bug #29252 reported by Sergey V. Udaltsov
12
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Fix Released
Medium
Scott James Remnant (Canonical)

Bug Description

Installed ubuntu "Dapper Drake" on Power G5 (it was successfully running Breezy before). Trying to boot, the system hangs (absolutely) at the very start. The last thing it is doing is "Detecting and activating hardware" - and nither "Ok" nor "Fail" appears. The keyboard freezes.

Actually, if I comment out /sbin/udevplug from /etc/init.d/udev - the systems starts ok. Then I can activate udevplug again and restart /etc/init.d/udev - and I can work. But I do not think it is a healthy way.

Revision history for this message
Phil Bull (philbull) wrote :

Thanks for the report.

Could you provide some more information, please? Try some of these procedures to see if you can find any useful info:

https://wiki.ubuntu.com/DebuggingProcedures

Changed in udev:
status: Unconfirmed → Needs Info
Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote : Output of lspci

lspci -vv

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote : Output of dmesg

I had to patch /etc/init.d/udev - start udevplug in background:

udevplug &

and ignore its status. Otherwise machine just hangs at that point

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

The machine is Power G5 2*2.0 Ghz/512M RAM, 160G HDD.
If you need more info, just let me know...

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Could you please be more specific about exactly what you installed.

"Dapper Drake" has not been released yet, so which pre-release version did you install? Was it one of the Flight CDs, in which case, which number? Or was it a daily, in which case for which date?

Thanks

Revision history for this message
PtOLU8zjbZxlgNOiyGyd (lkgdx5kefrptmd7ccufa-deactivatedaccount) wrote :

Please examine bug 28439 and bug 29541 as they point to the same problems in i386. On my particular case, I can point to a breezy dit-upgrade last monday, a daily on last Wednesday and daily dist-upgrades since then.

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

> Could you please be more specific about exactly what you installed.

Last Flight prerelease of Dapper, from CD. Latests updates did not change anything (doing dist-upgrade daily).
udev 079-0ubuntu3
linux-image-2.6.15-13-powerpc64-smp

If you are interested in any other packages versions - just let me know.

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

On bug 28439 people at least get failure after a minute - while I get nothing, just hanged system (even CapsLock is not working). Same about 29541.

Revision history for this message
PtOLU8zjbZxlgNOiyGyd (lkgdx5kefrptmd7ccufa-deactivatedaccount) wrote :

Plese see my cooments to bug 28439 I finally got an error message.

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

Alejandro,, your comment makes sense to me. Any ideas about workaround?

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Please boot your system, editing the kernel command line (from the grub menu) to remove the "splash" keyword and add "init=/bin/sh" in its place

Instead of booting your system will drop you at a prompt... at this prompt do the following:

1) Run "udevd --daemon"
2) Check that /dev/.udev/queue does NOT exist
3) Run "udevplug -s -v"
4) Report the last line before it hands
5) Wait for up to three minutes, to see whether it times out and drops you back to the shell.

Thanks

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

Unfortunately I cannot follow these instructions. The system gives me:
sh-3.1#
and hangs. CapsLock does not work. Probably the issue is not with udev only - but with the kernel as well.
BTW, since I am using Mac, I don't have grub - only yaboot. Just to clarify the context...

Revision history for this message
PtOLU8zjbZxlgNOiyGyd (lkgdx5kefrptmd7ccufa-deactivatedaccount) wrote :

I posted the resulst of the suggested test to bug 28439

Sergey, you can create a new entry in your yaboot configuration file duplicating the one you use to boot up normally and replace slpash for init=/bin/bash". For some reason, init="/bin/sh" kicked into the BusyBox, which is not what your want.

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

Ok, I created the entry Linux.debug (with init=/bin/sh), see a lot of interesting stuff
The shell is still unusable (the system is hang, no CapsLock). The only error message I see is:
/init: 102: cannot create /dev/.initramfs/progress_state: Directory nonexistent
After this line there are some USB-related lines (hub found, 3 ports detected, 2 full speed devices and one low speed device - addresses 2, 5, 6).
then prompt:
root@(none):/#
And the system is dead.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Are you sure the system is dead?

It might just be that your keyboard isn't working ;) Is it a USB keyboard?

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

Yes it is USB keyboard - Macs don't have other keyboard. And at this stage there is no networking - so I cannot check using ping or smth...
So if you give me another way to check the system...;)

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

I am reasonably convinced that this has been fixed, I've seen no new duplicates of this bug since the udevplug fix.

Please make sure your system is completely up to date, if you are still having the same problem, please reopen the bug.

Changed in udev:
assignee: nobody → keybuk
status: Needs Info → Fix Released
Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

Yes, it seems to be ok now. Thanks a lot.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.