Rebase to the v5.1 kernel series
This contains enhancements and bug fixes across the tree
sudo dnf upgrade --advisory=FEDORA-2019-e96e0ce38b
This update has been submitted for testing by jcline.
This update has obsoleted kernel-5.0.17-300.fc30, and has inherited its bugs and notes.
works stable. / i7-6700K @ 4400 overclocked,ASRock Z170 Extreme4,nvidia 430.14/
No regressions noted.
Works for me..
Default and Performance tests pass OK. AMD 965, x86_64 work station, Plasma DE, X-server, nVidia card GTX 650 (GK107) + nVidia RPM's from Negativo17.
This update has been pushed to testing.
Does this contain a fix for the fstrim dataloss (context)? I don't see a revert the faulty commit (like for example arch linux did) or is Fedora not affected?
doesn't seem to like the integrated GPU in my laptop. Getting screen freezes with
i915 0000:00:02.0: Resetting chip for hang on rcs0
messages showing up in dmesg, which didn't happen with the 5.0.x kernels. Will investigate further and see if I can get enough to file a bug report
Asus X75A laptop, Intel i5-3230M
Works here, but that fstrim think makes me a bit worried, so no karma.
Works fine on T470s
Someone need to check if fstrim patch included to this build. If not, this update must be unpushed.
Had an oops on T450s, so -1.
no regressions noted
LGTM but what about this fstrim patch?
This update has been unpushed.
The fstrim patch is queued up for 5.1.5 so unless that gets delayed it'll be available in updates-testing in the next day or two.
BTW, the Oops-es I had were RPC/NFS related (which have been reported). Worth noting that nfs-utils package was also released in the same cohort and I -1-ed that too, because reverting back to previous nfs-utils immediately made NFS work. But, maybe there is something in 5.1.4 that is causing it to Oops on RPC/NFS related calls.
This kernel fixed the Bluetooth connectivity issues from 5.0.16 onward. Shame that it's flawed in other ways.
jcline edited this update.
Karma has been reset.
seems to look ok so far. no problems yet with the laptop that was giving me errors under 5.1.4
Works on T450s and XS35GTv2. But, with nfs-utils 2.3.4 on both the client and server side, kernel produces and Oops, just like 5.1.4. The new Oops has been reported. So, not leaving karma. Will keep an eye on things and report back if something else breaks. At least that fstrim problem is not there any more. :-)
Works OK here
Working fine, and as noted previously the bluetooth issues in 5.0.16+ are fixed. Ryzen 2200G + amdgpu.
Works for me
Tested on a variety of ARMv7/aarch64 including Cubietruck, Panda-ES, OrangePi PC, Wandboard, Mustang, Jetson-TX1, Pine64, Rock960, udoo-neo, BBone Black, DB410c, and numerous combinations of the Raspberry Pi.
works for me on a T480s
works well for me
works for me, X1 gen 4
Works great! LGTM! =)
Both the default and performance kernel tests passed. Intel i7-6850K, ASUS X99 MB, 64G RAM, RX 590 GPU
seems to work ok for me on Intel i5-3550 with prop. nvidia-driver from rpmfusion and VirtualBox 6.0.8 from Oracle.
5.1.5 works well on my Lenovo T460p
Looks okay on X260 as well; good to stable? ;)
Working fine on an i7-6770HQ. Regression tests pass
as an addition for my comment above: it works well with my Lenovo T420 with Intel-Graphics and Intel Core i5-2520M.
Ryzen 1700x @ overclocked + rx560. Amdgpu. X-server.
After my initial testing, I ran in to a kernel splat when running a kvm guest on an i5-6260U. It appears to be the one described here:
I think the patch he's saying was picked up for the mainline kernel was this one:
but it hasn't been merged yet (either by Linus or in the stable tree)
5.1.5 has run normally. The default tests passed or skipped.
No regression noted
All is well on two different intel servers.
This update has been submitted for stable by jcline.
This update has been pushed to stable.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.