> 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 syste
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_DE
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 y
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.1
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 mu
> 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
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-
> 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 s
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 kern
> 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.fedoraprojec
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@
11 matches
Mail list logo