I have lvm2-2.02.97 plus udev-189 plus systemd-188. Everything works fine and it also worked fine with lower versions of lvm2 and udev. However, when I try to update systemd to any version higher than 188 (which is not in the tree anymore for quite a while) the boot process freezes when LVM is started. Fortunately I can recover from a previous backup which has systemd-188.
Created attachment 324562 [details] emerge --info emerge --info attached
What are the last dozen messages you see at boot time? Can you get to a recovery console of sorts? Can you provide a dump of the dmesg output up to that point?
(In reply to comment #2) > What are the last dozen messages you see at boot time? Can you get to a > recovery console of sorts? Can you provide a dump of the dmesg output up to > that point? Can't do anything that you asked: systemd-191 fails to build, while systemd-190 builds OK, but it segfaults (first line of message on boot). For now I switched back to openrc. I will build any new systemd that gets into the tree and will try to do what you asked.
(In reply to comment #3) > (In reply to comment #2) > > What are the last dozen messages you see at boot time? Can you get to a > > recovery console of sorts? Can you provide a dump of the dmesg output up to > > that point? > > Can't do anything that you asked: systemd-191 fails to build, while > systemd-190 builds OK, but it segfaults (first line of message on boot). > > For now I switched back to openrc. I will build any new systemd that gets > into the tree and will try to do what you asked.
Ar, stupid bugzie. (In reply to comment #3) > (In reply to comment #2) > > What are the last dozen messages you see at boot time? Can you get to a > > recovery console of sorts? Can you provide a dump of the dmesg output up to > > that point? > > Can't do anything that you asked: systemd-191 fails to build, while > systemd-190 builds OK, but it segfaults (first line of message on boot). > > For now I switched back to openrc. I will build any new systemd that gets > into the tree and will try to do what you asked. Please try -191 now that I fixed the build failure. Sorry for the inconvenience.
(In reply to comment #5) > Ar, stupid bugzie. > Please try -191 now that I fixed the build failure. Sorry for the > inconvenience. systemd 191 builds now, but segfaults like 190. 188 without any revs was the one worked. The 2 lines on the boot screen look like this: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details. segfault at 7d ip 45855717 sp bfe70518 error 4 in libc-2.15.so
(In reply to comment #6) > (In reply to comment #5) > > Ar, stupid bugzie. > > Please try -191 now that I fixed the build failure. Sorry for the > > inconvenience. > > systemd 191 builds now, but segfaults like 190. > 188 without any revs was the one worked. > The 2 lines on the boot screen look like this: > > Cannot add dependency job for unit display-manager.service, ignoring: Unit > display-manager.service failed to load: No such file or directory. See > system logs and 'systemctl status display-manager.service' for details. > > segfault at 7d ip 45855717 sp bfe70518 error 4 in libc-2.15.so I'm afraid you'd have to go upstream with that segfault. The display-manager lines are probably irrelevant but you can link your display manager unit to /etc/systemd/system/display-manager.service to check. $ ls -l /etc/systemd/system/display-manager.service lrwxrwxrwx 1 root root 35 sie 20 23:19 /etc/systemd/system/display-manager.service -> /usr/lib/systemd/system/xdm.service
(In reply to comment #7) > I'm afraid you'd have to go upstream with that segfault. In so many years of using Gentoo I learned that if you have a little bit of patience, something that doesn't work today will work next week or next month. So, for now, I'm back to openrc.
(In reply to comment #8) > (In reply to comment #7) > > I'm afraid you'd have to go upstream with that segfault. > > In so many years of using Gentoo I learned that if you have a little bit of > patience, something that doesn't work today will work next week or next > month. > So, for now, I'm back to openrc. Sadly, in systemd it usually works the other way ;). They first break something, then break more, and then say you're doing everything wrong :P.
(In reply to comment #8) > (In reply to comment #7) > > I'm afraid you'd have to go upstream with that segfault. > > In so many years of using Gentoo I learned that if you have a little bit of > patience, something that doesn't work today will work next week or next > month. > So, for now, I'm back to openrc. Please try -191-r1. That patch fixes some segfault, maybe it's yours as well.
(In reply to comment #10) > (In reply to comment #8) > > (In reply to comment #7) > > > I'm afraid you'd have to go upstream with that segfault. > > > > In so many years of using Gentoo I learned that if you have a little bit of > > patience, something that doesn't work today will work next week or next > > month. > > So, for now, I'm back to openrc. > > Please try -191-r1. That patch fixes some segfault, maybe it's yours as well. Problem fixed, I've built systemd-192 and lvm now starts! I think we can close this bug now!
