On Mon, 26 Sep 2011 11:43:52 -0400
Clyde E. Kunkel wrote:
> OK...was the problem the system would not shutdown in preparation to
> reboot, or was the problem the system tried to go thru the boot(-up)
> process and failed?
Well, since the screen went totally blank, and there was nothing
in the l
On 09/26/2011 10:11 AM, Tom Horsley wrote:
> On Mon, 26 Sep 2011 09:55:19 -0400
> Clyde E. Kunkel wrote:
>
>> I have seen this before after a systemd update. One time occurrence
>> usually.
>
> Judging from the normal messages I see on reboot, the code
> is trying to do some sort of "root pivot" t
On Mon, 26 Sep 2011 09:55:19 -0400
Clyde E. Kunkel wrote:
> I have seen this before after a systemd update. One time occurrence
> usually.
Judging from the normal messages I see on reboot, the code
is trying to do some sort of "root pivot" to swap in a
consistent set of files to run while killi
On Mon, Sep 26, 2011 at 8:34 AM, Tom Horsley wrote:
> I just applied latest f16 updates, had a whole bunch
> of files skipped due to dependency problems, but a
> vast number of updates applied OK.
>
> I then told system to reboot, the screen went totally
> black, and the reboot never happened.
>
>
On 09/26/2011 09:34 AM, Tom Horsley wrote:
> I just applied latest f16 updates, had a whole bunch
> of files skipped due to dependency problems, but a
> vast number of updates applied OK.
>
> I then told system to reboot, the screen went totally
> black, and the reboot never happened.
>
> The only
I just applied latest f16 updates, had a whole bunch
of files skipped due to dependency problems, but a
vast number of updates applied OK.
I then told system to reboot, the screen went totally
black, and the reboot never happened.
The only thing in the /var/log/messages file was the
normal entry
