[systemd-devel] systemd boot issue
Hello, Please see: -> http://fpaste.org/159783/ -> https://lists.fedoraproject.org/pipermail/devel/2014-September/202289.html I first encountered this issue with a custom built kernel-3.16, then in kernel-3.17 and now in 3.18 too. First issue here is that kernel boot-up halts after saying ... Starting Switch root. [3.031675] systemd-journald[948]: Received SIGTERM from PID 1 (systemd). And second, I've tried various systemd kernel parameters and to sift through systemd/journalctl logs, but can't find anything pointing at a real problem that halts the system. Others too have faced this issue before, -> https://lists.fedoraproject.org/pipermail/devel/2014-September/202274.html Does anyone here have a clue or suggestion? Thank you. --- Regards -P J P http://feedmug.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd boot issue
On 12/15/2014 11:45 AM, P J P wrote: I first encountered this issue with a custom built kernel-3.16, then in kernel-3.17 and now in 3.18 Do you encounter this with none custom built kernel in Fedora? JBG ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd boot issue
> On Monday, 15 December 2014 5:24 PM, Jóhann B. Guðmundsson wrote: > Do you encounter this with none custom built kernel in Fedora? I don't use the Fedora kernel, so I haven't seen it there. But as said earlier, Paul I guess encountered it with the Fedora kernel -> https://lists.fedoraproject.org/pipermail/devel/2014-September/202274.html --- Regards -P J P http://feedmug.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd boot issue
On 12/15/2014 12:02 PM, P J P wrote: On Monday, 15 December 2014 5:24 PM, Jóhann B. Guðmundsson wrote: Do you encounter this with none custom built kernel in Fedora? I don't use the Fedora kernel, so I haven't seen it there. But as said earlier, Paul I guess encountered it with the Fedora kernel -> https://lists.fedoraproject.org/pipermail/devel/2014-September/202274.html Start by Installing and trying the Fedora stock kernel to see if it happens there then report back here. JBG ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd boot issue
> On Monday, 15 December 2014 5:40 PM, Jóhann B. Guðmundsson wrote: > Start by Installing and trying the Fedora stock kernel to see if it > happens there then report back here. It does not happen there. Though IMO that's irrelevant. I left the VM with the custom 3.18.0 kernel in the stalled state since morning, -> http://fpaste.org/159783/ and now after 6-7 hours suddenly I see the login prompt with kernel-3.18.0. I have hit # shutdown -r now and boot-up has stalled at the same spot again. Let's see... --- Regards -P J P http://feedmug.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd boot issue
On 12/15/2014 12:32 PM, P J P wrote: It does not happen there. Though IMO that's irrelevant. It's not irrelevant since you might not be compiling your kernel without required config options which either break dracut or systemd. JBG ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd boot issue
> On Monday, 15 December 2014 6:43 PM, Jóhann B. Guðmundsson wrote: > It's not irrelevant since you might not be compiling your kernel without > required config options which either break dracut or systemd. Is there a known list of these options that a user must enable? --- Regards -P J P http://feedmug.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd boot issue
On 12/15/2014 03:15 PM, P J P wrote: On Monday, 15 December 2014 6:43 PM, Jóhann B. Guðmundsson wrote: It's not irrelevant since you might not be compiling your kernel without required config options which either break dracut or systemd. Is there a known list of these options that a user must enable? See the "Requirements" section in the readme file [1] 1. https://github.com/systemd/systemd/blob/master/README ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd boot issue
On Mon, 15.12.14 11:45, P J P (p...@fedoraproject.org) wrote: >Hello, > > Please see: > -> http://fpaste.org/159783/ > -> > https://lists.fedoraproject.org/pipermail/devel/2014-September/202289.html > > I first encountered this issue with a custom built kernel-3.16, > then in kernel-3.17 and now in 3.18 too. First issue here is that > kernel boot-up halts after saying > >... >Starting Switch root. >[3.031675] systemd-journald[948]: Received SIGTERM from PID 1 > (systemd). > > And second, I've tried various systemd kernel parameters and to sift > through systemd/journalctl logs, but can't find anything pointing at a real > problem that halts the system. Others too have faced this issue before, > > -> > https://lists.fedoraproject.org/pipermail/devel/2014-September/202274.html > > Does anyone here have a clue or suggestion? Can you boot with "systemd.log_level=debug systemd.log_target=kmsg"? This should print all logs to the console. Most likely there's some necessary kernel option not enabled in your custom kernel. Check that you have enabled everything listed in README. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd boot issue
Hi, > On Monday, 15 December 2014 9:23 PM, Lennart Poettering wrote: > Can you boot with "systemd.log_level=debug systemd.log_target=kmsg"? > This should print all logs to the console. Yes done! -> http://fpaste.org/159929/ > Most likely there's some necessary kernel option not enabled in your > custom kernel. Check that you have enabled everything listed in README. Yes, all of those options are duly set, except 'CONFIG_SCHED_DEBUG'; And CONFIG_UEVENT_HELPER_PATH was set to "/sbin/hotplug"; Both seem fairly innocuous. -> http://fpaste.org/159938/ Even after setting these two configuration options, system boot halts at the same spot as earlier. The fpaste link above is after setting above two configuration options. --- Regards -P J P http://feedmug.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd boot issue
Hi, > On Monday, 15 December 2014 10:54 PM, P J P wrote: > and now after 6-7 hours suddenly I see the login prompt with kernel-3.18.0. I > have hit ># shutdown -r now >and boot-up has stalled at the same spot again. Let's see... On a VM I had enabled 'CONFIG_LOCKUP_DETECTOR=y' & 'CONFIG_DETECT_HUNG_TASK=y' to detect hung tasks and to panic on hard or soft kernel lock-ups. After a while it did panic with a hung task trace. > -> http://fpaste.org/159929/ > -> http://fpaste.org/159938/ > > Even after setting these two configuration options, system boot halts at the > same spot as earlier. The fpaste link above is after setting above two > configuration options. On another machine that I left over night, it says - Failed to load SELinux policy. Freezing. === ... Starting Switch Root... [ 4.615752] systemd[1]: Switching root. [ 4.632717] systemd-journald[126]: Received SIGTERM from PID 1 (systemd). [ 5.296874] audit: type=1404 audit(1418662423.615:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 [ 302.048179] kworker/dying (32) used greatest stack depth: 12976 bytes left [13112.020686] systemd[1]: Failed to load SELinux policy. Freezing. === I've restarted it with - systemd.log_level=debug systemd.log_target=kmsg enforcing=0. Is there a way to see what systemd(1) is doing after it says - Starting Switch Root... - ? --- Regards -P J P http://feedmug.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd boot issue
> On Tuesday, 16 December 2014 10:41 AM, P J P wrote: >> and now after 6-7 hours suddenly I see the login prompt with kernel-3.18.0. >> I have hit >> # shutdown -r now >> and boot-up has stalled at the same spot again. Let's see... > > I've restarted it with >- systemd.log_level=debug systemd.log_target=kmsg enforcing=0. It is reproducible. With the above parameters the VM hangs for long at - Starting Switch Root... - But eventually continues to boot and show the login prompt after > 3 hours. -> http://fpaste.org/160132/ [13494.227608] systemd[1]: Startup finished in 2.039s (kernel) + 3.288s (initrd) + 3h 44min 48.899s (userspace) = 3h 44min 54.227s. systemd(1) is is taking 3:44 hours it seems. Another glitch is network.service fails to come up. :( - Is there a way to see why/where is it spending 3 hours? - Could enforcing=0 be a clue to maybe something is up with SELinux? Any suggestions would be helpful. --- Regards -P J P http://feedmug.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
