FEDORA-2017-14ad2c5d17

enhancement update in Fedora 26 for kernel

Status: obsolete

The 4.12.4 kernel rebase contains new features and a number of important bug fixes across the tree.

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.

Comments 35

This update has been submitted for testing by jforbes.

This update has been pushed to testing.

The 4.12 kernel does not seem to import UEFI keys to verify kernel modules anymore. In particular, the process described in [1] fails now, with the error

modprobe: ERROR: could not insert 'xxx': Required key not available

Looking at the output of keyctl, we see that only the kernel signing key has been added, but none of the UEFI ones:

# keyctl list %:.builtin_trusted_keys
1 key in keyring:
 88834290: ---lswrv     0     0 asymmetric: Fedora kernel signing key: fbae8ddf4ffd384e990097e7b82ddf7bacf91b23

Also, in dmesg the message changed from

EFI: Loaded cert 'xxx' linked to '.builtin_trusted_keys'

in 4.11.x, to

Loaded UEFI:db cert 'xxx' linked to secondary sys keyring

in 4.12.

[1] https://docs.fedoraproject.org/en-US/Fedora/26/html-single/System_Administrators_Guide/index.html#sect-signing-kernel-modules-for-secure-boot

critpath: -1
  1. Wayland graphics broken for QXL virtual video device: system hangs before reaching the graphical login screen. System boots correctly after adding "nomodeset" to the kernel boot options, likewise after removing kernel boot option "rhgb" and enabling "WaylandEnable=false" in configuration file /etc/gdm/custom.conf.
  2. System boot successfully on real hardware with video device ATI Radeon HD 3470.
karma: +1 critpath: +1

As per the previous comment, correct feedback was -1 for the last two list items, of course.

karma: -1 critpath: -1

QXL virt vga broken with Wayland

karma: -1

works for me

karma: +1

Works just fine on a T450s with Wayland session.

Not going to leave karma, because I see folks are having trouble. It boots for me on an Atom based server, T450s and a VM. I did see an i915 graphics related oops on the first reboot of T450s. This went away after cold boot. Also, both the laptop and the VM that are running gnome developed account manager related selinux denials.

UEFI Keys not imported : PKCS#7 signature not signed with a trusted key error

karma: -1

As previous comments (UEFI keys , Qxl) , -1 for the last items.

karma: -1 critpath: -1

HP 850 G4. i5-7200U w/integrated GPU, Gnome with Xorg, ipsec VPN. Generally working, not adding karma as of problems others see.

critpath: +1 kernel regression: +1

Fine on two systems with BIOS boot and KDE (no wayland), Core i3 540 with AMD GPU and AMD E-450 APU.

Had sudden boot fails on F26 with the i3 at early stage (also on 4.11), but went away when using a generic (not hardware tailored) initramfs.

karma: +1 critpath: +1

Works Fine on a E7470.

karma: +1

critpath: +1

Works for me on a i686 installation. Using a Dell e6220. Gnome on Wayland is working.

karma: +1

critpath: +1

Regression tests pass and boots fine, however I'm getting many selinux errors reported here:

https://bugzilla.redhat.com/show_bug.cgi?id=1476345

Someone should download GENUINE kernel from Linus and compile it. I see gap between 4.11 and 4.12 because labbott was doing all previous 4.11s but skipped 4.12 out of the blue (why?) and is currently doing 4.13. jforebes- do we trust him? Besides as is was said here: "Had sudden boot fails on F26 with the i3 at early stage (also on 4.11), but went away when using a generic (not hardware tailored) initramfs.". I got it too, ie. some boot failures/restart failures/boot black screen on 4.11.11-300.fc26.x86_64. Not stable at all. For the reason of signing keys and SELinux failures if I was able to downvote I would say: -10 (minus ten). Not good. Not good at all.

All is well for me. Headless Dell R520.

karma: +1 critpath: +1

@anonymous

You're joking, right? Otherwise do a little research about Fedora's kernel maintainers and kernel stabilization. A xx.yy.0...2 is hardly ever shipped (apart from rawhide).

And these boot failures in early stage are likely no kernel issue, but a dracut problem, as generic initramfs fixed it for me.

[Vote repeated, as it's deleted otherwise]

karma: +1 critpath: +1

The QXL issue is #1462381. (It's not specific to Fedora, I've reproduced it with the upstream kernel, and someone else has reported it against Debian 9 too.)

I haven't encountered any issues on bare metal, but giving negative karma because virtualization is significant for one of my workflows.

karma: -1 critpath: -1

"labbott was doing all previous 4.11s but skipped 4.12 out of the blue " This is perfectly normal. kernel 4.10 was maintained by jforbes, and for a long time, he and labbott take charges of the alternative kernels. And, if you take my opinion, they are doing an excellent job.

no regressions noted with Xfce on my clevo i7

karma: +1

Warning on boot:

[ 0.000000] ******** [ 0.000000] NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE [ 0.000000] [ 0.000000] trace_printk() being used. Allocating extra memory. [ 0.000000] [ 0.000000] This means that this is a DEBUG kernel and it is [ 0.000000] unsafe for production use. [ 0.000000] [ 0.000000] If you see this message and you are not debugging [ 0.000000] the kernel, report this immediately to your vendor! [ 0.000000] [ 0.000000] NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE [ 0.000000] ********

karma: -1

Changing feedback as I see the debug kernel warning too.

[    0.000000] **********************************************************
[    0.000000] **   NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE   **
[    0.000000] **                                                      **
[    0.000000] ** trace_printk() being used. Allocating extra memory.  **
[    0.000000] **                                                      **
[    0.000000] ** This means that this is a DEBUG kernel and it is     **
[    0.000000] ** unsafe for production use.                           **
[    0.000000] **                                                      **
[    0.000000] ** If you see this message and you are not debugging    **
[    0.000000] ** the kernel, report this immediately to your vendor!  **
[    0.000000] **                                                      **
[    0.000000] **   NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE   **
[    0.000000] **********************************************************
karma: -1 critpath: +1 kernel regression: +1

Regressions since 4.11.11: 1. [i915] if external display is connected via HDMI, console output (esp. prompt for LUKS password) is no longer displayed on it (only on internal LCD). 2. [usb] keyboard and mouse input (connected via Logitech Unifying receiver, USB ID 046d:c52b) becomes erratic, hanging every few seconds and making the machine almost unusable until I disable USB autosuspend for the receiver USB device in powertop (I have powertop.service enabled).

karma: -1 critpath: -1 kernel regression: +1

Buggiest kernel in a while

karma: +1 critpath: +1

Sorry, I'm used to giving postive karma, force of habit

karma: -1 critpath: -1

This update has been obsoleted.

Maybe we could have 4.11.12 on F26 meanwhile to be on par with F25 at least?

Does not boot: error: nouveau 0000:00:12.0: DDC responded, but no EDID for DP-1

critpath: -1

Touchpad resume issue fixed

#1431375: +1

Add Comment & Feedback

Please login to add feedback.

Content Type
RPM
Status
obsolete
Test Gating
Submitted by
Update Type
enhancement
Update Severity
unspecified
Karma
-4
stable threshold: 3
unstable threshold: -3
Autopush (karma)
Disabled
Autopush (time)
Disabled
Dates
submitted 2 years ago
in testing 2 years ago

Related Bugs 3

0+1 #1431375 Yoga 900 touchpad fails to resume
00 #1456722 kvm_stat adds python2 dependency
00 #1471302 4.12 renders mtx unable to manipulate a tape library

Automated Test Results

Test Cases

0+4 Test Case kernel regression