An update to this bug.
I haven't seen the hang described here since I upgraded GDM to the version
3.14.0-0ubuntu1.
It may or may not have anything to do with this.
However, this bug report may now be closed.
** Changed in: systemd (Ubuntu)
Status: Incomplete = Invalid
--
You received
That's the one thing I actually tried to install, but it didn't break
the initramfs in such a way. So I still don't know at all what's wrong
here :-(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Martin,
Well the GenuineIntel.bin may come from intel-microcode package of the Vivid
multiverse repository.
This is installed because of the Intel Core i7 Haswell processor.
My motherboard Asus Sabertooth has UEFI-BIOS and it is using UEFI Secure boot,
which may have something to do with this
Here is the attachment /boot/initrd.img-*
** Attachment added: initrd.img-3.16.0-24-generic
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+attachment/4258396/+files/initrd.img-3.16.0-24-generic
--
You received this bug notification because you are a member of Ubuntu
Touch
Martin,
The command cpio -tv /boot/initrd.img-3.16.0-24-generic did nothing.
Terminal just started a neverending process (but not getting stuck).
I did wait for several minutes.
The size of /boot/intitrd.img-3.16.0-24-generic is 19.2 Mb.
--
You received this bug notification because you are a
Argh, forgot a :
$ cpio -tv initrd.img-3.16.0-24-generic
drwxr-xr-x 2 root root0 Nov 10 17:05 kernel
drwxr-xr-x 2 root root0 Nov 10 17:05 kernel/x86
drwxr-xr-x 2 root root0 Nov 10 17:05 kernel/x86/microcode
-rw-r--r-- 1 root root
Martin,
My setup is fairly new, from September 2014.
I installed Ubuntu-Gnome Trusty then and upraded it first to Utopic and now to
Vivid dev.
I haven't mofified /etc/initramfs-tools/initramfs.conf in any way.
I attach this file here.
The folder /etc/initramfs-tools/conf.d/ is empty.
**
Martin,
I also attach the file /etc/intramfs-tools/update-initramfs-conf here.
** Attachment added: update-initramfs.conf
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+attachment/4257300/+files/update-initramfs.conf
--
You received this bug notification because you are a
OK, that looks fairly normal. And yet your initramfs is not at all
matching the expected form :-( Perhaps you can upload
/boot/initrd.img-3.16.0-24-generic somewhere where I can inspect it?
(It's about 30 MB). If not, then at least the output of
cpio -tv /boot/initrd.img-3.16.0-24-generic
Did you modify /etc/initramfs-tools/initramfs.conf in any way? Please
attach it here, and also any file in /etc/initramfs-tools/conf.d/
(normally there should be none).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Martin,
Here are the results.
1) gzip -cd /boot/initrd.img-3.16.0-24-generic | cpio -t | grep readlink
gzip: /boot/initrd.img-3.16.0-24-generic: not in gzip format
cpio: arkiston ennenaikainen loppu
(arkiston ennenaikainen loppu = the archiv ended prematurely)
2) after running sudo
Harry [2014-11-07 17:24 -]:
gzip: /boot/initrd.img-3.16.0-24-generic: not in gzip format
Le huh? Can you please give the output of
file /boot/initrd.img-3.16.0-24-generic
Thanks!
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) |
Here:
file /boot/initrd.img-3.16.0-24-generic
/boot/initrd.img-3.16.0-24-generic: ASCII cpio archive (SVR4 with no CRC)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Martin,
Here are the answers.
1) $ ls -l /sbin/init
Command not found
So, a little different. What is missing here?
2) Initramfs-tools v. 0.103ubuntu8
That is the latest one.
3) /boot/grub/grub.cfg
It is now attached.
** Attachment added: Grub.cfg
ok, these look good. Can you please check the output of
gzip -cd /boot/initrd.img-3.16.0-24-generic | cpio -t | grep readlink
it should be something like
150957 blocks
bin/readlink
If that's not there, then for some reason your initramfs is broken. Does
it change anything if you do
SysRQ
My keyboard does not apparently have that button.
http://www.logitech.com/en-gb/product/illuminated-keyboard-k740
So, at least trying Alt+Print Screen R+E+I+S+U+B does nothing, even after a
successful boot.
The hang
Yes, I now have only this in kernel line: quiet init=/lib/systemd/systemd
1) Why doesn't my setup boot at all, if I remove the kernel line
init=/lib/systemd/systemd ?
That's a good question, if you have systemd-sysv installed it should
work without it (that's how I boot my system).
$ ls -l /sbin/init
lrwxrwxrwx 1 root root 20 Nov 3 07:41 /sbin/init -
Yes, it's certainly a race condition of some sort. Unfortunately quite
impossible to debug remotely as there are no available logs/kernel
traces :-( SysRQ missing is also a bit unhelpful there (yes, it's
usually Alt+PrintScr); does that work if boot works normally? If it just
doesn't work with
Hi Martin,
True, I cannot switch between tty's. The whole system is unresponsive to
any keyboard commands.
About SysRQ (reisub): I cannot try it, because in my keyboard (Logitech K740)
there is no SysRQ button.
Usually it is the alt-function of the PrintScreen button, but not here.
About the
Martin,
In addition the previous post #8
I tried again booting without quiet in the kernel line: 10/10 boots were
successful.
Then with quiet: 3 out of 10 did hang.
Hanging (or crash) happens right after the fsck is done.
Mostly after sda1 fsck and before sdb1 fsck.
Sometimes both sda1 and
20 matches
Mail list logo
