Yeah, I was in hurry and didn't have the time to give you the reason why I did this.
I sent the latest apport from a kernel with which I don't experience the issue. The difference is that I see these messages: [ 5.527952] bio: create slab <bio-1> at 1 [ 151.415509] bio: create slab <bio-2> at 2 [ 161.717873] bio: create slab <bio-3> at 3 [ 162.277013] bio: create slab <bio-4> at 4 When the last of these appears, boot immediately continues correctly. Not sure if it's of any relevance. Anyway, today I've tried the following mainline kernels: 3.13.0-031300 3.14.0-031400 3.15.0-031500 3.16.0-031600 What surprised me is that even with 3.13.0-031300 I experienced the problem. I'm kind of confused now. I'll continue investigation tomorrow. I will do kernel bisection as you requested, but first I'd like to make sure the problem is not with initrd-s. I don't know what to do if it turns out my initrd-s are the culprits. The only working kernel I have (vmlinuz-3.13.0-37-generic) has its initrd generated from the old Trusty times. It seems every initrd I generate with any new installed kernel with Utopic, has the problem. I won't send more apports, sorry for the inconvenience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396213 Title: LVM VG is not activated during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396213/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
