yeah yestarday my computer don't boot with kernel-4.18.20 , after back to
kernel-core-4.18.19-100.fc27.x86_64, it resume to work perfectly .
Thanks for the tip .
It might be related with [1] ?
"I see that a 4.18.20-100.fc27 is already in koji, and unfortunately 4.18.xx is now
EOL.
May I suggest that f27 to get a new 4.18.20 build with the STIBP backport reverted
please? (Current 4.19.3-rc reverts that already.)"
[1]
https://bodhi.fedoraproject.org/updates/FEDORA-2018-b68776e5b0#comment-86...
On Sun, 2018-12-02 at 15:20 +0100, Reindl Harald wrote:
how does Fedora think to handle
https://bugzilla.kernel.org/show_bug.cgi?id=201685
4.18.20 is the last 4.18.x and happily at least 4.18.20 from F27 runs
fine on F28 systems but given that bug upgrade to 4.19.x seems to be
just a lottery with your data - on some or even many systems all
seems
to be fine BUT when you are affected and nobody until now knows the
root
cause
honestly the rebase to 4.19 was too fast to start with!
WHY did that rebase happen at all?
kernel-4.19.2-200.fc28 jcline 2018-11-15 01:34:18
bug reported: 2018-11-13 19:42:20 UTC
and yes i had that bugreport in my inbox just because i have
subscribed
to filesystem / raid related mailing lists and the word "crazy"
appeared
in my mind when i saw the rebase two days later because i expect that
downstream maintainers at least have the same lists subscribed
ordinary
users have
_______________________________________________
kernel mailing list -- kernel(a)lists.fedoraproject.org
To unsubscribe send an email to kernel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelin
es
List Archives:
https://lists.fedoraproject.org/archives/list/kernel@l
ists.fedoraproject.org --
Sérgio M. B.