The 4.10.5 stable kernel update contains a number of important fixes across the tree.


The 4.10.4 stable kernel update contains a number of important fixes across the tree. It also reverts CONFIG_CFG80211_CRDA_SUPPORT to match the previous 4.9 kernels.


The 4.10.3 kernel rebase contains a number of new features, important fixes, and additional hardware support.

Reboot Required
After installing this update it is required that you reboot your system to ensure the changes supplied by this update are applied properly.

How to install

sudo dnf upgrade --advisory=FEDORA-2017-90aaa5bd24

This update has been submitted for testing by jforbes.

3 years ago

This update has obsoleted kernel-4.10.4-200.fc25, and has inherited its bugs and notes.

3 years ago
User Icon hreindl commented & provided feedback 3 years ago
karma

works for me and CRDA/hostapd are also fine again

User Icon dhgutteridge commented & provided feedback 3 years ago
karma

No regressions noted on x86_64 Ivy Bridge and i686 Diamondville.

User Icon jayjayjazz commented & provided feedback 3 years ago
karma

Works fine on x86_64.

User Icon psygnoser commented & provided feedback 3 years ago
karma

works ok. crda fixed.

BZ#1422247 Can't set crda with 4.10 kernel
User Icon xosevp commented & provided feedback 3 years ago
karma

It works flawlessly.

BZ#1422247 Can't set crda with 4.10 kernel
User Icon yuwata commented & provided feedback 3 years ago
karma

works for me and CRDA is fine

User Icon bradw commented & provided feedback 3 years ago
karma

Personal LAMP and mail server. All OK.

User Icon idosch provided feedback 3 years ago
karma

This update has been pushed to testing.

3 years ago
User Icon nivag commented & provided feedback 3 years ago
karma

wfm - desktop 32GB Intel i7-4770 CPU using the Mate Desktop Environment

User Icon g6avk commented & provided feedback 3 years ago
karma

Works for me, x86_64 work station.

User Icon greg18 commented & provided feedback 3 years ago
karma

works for me

BZ#1422247 Can't set crda with 4.10 kernel
BZ#1432430 CVE-2017-6874 kernel: Race condition in kernel/ucount.c [fedora-all]
BZ#1432429 CVE-2017-6874 kernel: Race condition in kernel/ucount.c
User Icon bojan commented & provided feedback 3 years ago
karma

Looks good here on x86_64 (T450s, Atom based server, VM).

User Icon cserpentis commented & provided feedback 3 years ago
karma

works for me

User Icon sassam commented & provided feedback 3 years ago
karma
  • Works for me on Thinkpad X220.
  • Regression tests passed.
User Icon wolnei commented & provided feedback 3 years ago
karma

No regressions noted.

User Icon lupinix commented & provided feedback 3 years ago
karma

Works fine with ThinkPad T450s

User Icon dimitrisk commented & provided feedback 3 years ago
karma

WFM, Thinkpad X250

User Icon anonymous commented & provided feedback 3 years ago

Look good to me on a dell M5510 I got some warning/error about ACPI but they were there with 4.9 kernel

karma: +1

User Icon hhlp commented & provided feedback 3 years ago
karma

LGTM, pass default and performance test

User Icon fcami commented & provided feedback 3 years ago
karma

breaks GDM on Radeon R7 250 reverting to 4.9.14-200 works

This update has been submitted for stable by jforbes.

3 years ago

This update has been pushed to stable.

3 years ago
User Icon jayjayjazz commented & provided feedback 3 years ago
karma

Works fine on x86_64.

User Icon anonymous commented & provided feedback 3 years ago

Kernel 4.10.5 won't boot. When I revert back to 4.9.14 everything boots fine. I use Nvidia 378.13, i think they are causing problems.

How can I compile and install nvidia drivers for the 10.5 core when I can't even boot into it. Seems Fedora struggle a lot with recent kernel upgrades and nvidia....

User Icon anonymous commented & provided feedback 3 years ago

Crashes on boot under qemu-kvm-2.7.1-4.fc24.x86_64 with cpu set to host-model. Previous kernel kernel-4.9.14-200 was working fine. It boots if i change cpu model to hypervisor-default.

User Icon pbrevig commented & provided feedback 3 years ago

My kernel was upgraded to 4.10.5-200.fc25.x86_64 this morning. Since then, I have received the following recurring syslogd error messages, all related to supposed hardware errors:

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: CPU 2: Machine Check: 0 Bank 128: 000000008802000b

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: TSC 7f538132a1

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: PROCESSOR 0:306a9 TIME 1490710022 SOCKET 0 APIC 2 microcode 1c

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: CPU 3: Machine Check: 0 Bank 128: 000000008802000b

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: TSC 7f538162d6

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: PROCESSOR 0:306a9 TIME 1490710022 SOCKET 0 APIC 3 microcode 1c

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: CPU 3: Machine Check: 0 Bank 128: 000000008804000a

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: TSC 7f53acb914

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: PROCESSOR 0:306a9 TIME 1490710022 SOCKET 0 APIC 3 microcode 1c

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: CPU 2: Machine Check: 0 Bank 128: 000000008804000a

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: TSC 7f53acc428

Message from syslogd@Bre at Mar 28 11:07:02 ... kernel:mce: [Hardware Error]: PROCESSOR 0:306a9 TIME 1490710022 SOCKET 0 APIC 2 microcode 1c

User Icon anonymous commented & provided feedback 3 years ago

dkms will not compile, and update nvidia 378.13 or 375.39. fences.h seems to be missing. even trying to build nvidia driver without dkms fails. 4.9.14 works, not 4.10.5

User Icon jforbes commented & provided feedback 3 years ago

http://rglinuxtech.com/ has some pointers to a patch for nvidia to get things working.

User Icon hreindl commented & provided feedback 3 years ago

@anonymous: that's the price you have to pay when you mix 3rd-party-blobs and a fast moving distribution - the same happens here for vmware workstation regulary but Fedora is never the point of contact for that issues - in your case rpmfusion and pray to god is and one soltuion would be not switch to the next Fedora release until the used one is EOL

User Icon anonymous commented & provided feedback 3 years ago

@hreindl, it was in the updates this morning. I had no reason to believe that dkms would puke, since all the 4.9 kernels updated 378.13 without problems. I did use the patch, and now running 4.10.5-200 with 378.13 and no issues so far.

User Icon hreindl commented & provided feedback 3 years ago

I had no reason to believe that dkms would puke

you had - 4.9.x != 4.10.x

when the first or second number in the version changes you have a new kernel generation which is supposed to break anything outside the upstream kernel tree (if not be happy but don't expect it)

User Icon leigh123linux commented & provided feedback 3 years ago
karma

@hreindl FYI rpmfusion drivers doesn't use dkms!

f25 rpmfusion nvidia driver have been patched for many weeks

https://pkgs.rpmfusion.org/cgit/nonfree/nvidia-kmod.git/commit/?h=f25&id=1168d85cdb210e26d2a9aff5970d249e1a328e41

User Icon hreindl commented & provided feedback 3 years ago

@leigh123linux well, when he even combines Fedora with a handcrafted nivida driver instead using the rpmfusion ones it's pretty much expected that this setup will break regulary after each kernel update - there are at least people which can and do apply patches if available - however, it's expected that 3rd party kernel modules are breaking by jumping from 4.9 to 4.10 and the same will hapen in a few months from 4.10 to 4.11


Please login to add feedback.

Metadata
Type
security
Karma
18
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
3 years ago
in testing
3 years ago
in stable
3 years ago
BZ#1422247 Can't set crda with 4.10 kernel
0
3
BZ#1432429 CVE-2017-6874 kernel: Race condition in kernel/ucount.c
0
1
BZ#1432430 CVE-2017-6874 kernel: Race condition in kernel/ucount.c [fedora-all]
0
1

Automated Test Results

Test Cases

0 5 Test Case kernel regression