I bodged up a test case for this by running the UEC image like this: kvm -monitor stdio -m 512 -kernel lucid-server-uec-i386-vmlinuz- virtual -append "root=/dev/sda" -hda lucid-server-uec-i386.img -boot c
What appears to be happening is: 1) Initially, I hadn't changed /etc/fstab to match the fact that the root image in my test happened to wind up on /dev/sda rather than /dev/sda1, so mountall stalled waiting for /dev/sda1 to appear which was never going to happen 2) After changing this, it still took a while for /dev/sda to appear for some reason, which exceeded mountall's boredom timeout 3) Either way, mountall asked plymouth to display a message along the lines of "The disk drive for / is not ready yet or not present" (or, in case 2, /tmp instead of /) 4) Because I'm booting without an initramfs, /dev/pts wasn't present before mountall ran and so plymouthd failed to attach to its session 5) This resulted in the details plugin's show_splash_screen method being called with boot_buffer == NULL: bam, segfault 6) Furthermore, in the process of investigating this, I found that plymouth:debug=file: doesn't work even if you hack around to make sure that it has a writable filesystem I'm attaching a few logs, respectively: * plymouth-debug.log: plymouth:debug output showing the failure to attach to a session, and trace output up to the subsequent segfault * plymouthd.trace: strace matching the above * mountall.log: mountall log output after adjusting /etc/fstab as above; note that I had to run 'mount -t devtmpfs -o mode=0755 none /dev || true' before running mountall in order to make sure that I had somewhere to write the log output, since I wasn't using an initramfs I'll also send patches upstream for 5 and 6. I think that we should consider an SRU for 5, since as far as I can tell this will break standard server boots without an initramfs. ** Attachment added: "plymouth-debug.log" http://launchpadlibrarian.net/45942715/plymouth-debug.log -- rm: cannot remove `/var/lib/urandom/random-seed': Read-only file system https://bugs.launchpad.net/bugs/567592 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.com/mailman/listinfo/ubuntu-bugs
