The 5.6.7 stable kernel update contains a number of important fixes across the tree.
sudo dnf upgrade --advisory=FEDORA-2020-64c805f706
This update has been submitted for testing by jforbes.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
works for me: desktop 16GB Intel i7-3770 CPU
& laptop 8GB Intel i5-2520M CPU Lenovo T420
(the desktop ran the performance test in under 10 minutes, but the laptop took about 123 (usually about 108) minutes -- more than 12 times longer!) - all using the Mate Desktop Environment
This update has been pushed to testing.
For whatever reason, can't get these installed. Enabling singular or full testing still shows dnf wanting to install 5.6.6 instead. This is a production system so I won't risk quickly losing two working kernels trying to figure out why.
Downloading the rpm's seems to have some sort of dependency conflict for me as well that I haven't seen before.
Pointing that out since 5.6.6 won't boot so I can't test this one.
This update can be pushed to stable now if the maintainer wishes
One of those days lol. Did nothing and later it just showed up.
Still won't boot same as 5.6.6. AMD Ryzen, Nvidia.
Système: Fedora 31 (x86_64) ~ workstation (KDE) Processeur: Intel I5-7300HQ (4) @ 3.500GHz, RAM: 8 GB, SSD: 256 GB (samsung), HDD: 1 TB (hitachi), Graphique: Optimus ~ HD Graphics 630 (Intel ) + 1050 TI - GP107M ( Nvidia ), Son: HD HD Audio (Intel), Réseau: RJ45 (Qualcomm), Wifi (Intel), usb: V3, V2 (Intel)
No regressions. ThinkPad T495, Ryzen 3700U/Vega graphics, GNOME/Wayland.
Works. GNOME on Wayland (CPU: Intel Xeon E5-2650 v2, GPU: Radeon RX 580 Series; SSD Plextor PX-128M6S).
Ran default and performance tests, and daily workflow is going well
So it might be hanging on "init script for live image" whatever that is since its not a live usb or being installed from live image. A search for me just shows 2011 stuff that I didn't bother to look at currently.
Boots but resuming from suspend is broken (system freeze after screen comes back). Intel Haswell laptop.
This update has been submitted for stable by jforbes.
aarch64 and x86_64
This update has been pushed to stable.
Some technical troubleshooting shows that this boots for me when using Nouveau. The proprietary Nvidia Vulkan kernel mod is failing to complete on anything 5.6.6+. I have Fedora Vanilla kernel 5.7.0 installed right now and it has the same problem.
To work around the issue with current kernels, one must uninstall Nvidia proprietary and de-blacklist Nouveau for it to boot.
It can be done when stuck at boot of this kernel by pressing ALT-F2 then using "$ sudo bash <nvidia.run file> --uninstall". Then "$ reboot" and pressing e to edit the kernel line to remove the blacklist.
I don't know if this should be considered a kernel regression or if the kernel devs are making Nvidia fix it or what is going on there. And also have yet to look up anything. Just posting this as a note.
Nvidia Vulkan proprietary is broken here. Thank you.
After installing this and rebooting I'm getting horrible screen flickering on some GUI elements, like popup menus and when scrolling in firefox. I'm using KDE plasma and kwin_x11 and I don't know if it's actually caused by this update,it could be something else.
Unsure if related, but it seems to me that something is breaking something in wine.
After installing this kernel and rebooting I am no longer able to launch World of Warcraft Retail from the wine-installed battle.net launcher, while WoW Classic still works (and the launcher obviously still starts, too). No combination of un-/reinstall, uninstall with complete application data purge and following reinstall or uninstall with complete wine prefix purge changes a thing.
Running WoW.exe manually with WINEDEBUG set yields this error:
*** stack smashing detected ***: <unknown> terminated
5697.162:0164:010e:err:seh:setup_exception nested exception on signal stack in thread 010e eip 00007f24b5649625 esp 00007fffffeab660 stack 0x132000-0x230000
Which led me to this (old) bug report from mid 2014. Tried to debug further but tbh I have no clue what the WINEDEBUG output would mean. Full output of manual WoW.exe start can be found here.
I am pretty sure it is not directly caused by the last update to my installed wine packages (wine-alsa, wine-alsa, wine-arial-fonts, wine-capi, wine-capi, wine-cms, wine-cms, wine-common, wine-core, wine-core, wine-courier-fonts, wine-desktop, wine-filesystem, wine-fixedsys-fonts, wine-fonts, wine-ldap, wine-ldap, wine-marlett-fonts, wine-ms-sans-serif-fonts, wine-openal, wine-openal, wine-opencl, wine-opencl, wine-pulseaudio, wine-pulseaudio, wine-small-fonts, wine-symbol-fonts, wine-system-fonts, wine-systemd, wine-tahoma-fonts, wine-times-new-roman-fonts, wine-twain, wine-twain, wine-wingdings-fonts, upgraded to v5.6-1.fc31 at ~2020-04-24 02:45 CET), and a little unsure if any update to the game client might be responsible, since it worked until at least 2020-04-30 03:00 CET, at which point I installed the v 5.6.7-200.fc31 updates to affected kernel packages on my system (kernel, kernel-core, kernel-devel, kernel-modules, kernel-modules-extra, kernel-headers) and powered the system off.
After booting today, described behaviour occurred.
The machine was definitely rebooted after game server maintenance (~2020-04-29 03:00 CET) and the game still worked, too, but I don't know if game client updates are tied to that procedure in any way (although I would expect at least an approximate temporal link since that's the time when new software is deployed to the game servers, so if a client update is required it would either have to already be updated or install the update ASAP).
Running FC31, kernel 5.6.7-200.fc31.x86_64, GNOME on Wayland, wine v5.6-1.fc31 on a Lenovo ThinkPad T495.
I'm unsure on where to search for further information on how or if the kernel update is related to this, feel free to name any required info.
Well, nevermind, this is unrelated. Problem also occurs when running previously installed 5.5.17-200.fc31 and 5.6.6-200.fc31 kernels which definitely worked before. Since it worked after the last wine update it's probably some bug in the launcher or WoW.exe.
" it's probably some bug in the launcher or WoW.exe."
While its not the place for Wine or Wow problems, yes the recent update to Wow has caused a problem. You need a newer version of Wine to fix this. It is NOT kernel related.
*the launcher (not Wow).
Fails to boot. ( stocks on Lenovo Logs ) Lenovo Exterme X1 gen 2 Intel® Core™ i7-9750H CPU @ 2.60GHz GeForce GTX 1650 with Max-Q Design/PCIe/SSE2 ( Hybrid with Intel® UHD Graphics 630 )
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.