The 4.15.7 update contains a number of important fixes 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-1eb9af6691Please login to add feedback.
| 0 | 0 | Test Case kernel regression |
This update has been submitted for testing by labbott.
LGTM, x86_64, i3-2350M
Works for me. Some earlier update (probably kernel-related) broke network after suspend, and intermittent suspend problems because of gam_server refusing to sleep, but I don't know where it came from and it's gone now.
Works for me.. Regression tests pass OK.
x86_64 work station, Plasma DE, X-server, nVidia card GTX 650 (GK107) /nouveau
wfm: desktop 16GB Intel i7-3770 CPU, laptop 16GB Intel i7-3610QM CPU, laptop 8GB Intel i5-2520M CPU Lenovo T420 - all using the Mate Desktop Environment (regressions tests past -- but both laptops took excessive tome to complete the performance, over an hour)
works for on Intel i5-3550 and Intel i5-2520M CPU Lenovo T420
works for me
I'll test this when it hits testing repos ;)
This update has been pushed to testing.
No regressions here.
LGTM. No regressions detected.
WFM, Thinkpad X250
Still not booting on docking station with Lenovo X260
https://bugzilla.redhat.com/show_bug.cgi?id=1549042
everything works as before.
Works on T470s
Doesn't boot on T470 when docked.
Works fine, no regression noticed, paxtest failed on Lenovo E560
Doesn't boot on HP Elitebook 820 G2 when docked.
no regressions noted
Any 4.15.X doesn't boot on T470 when 'docked'
4.14.X boots fine
works for me fine on T450s, docker or undocked.
No regression noted
no issues with Thinkpad T450s
Working fine on an X1 Carbon 4th gen and Xeon D 1520.
This update has been submitted for batched by labbott.
This update has been submitted for stable by labbott.
No regressions noted.
Why is this submitted to stable? A few people have reported docked laptops not booting. This has been happening for the most of 4.15.x branch. How is that stable?
I agree, it's not stable but it's not a regression - so it's not making things worse compared to 4.15.6, right?
On my two Intel workstations, this kernel works just fine. Thumbs up!
It's not making things worse compared to 4.15.6 because that kernel had exactly the same issue.
Yeah, it's the same for all 4.15.x kernels...
because 4.15.x is already out there, so 4.15.7 is not a regression at all
"A few people have reported docked laptops not booting" is sad, but they can boot with a older kernel anyways i for my self currently run 45 Fedora 26/27 instances (servers, vms, workstations) with 4.15 and no single issue should Fedora hold back 4.15 for a unknown amount of time because a few machines which can hold it back on their own?
It was already escalated upstream and needs some resources on it. But it's is fair point this is a breaking change since 4.14.18 ;) Perhaps it should stay in
testinguntil resolved and anybody who wants new kernel can pull it off that repo until then?Fixes BZ#1553448
karma: +1
Works for me. No regression. And it fixed this issue on sshuttle.
I'm on a Dell Inspiron 5557:
Oh, i'm using bumblebee with NVIDIA propietary driver from negativo17.
karma: +1
Unlike 4.15.6 this one works with haproxy again.
This update has been pushed to stable.