Hi,
I encountered a systemd bug during saving vmcore for kdump kernel.
I got the following message:
[ 60.283489] systemd[1]: Started Reload Configuration from the Real Root.
[ 60.290912] systemd[1]: Reached target Initrd File Systems.
[ 60.296162] systemd[1]: Reached target Initrd Default
On 11/05/2018 07:42 PM, Cristian RodrÃguez wrote:
>
>
> El 01-11-2018 a las 5:34, piliu escribió:
>
>> Any suggestion?
>>
>
> Yeah. Don't..if poweroff fails reboot will too..please attack the root
> cause of this problem.. why the machine fails t
On 11/01/2018 05:52 PM, Andrei Borzenkov wrote:
> On Thu, Nov 1, 2018 at 11:34 AM piliu wrote:
>>
>> Hi,
>>
>> I encounter an issue during the poweroff. In my bash script, firstly I
>> use poweroff cmd to start systemd-poweroff.service, and use reboot cmd
>
Hi,
I encounter an issue during the poweroff. In my bash script, firstly I
use poweroff cmd to start systemd-poweroff.service, and use reboot cmd
as a bake up if the poweroff fails. But during tests, many times, the
machine is rebooted directly, without waiting for the result of poweroff.
Since bo
When trying to interact with a emergency shell, this bug brights trouble
by dumping endless status message to console
On 12/25/2017 01:31 PM, piliu wrote:
> Hi,
>
> When debugging with a shell, manager_status_printf() always prints "A
> start job...". After tracing the syst
Hi,
When debugging with a shell, manager_status_printf() always prints "A
start job...". After tracing the systemd's code, I found in that
function, the cond "if (type == STATUS_TYPE_EPHEMERAL && m &&
m->n_on_console > 0)" does not meet.
With a debugging patch, I got the following message, which
