The v4.16.4 update contains 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.

How to install

sudo dnf upgrade --advisory=FEDORA-2018-e71875c4aa

This update has been submitted for testing by jcline.

2 years ago
User Icon laolux provided feedback 2 years ago
karma
User Icon shecks commented & provided feedback 2 years ago
karma

Both default and performance kernel regression tests passed on Intel i7-6850K, 64Gig RAM, ASUS RX560 GPU

User Icon ibims commented & provided feedback 2 years ago
karma

works well

User Icon nivag commented & provided feedback 2 years ago
karma

wfm: desktop 16GB Intel i7-3770 CPU, laptop 8GB Intel i5-2520M CPU Lenovo T420 (this only took only 9m42s, which is less than the 106 it took for 4.16.3) - all using the Mate Desktop Environment regression test passed

jforbes edited this update.

2 years ago
User Icon jag commented & provided feedback 2 years ago
karma

WFM, regression tests passed

i7-4790K , 32 GB RAM, Gigabyte GTX 970, Gigabyte Z97X, Fedora 27 + 4.16.4-200 -> Working fine.

karma: +1

User Icon gerhardw commented & provided feedback 2 years ago
karma

Missing the patch for the KVM problem as discussed in: FEDORA-2018-b6be90818d

and 4.16.5 has been released (also missing the KVM patch)

This update has been pushed to testing.

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

works for me

User Icon augenauf commented & provided feedback 2 years ago
karma

works for me.

Hi @gerhardw,

Missing the patch for the KVM problem as discussed in: FEDORA-2018-b6be90818d

Yes, I was concerned about pulling the patch in without a review from the KVM maintainers. It looks like it's now received some feedback and will need a bit of tweaking. I'm going to leave it out of the 4.16.5 build as well since it sounds like it may cause issues for nested virtualization. Hopefully it'll be resolved before 4.16.6. Sorry about that.

User Icon filiperosset commented & provided feedback 2 years ago
karma

no regressions noted

User Icon dimitrisk commented & provided feedback 2 years ago
karma

No regressions noticed, Thinkpad X250

User Icon jlmagee commented & provided feedback 2 years ago
karma

tested on Thinkpad P51 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz with 4.14.3-200 networking didn't work. Networking is fine on this 4.16.4-300 I don't appear to have a KVM problem either.

karma

Resume from suspend to memory works, but I have lots of "DMAR: [DMA Write] Request device [00:02.0] fault addr 1af36000 [fault reason 05] PTE Write access is not set. DMAR: DRHD: handling fault status reg 3.". 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]). It's HD 4000 from i7-3770.

Hi @ciupicri,

Can you file a bug with:

  • Whether it is a new regression in 4.16.4 (not present in the 4.16.3 kernel) or it is a new regression in 4.16 (not present in 4.15 kernels)

  • Whether or not the Rawhide kernel also exhibits this

  • The dmesg log

Thanks!

This update has been submitted for batched by jcline.

2 years ago

This update has been submitted for stable by jcline.

2 years ago

On my system (AMD A10-7800 Radeon R7, ASUSTeK A88XM-E), this kernel hangs during the boot process. It makes it this far:

[    2.326086] usb 3-2: New USB device found, idVendor=046d, idProduct=c24c
[    2.328038] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.328984] usb 3-2: Product: G400s Optical Gaming Mouse
[    2.329915] usb 3-2: Manufacturer: Logitech
[    2.338356] input: Logitech G400s Optical Gaming Mouse as /devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.0/0003:046D:C24C.0004/input/input4
[    2.340400] hid-generic 0003:046D:C24C.0004: input,hidraw3: USB HID v1.10 Mouse [Logitech G400s Optical Gaming Mouse] on usb-0000:00:12.0-2/input0
[    2.345363] hid-generic 0003:046D:C24C.0005: hiddev98,hidraw4: USB HID v1.10 Device [Logitech G400s Optical Gaming Mouse] on usb-0000:00:12.0-2/input1

According to the dmesg output from the previous kernel, 4.16.3-200.fc27.x86_64, the next lines should be:

[    2.386486] [drm] radeon kernel modesetting enabled.
[    2.387492] checking generic (e0000000 300000) vs hw (e0000000 10000000)
[    2.387493] fb: switching to radeondrmfb from EFI VGA
[    2.388569] Console: switching to colour dummy device 80x25
[    2.412982] [drm] initializing kernel modesetting (KAVERI 0x1002:0x130F 0x1043:0x85CB 0x00).
[    2.413020] [drm] doorbell mmio base: 0xF0000000
[    2.413023] [drm] doorbell mmio size: 8388608
[    2.413081] ATOM BIOS: 113
[    2.413128] radeon 0000:00:01.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
[    2.413132] radeon 0000:00:01.0: GTT: 2048M 0x0000000040000000 - 0x00000000BFFFFFFF
[    2.413137] [drm] Detected VRAM RAM=1024M, BAR=256M

…but 4.16.4-200.fc27.x86_64 never gets there.

If I type on the keyboard, letters appear on the screen, and I can Ctrl-Alt-Del to reboot. But otherwise, the kernel is hung.

It looks like there's a fairly bad regression for at least some percentage of AMD systems?

This update has been pushed to stable.

2 years ago

I opened BZ#1572944 (4.16.4-200.fc27.x86_64 hangs during boot on AMD system).

User Icon ozeszty commented & provided feedback 2 years ago
karma

I had no issues with Athlon II X2 260 with R7 240.


Please login to add feedback.

Metadata
Type
security
Karma
11
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
2 years ago
in testing
2 years ago
in stable
2 years ago
modified
2 years ago
BZ#1567306 CVE-2018-1108 kernel: drivers: getrandom(2) unblocks too early after system boot
0
0
BZ#1571036 Kernel updates breaks screen brightness keys
0
0
BZ#1572074 CVE-2018-1108 kernel: drivers: getrandom(2) unblocks too early after system boot [fedora-all]
0
0

Automated Test Results

Test Cases

0 0 Test Case kernel regression