On 2018-07-02 23:04, John Andersen wrote:
On 07/02/2018 2:06 AM, Carlos E. R. wrote:
On 2018-07-02 09:48, Markus Egg wrote:
Am 01/07/18 um 07:40 schrieb David C. Rankin:
This is a kernel issue that appeared early in the 4.16.x set of releases and is also present in the 4.17 kernel for some hardware:
Hmm, but SuSE Leap 15 has a 4.12.14 kernel afaik. Is that kernel too old for that hardware?
The kernel version used by Leap is not that relevant, because it is heavily patched by SLE people. So maybe they backported something from a much more modern kernel that brought this in.
More likely they FAILED to backport some critical fix or hardware driver which was added in later kernels.
No, because previous kernels worked on his machine, obviously.
Hopefully the new Suse owners will straighten out this mindless backporting of patches to avoid re-certifying kernels for two customers.
Certainly not. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)