Kernel 3.11.2-201 rebooting issue (or systemd?)

[Frantisek Hanzlik]

linuxnutster at videotron.ca wrote:
> On 10/02/2013 09:53 PM, Frank wrote:
>> On 02/10/13 07:28 PM, John Schmitt wrote:
>>> On Wed, Oct 02, 2013 at 08:55:50AM -0400, linuxnutster at videotron.ca
>>> wrote:
>>>> I just installed the latest kernel, and subsequently the latest
>>>> akmod-nvidia drivers from testing. Whenever I boot into XFCE and
>>>> then choose to reboot, it goes to a black screen which says
>>>> "rebooting," but it hangs there.
>>>>
>>>> If anybody can point me to a fix...thanks ahead of time...
>>
>>
>>     I have been having a similar problem for the past few weeks....
>> I posted about it a few days ago but got no replies.
>> I can reboot from the lightdm greeter...but any attempt to reboot
>> from within a window manager or DE results in a black screen with
>> "rebooting" at the top.
>>
>>
>>> If it's not this:
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1007607
>>>
>>> then file a new bug.
>>    It all started apparently with this kernel.
>>
>>    3.11.1-200.fc19.i686 #1 SMP Sat Sep 14 15:30:55 UTC 2013
>>
>>
>>
> 
> This is exactly what it does in my case, but strangely enough, only on one
> of my machines - two others are fine; however, in my case it started with
> kernel 3.11.2-201.fc19.x86_64

IMO this is rather systemd issue than kernel. When systemd arrived
in Fedora, I have steadily lots of issues with this - sometimes
system will not do shutdown (stay in phase when display something as
"power-off target reached" but computer isn't switched off), sometimes
will not reboot (it stop in stage as before when doing shutdown - very
amusing when it is remotely managed machine), sometimes system will
not boot correctly and stay in stage when GUI nor CLI not accessible
and only option is switch system off.
And there are other somtimes important systemd issues, as impossibility
to cleanly switch between different targets (e.g. graphical or
multi-user to rescue and back) and so on.
And this status is after three years when systemd is implicit init
in distro, and after that in the name of big, excellent systemd was
done lot of compromises at other Linux system places!
Maybe systemd will someday working satisfyingly, but its't actual
implementation is rather a tragedy.
With SYSV init or upstart was not these problems there.

Franta Hanzlik