Thanks Colin, but also thank you all people all who helped report and
analyze this bug! Nice team work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723482
Title:
system hangs on boot after updates
alsa-utils (1.0.24.2-0ubuntu2) fixes my system.
Thanks, Colin!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723482
Title:
system hangs on boot after updates from 2011-02-22
--
ubuntu-bugs mailin
This bug was fixed in the package alsa-utils - 1.0.24.2-0ubuntu2
---
alsa-utils (1.0.24.2-0ubuntu2) natty; urgency=low
* Remove '(mounted MOUNTPOINT=/usr) and (mounted MOUNTPOINT=/var)' from
/etc/init/alsa-restore.conf's 'start on' condition. Not only is this
redundant, bec
Furthermore, the whole thing is redundant anyway since runlevel [2345]
implies that all filesystems listed in fstab have already been mounted!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723482
Titl
Actually, never mind the previous comment - it was obvious once I
thought about it the right way. The mounted event is SYNCHRONOUS:
anything that says 'start on mounted ...' will block mountall until it
comes back, and this is by design (see mounted(7)). Thus the effect of
alsa-restore's 'start on
I am working on debugging this. For the record, I think that the alsa-
restore.conf workaround is essentially a coincidence; it seems to be
tickling some kind of race condition elsewhere. It's quite difficult to
extract debugging output from this stage of the boot process, which is
slowing me dow
Sébastien and Eric: Thanks! Confirmed here as well; normal system boot
was restored by moving alsa-restore.conf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723482
Title:
system hangs on boot afte
I confirm that after renaming
/etc/init/alsa-restore.conf
to
/etc/init/alsa-restore.conf.disabled
the system does not hang anymore at reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/72348
** Changed in: mountall (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723482
Title:
system hangs on boot after updates from 2011-02-22
--
ubuntu-bugs maili
apt-get install alsa-utils
hangs the system at next reboot.
Just rename the /etc/init/alsa-restore.conf to
/etc/init/alsa-restore.conf.disabled make it boot again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Doing install ubuntu-desktop after upgrading natty gives me the hang.
So the path to reproduce is :
Install maverick with multiple separate FS minimal install
upgrade to natty
then install ubuntu-desktop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
ok, maybe not.
I got a different behaviour but not a hang.
Systems switchs to vt7 and then stays on this vt.
Nothing happens then.
But system runs, switching back to tty1 show the login as usual.
So no luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Ok, I managed to reproduce the breakage.
1- Install maverick minimal (I just selected openssh server) with multiple
separate FS on LVM
2- update maverick -> latest update.
3- change apt to point to natty
4- upgrade -> linux-image, mountall, libc6, grub-pc
then hang
--
You received this bug
I tried to setup a natty server in a Virtualbox machine.
Unfortunately, the VM is working OK.
I'm now trying to setup a maverick then upgrade to natty to see if it gonna
break.
Stay tuned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Hi
I've upgraded another machine (netbook) yesterday. This one has one ext4
partition only and is affected by the bug also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723482
Title:
system hangs
Hi again
The #24 solution is fast and working (you don't need to edit any grub options
by the way).
My opinion: it's mountall!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723482
Title:
system han
My machine, that has separate /var and /usr is affected with this problem
exactly.
The other (laptop) having many mountpoints but /usr /var are not separate from
/ doesn't suffer- boots normally.
At first I've chrooted from GRML to remove ureadahead and it doesn't help.
Now I'll try some of the a
Here's the quickest way I've found (this requires that you've set a root
password):
* Edit the normal (non-recovery) grub entry, removing "quiet",
"splash",and "vt_handoff". Optionally add "--verbose".
* Press Ctrl-X and let the system run through the boot process until it
hangs.
* Hit SysRq-i,
Here is the technique I use to work around the problem, it might not be any
better than Sebastian's technique, but anyway here it is, in the hope it might
help Herbert:
- on grub screen, hit 'e' to edit boot commands
- add init=/bin/bash to the kernel command line
- press F10 to boot the kerne
It should read :
getty -8 -n -l /bin/bash 38400 tty8&
getty -8 -n -l /bin/bash 38400 tty6&
If you don't gives the getty that magic value, it's won't work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
does not work for me.
1.: although I have all recent upgrades I still have kernel 2.6.37 (I do not
know why, It is just not used, 2.6.38 does not even show up on list)
2.: there is nothing like that "crashkernel=..." thin in my grub boot line
3.: when executing the chroot /root /bin/bash command
To help people who are stuck, here's the operations I need to do at each boot :
When in the grub chooser (hold shift while booting if it does not show up),
edit the boot configuration :
go the to line which says :
linux /vmlinuz-2.6.38-5-generic root=/dev/ ro
crashkernel=384M-2G:64M,2G-:128M
I have two machines on which I do the alpha natty updates at the same
time. One of them has few partitions, and boots fine. the other one has
many partitions, and can't boot.
Using /dev/sda* device files instead of UUIDs does not help.
A workaround is to manually kill mountall process during init
A T61 of mine was affected by this bug as well. Downgrading mountall
from rev. 2.22 to 2.21 did not help, no luck with downgrading ureadahead
from 0.100.0-10 to 0.100.0-9 either.
I then tried booting into Ubuntu 10.10 which was installed on the same
machine (but on a different root partition) and
(The /dev/shm bug is unrelated, it seems -- see Bug #566788)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723482
Title:
system hangs on boot after updates from 2011-02-22
--
ubuntu-bugs mailing l
** Attachment added: "Anacoluthon's mounts state after interrupting a manual
run of mountall."
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/723482/+attachment/1869708/+files/anacoluthon-proc-mounts.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Attachment added: "Anacoluthon's mount state after the systems boots
completely."
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/723482/+attachment/1869709/+files/anacoluthon-proc-mounts.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Attachment added: "Screenshot of anacoluthon, blocked at a manually run
mountall."
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/723482/+attachment/1869707/+files/anacoluthon-mountall-blocked.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Attachment added: "Anacoluthon's mountall output, first and second runs
separated with a blank line."
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/723482/+attachment/1869706/+files/anacoluthon-mountall.log
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "Anacoluthon's mounts state after forcing a prompt with
SysRq-i"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/723482/+attachment/1869705/+files/anacoluthon-proc-mounts.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Attachment added: "Anacoluthon, blocked at boot."
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/723482/+attachment/1869704/+files/anacoluthon-boot-blocked.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I've tried to grab as much state as I could. Attached is the fstab from
anacoluthon, a T42 Thinkpad that suffers from this problem.
When booting, I choose the normal (i.e., non-recovery) GRUB entry, since
the goal's to bring the system up. I edit the entry before booting,
removing the quiet, splas
Here's a snapshot of the console at hang point
** Attachment added: "point where boot hangs"
https://bugs.edge.launchpad.net/ubuntu/+source/mountall/+bug/723482/+attachment/1868873/+files/IMG_20110224_080756.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Here's the dpkg.log (easy part).
** Attachment added: "dpkg.log from 02/01 to 02/24"
https://bugs.edge.launchpad.net/ubuntu/+source/mountall/+bug/723482/+attachment/1868853/+files/dpkg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Also, could you attach the full /var/log/dpkg.log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723482
Title:
system hangs on boot after updates from 2011-02-22
--
ubuntu-bugs mailing list
ubuntu
Can you add --verbose to the 'exec mountall' line in
/etc/init/mountall.conf and report the last screenful of output?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723482
Title:
system hangs on boot
Unfortunately, commenting UUID did not fix the boot problem.
I realized it after a reboot. mountall started to hang again.
I made various attemps.
Behaviour is unconsistent. Somethings, mountall mounts 1 fs, sometimes 3-4,
sometimes nothing.
After a few tries, the mountall mounts everything and re
Here's an ltrace of the mountall.
** Attachment added: "ltrace of an hanging mountall"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/723482/+attachment/1867267/+files/mountall.ltrace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I have a similar problem
After today's updates, I cannot boot my laptop anymore
I boot selecting Ubuntu safe-mode, and when laptop hangs up, press
SysReq+i and this actions give shell.
I see:
init: ureadahead-other main process (903) terminated with status 4
# df -h
/dev/sda2 /
none/dev
I'm indeed proti from freenode.
I made some progress regarding this issue.
I found that if you comments all the entries in the /etc/fstab that refers to
an UUID (in my case, it's /boot and the swap), then mountall behaves normaly
and the system is able to boot up to the gdm login.
The mystery sta
proti states his home system was still usable today until applying the
last sequence of updates:
1.
2011-02-22 21:05:19 status installed man-db 2.5.9-3
2.
2011-02-22 21:05:21 status installed libpam-modules 1.1.2-2ubuntu3
3.
2011-02-22 21:05:32 status installed man-db 2.
41 matches
Mail list logo
