The 4.17.4 stable kernel update contains a number of important updates across the tree.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2018-d82a45d9ab
Please log in to add feedback.
0 | 0 | Test Case kernel regression |
This update has been submitted for testing by jforbes.
This would be the third kernel update in a row that will not boot as a Xen dom0 or a PV domU, even though Fedora's kernel team has worked with the Xen developers per bug 1592976 and we now have two tiny patches which have been sent on to LKML that fix it and only touch the Xen portion of the tree. It would be great if they could be included.
wfm: desktop 16GB Intel i7-3770 CPU (performance test elapsed 9m37s), laptop 8GB Intel i5-2520M CPU Lenovo T420 (performance test elapsed 106m37s) - all using the Mate Desktop Environment, again the laptop took an excessive amount of time to perform the performance test!
seems to work on Intel i5-3550 CPU x86_64.
This update has been pushed to testing.
Works for me.. Regression tests pass OK.
x86_64 work station, Plasma DE, X-server, nVidia card GTX 650 (GK107) + nVidia RPM's from Negativo17.
Works here on T450s, XS35GTv2 and a VM.
No regressions noted on x86_64 Ivy Bridge and Haswell.
No regressions on T480s.
Works
Working on X1 Carbon 4th gen.
wfm on i7-5820K. no regressions noted.
The problem https://bugzilla.redhat.com/show_bug.cgi?id=1572944 is resolved at least in my case. Doesn't hang on boot like the previous 4.17-releases and I don't have to randomly hammer my keyboard anymore ;)
karma: +1
WFM on a Thinkpad X250
WFM on Thinkpad W530
No regression found on Lenovo E560, kernel test passed (except from paxtest as usual)
Seems OK on Vostro 3560.
Works for me. No regressions noted
Various regressions with USB kernel oops and heavy load kernel oops.
https://bugzilla.redhat.com/show_bug.cgi?id=1599101 https://bugzilla.redhat.com/show_bug.cgi?id=1598462
karma: -1
Also 4.17.5 is out ;)
Since I fully updated from updates-testing today I experienced two system hangs, when even sysrq was not working (and unfortunately nothing in the logs). I can't say it's the kernel's fault, but it's a likely candidate. Let's keep it in testing for a little longer.
Since there's not been a stampede of additional reports of system hangs I'm going to push this.
This update has been submitted for batched by jcline.
This update has been submitted for stable by jcline.
Booting on GCE properly. 4.17.3-200.fc28.x86_64 does not due to the crng init issue.
This update has been pushed to stable.