Update for kernel-tmb 4.14.65.

It seems to have the same problem of kernel-tmb 4.14.62

BUT

I restarted with kernel 4.14.65 (no systemd-logind problem) and tried a "systemctl hibernate" which failed: pc hung on lock screen (known bug on samsung rc730)
I then restarted pc with "Ctrl+ALt+PrtScreen+R E I S U B" and chose kernel-tmb 4.14.65: everything was ok. No systemd-logind bug.
So, I tried a "systemctl hibernate" with kernel-tmb 4.14.65: everything went fine: pc stopped and I was able to resume correctly.
I restarted again with kernel-tmb 4.14.65 and here it was again:
systemd-logind failed with exit-code=1/FAILURE.
I restarted with kernel 4.14.65 and tried a system restart: I had a kernel panic (that was expected too) but when I forced a restart with kernel-tmb 4-14-65 everything was fine again...

SO
maybe it's something related to "systemctl hibernate"?
A broken restart FIXes it?
Maybe it's something related with samsung power management/samsung-tools (just like the "no /dev/video0" bug)?

Kernel 4.14.65 doesn't seem to be affected, nor kernel-tmb 4.14.44.

(In reply to Riccardo Poleggi from comment #1)

> 
> Kernel 4.14.65 doesn't seem to be affected, nor kernel-tmb 4.14.44.


Please reproduce the problem with kernel-tmb-4.14.65-1.mga6 and, after using the Magical keys (like you did before) to reboot, use an unaffected kernel, become root and run:

  journalctl -ab -1 > log.txt

and attach log.txt to this bug report

(Compress with xz if the file is too large to attach)


Assigning to the kernel maintainers and CC'ing the basesystem maintainers.

Assignee: bugsquad => kernel
Keywords: (none) => NEEDINFO
CC: (none) => basesystem, marja11

This is the same "slow boot" bug as another report...

The security fixes for random() not being random enough causes boot delays on some hw (and vm's) because of "missing" entropy data...

If you "type random garbage" during boot it will get enough random data to fulfill random entropy and fully init rnd fast enough...

CC: (none) => tmb

Created attachment 10328 [details]
"journalctl -ab -1 > log.txt" on samsung rc730

Here is the requested file.

However, the "type random garbage" workaround seems to work.

I was able to restart with kernel-tmb 4.14.65 after a "systemctl hibernate" typing "random garbage" at bootstrap.

And it seems also that even when there's no systemd-logind error, typing random garbage during boot time makes the process faster (that'd make sense to me...).

I only have "a stop" at "wait for network...." but I could figure out that it was related to samsung-tools: pressing "Fn+F9" to switch on wifi "unfreezes" it.

Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Status: NEW => RESOLVED
Resolution: (none) => OLD
CC: (none) => ouaurelien