** Changed in: mountall (Ubuntu)
Status: Confirmed = Fix Released
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
On Tue, 2010-02-23 at 02:35 +, Anand Kumria wrote:
When do you expect the fixed to be uploaded? I've not seen anything about
udev changing in any recent upgrades.
This was uploaded to lucid last week
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Startup fails somewhere around
OK - I still have issues during startup (mountall never emits the 'filesystem'
event) but we can track that in another bug.
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of
When do you expect the fixed to be uploaded? I've not seen anything about udev
changing in any recent upgrades.
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Bugs,
The original report appears to be related to missing events from udev,
which we discovered the cause of at the recent sprint. Once the fix for
that is uploaded, I'm going to mark this as fixed, given there have also
been large numbers of changes to mountall that probably cure other
people's
I think was fixed in mountall-2.4; but this bug appears dead.
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Anything further I can assist with here?
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
After a few more cycles of debugging, it appears that mountall is SIGSEGVing
when the remount of / to rw occurs.
You can test this by changing grub to mount the root device 'rw' instead
of 'ro' and mountall no longer fails.
Note: I had significant difficulty reproducing the problem as
Hi there,
I also have this bug too -- with similiar debug logs (which I've only
capture via camera; but I can transcribe them).
One difference I have is that this affects me with both 2.6.32-8-generic
and 2.6.32-9-generic as well as the 2.6.31-16-generic kernel.
If you need any further
Still happens here on both my systems
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I been debugging one of my systems that was having the same problem on a
system I rebooted after it was upgraded to upstart 0.6.3-11. It was
looking to be a problem with mountall. When I would initctl emit
filesystem, it would just hang. Not sure if this is the same issue now
as it turns out that
I have been testing LinuxFromScratch and wanted to use only upstart with it (
no old sysv scripts ).
Mountall hangs when emitting events using some ~20% cpu if root is mounted as
read-only at boot.
Changing it to rw seems to make it boot just fine.
--
Startup fails somewhere around filesystem
How often is it reproducible on your system?
I'll try to look at CPU usage next time i catch this problem to see if it is
the same bug.
Does initctl emit filesystem work for you to continue boot?
--
Startup fails somewhere around filesystem or HAL being started
So far on every boot.
I have set up tty1 to start on local-filesystems. initctl emit works and
returns immediatly.
Then emitting local-filesystems for second time, without rebooting, initctl
itself hangs, i'll have to ctrl+c it and then it usually returns immediately
again. Currently tty1,
Well, since it's LFS, maybe you could recompile mountall with debug
symbols and use gdb to look where mountall hangs?
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Ok, not very handy with gdb yet. mountall backtrace in attachment.
initctl backtrace:
0x00393422 in __kernel_vsyscall ()
#0 0x00393422 in __kernel_vsyscall ()
#1 0x001e4b9c in poll () from /lib/libc.so.6
#2 0x00be80fb in _dbus_poll (fds=0xbfbcaa34, n_fds=1, timeout_milliseconds=-1)
at
Meant to add, that is 'vanilla' upstart-0.6.3 , ubuntu 0.6.3-10 is the
same, but 'local-filesystems' isn't emitted until 'filesystem' is
emitted too.
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification
So mountall keeps writing mtab over and over again.
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I found that if upstart re-reads a job config file, e.g. after i rename
it, and this job hasn't yet been started, this job doesn't get any of
the previously emitted events. Maybe this takes place on some
conditions?
--
Startup fails somewhere around filesystem or HAL being started
I suspect that when mountall remounts / filesystem (ro - rw), an
inotify event might be generated (not sure if it is), which in some
cases is gotten by upstart afte filesystem event is emitted, thus making
all the jobs not get this event.
--
Startup fails somewhere around filesystem or HAL being
Hello, I have the same problem too.
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The above seems to be systematic.
Another two failed logs show same swap
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
nope, spoke too soon, currect boot shows same swap
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
and spoke too soon again, I forgot that I continued the boot using
initctl emit filesystem, so last comment is wrong
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Exactly same behavier of modem-manager here
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
And this log looks very normal.
On succcesfull boot, these lines are swapped:
fsck from util-linux-ng 2.16
activating /dev/disk/by-uuid/69bc5081-c9e0-4b14-8912-ab95c2a3713a
But I logged both boots (succesfull and not) only once
--
Startup fails somewhere around filesystem or HAL being started
Mountall log when it fails:
mounting /proc/sys/fs/binfmt_misc
mount /proc/sys/fs/binfmt_misc [1116] exited normally
mounting /sys/fs/fuse/connections
mount /sys/fs/fuse/connections [1117] exited normally
mounting /sys/kernel/debug
mount /sys/kernel/debug [1118] exited normally
mounting /dev/pts
On Fri, 2009-11-13 at 18:06 +, Ruslan wrote:
The strange thing is that when the system starts normally, modem-manager
output isn't displayed even when 'quiet' and 'splash' kernel commands are
omitted. In such mode just fsck says something, some other logs show up, but
no modem-manager
The strange thing is that when the system starts normally, modem-manager output
isn't displayed even when 'quiet' and 'splash' kernel commands are omitted. In
such mode just fsck says something, some other logs show up, but no
modem-manager log.
But every time startup stops, this modem-manager
2 Maxim Levitsky
Is it frequent on your system? If yes, does this problem show up if you
add --debug kernel command line option? I cannot reproduce this problem
in --debug mode... at least have not reproduced yet.
--
Startup fails somewhere around filesystem or HAL being started
Yep, its not hal fault.
There was no attempt to start it.
Log entries are most likely from older boots or so.
initctl emit filesystem works fine
--
Startup fails somewhere around filesystem or HAL being started
https://bugs.launchpad.net/bugs/474907
You received this bug notification because
I confirm same behavior on both my systems.
I also set tty6 to start on startup, and I found that hal wasn't running.
System logs show that 'hal exited with exit code 1', but I need to retest this.
--
Startup fails somewhere around filesystem or HAL being started
32 matches
Mail list logo
