I agree with your diagnosis.
It looks like ply_boot_client_flush() is blocking on a write() to
plymouthd, which is blocking on a write() back to the process calling
that, because the former function only flushes pending writes (in a
blocking way) without reading responses
I'd say then that the bu
possible duplicate of 554079 ?
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
Looks to me like this is probably a bug in the ply_boot_client_flush()
added in revision 1296.
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Aha - looks like a pretty classic deadlock then, both ends in a blocking
write and nobody reading.
Thanks for helping to pin this down.
Scott, you know the plymouth protocol code better than I do; can you
confirm that this is what's happening here? Is this a plymouth bug, or
a mountall bug for m
** Also affects: plymouth (Ubuntu Lucid)
Importance: High
Status: Triaged
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Reading symbols from /sbin/mountall...Reading symbols from
/usr/lib/debug/sbin/mountall...done.
done.
Attaching to program: /sbin/mountall, process 343
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
[Thread de
Suspected as much.
Can you get a backtrace of this mountall process, too?
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
Yes, there is:
mountall --daemon --force-fsck
Keep in mind that I touched /forcefsck to trigger the problem.
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
mkibini,
When this hang happens, is there a mountall process running?
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
For the sake of completeness, here it is the bt for the "plymouth quit"
process
** Attachment added: "plymouth-bt.txt"
http://launchpadlibrarian.net/43991590/plymouth-bt.txt
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because
Here you are the backtrace of plymouthd.
While getting this I also noticed that if, while the fsck is in process
and plymouth is not hanged, I switch to vt1 and wait until I see an [ Ok
] (I don't know which boot step prints this as it's the only thing on
vt1) and then switch to vt7 plymouth termi
If someone can reproduce this error (plymouth quit is running
indefinitely), please grab a backtrace of plymouthd with 'sudo gdb
plymouthd $pid_of_plymouthd'.
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Triaged
** Changed in: plymouth (Ubuntu)
Importance: Undecided => High
--
@Steve Langasek: in my case (see the ps.txt I attached to my report)
there definitely is a plymouth quit process.
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can reproduce this by simply touching the file '/forcefsck' and
rebooting.
Killing either 'plymouth quit' or 'plymouth --mode=boot --attach-to-
session' shows gdm again, all though kill 'plymouth --mode=boot
--attach-to-session' spams the terminal with the following message:
'mountall: Plymouth
> Killing '/bin/plymouth quit --retain-splash' shows the gdm login
screen.
Are you saying that there was a running 'plymouth quit' process that you
had to kill?
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member
Same issue. GDM starts, but you can't see the login screen (presumably
because plymouth hides gdm)
Killing '/bin/plymouth quit --retain-splash' shows the gdm login screen.
Plymouth's fsck screen never goes past seventy-something percent, even
though fsck has quit. I presume that's why it doesn'
** Changed in: plymouth (Ubuntu)
Status: New => Confirmed
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
I also had this issue. When killing plymouth, gdm starts normally
though.
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
No evidence that this is the same as bug #554519. Unduping.
** This bug is no longer a duplicate of bug 554519
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
and got stuck on "Checking disk 1 of 1 (71%)"
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.
*** This bug is a duplicate of bug 554519 ***
https://bugs.launchpad.net/bugs/554519
** This bug has been marked a duplicate of bug 554519
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
and got stuck on "Checking disk 1 of 1 (71%)"
--
Graphical bootstrap hangs
*** This bug is a duplicate of bug 554519 ***
https://bugs.launchpad.net/bugs/554519
Also, here is the boot log.
** Attachment added: "boot.log"
http://launchpadlibrarian.net/42996558/boot.log
--
Graphical bootstrap hangs on fsck
https://bugs.launchpad.net/bugs/554737
You received this b
*** This bug is a duplicate of bug 554519 ***
https://bugs.launchpad.net/bugs/554519
** Attachment added: "ps.txt"
http://launchpadlibrarian.net/42996460/ps.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/42995536/BootDmesg.txt
** Attachment added: "CurrentDmesg
22 matches
Mail list logo
