This stable update contains important 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-3b24e8588b

This update has been submitted for testing by jcline.

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

works for me

Still seems to continue the old tradition of 4.19.x kernels not working on Atom servers (I think 4.19.4 and 4.19.5 are the only ones that boot for me, which is why I'm still running 4.19.5):

[    3.950318] host_name kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    4.063285] host_name kernel: ACPI: watchdog: Skipping WDAT on this system because it uses RTC SRAM
[    4.063394] host_name kernel: BUG: unable to handle kernel paging request at 000000030000000d
[    4.063411] host_name kernel: PGD 0 P4D 0
[    4.063418] host_name kernel: Oops: 0000 [#1] SMP PTI
[    4.063423] host_name kernel: CPU: 0 PID: 384 Comm: systemd-udevd Not tainted 4.19.8-300.fc29.x86_64 #1
[    4.063428] host_name kernel: Hardware name: Online Labs SR/SR, BIOS 00.00.00.0011 03/29/2016
[    4.063439] host_name kernel: RIP: 0010:acpi_ns_build_normalized_path+0x76/0x108
[    4.063444] host_name kernel: Code: 31 c0 48 85 ff 74 de 31 d2 49 89 f8 31 c0 4c 39 05 ff 5b 57 01 74 61 4c 39 c7 74 0e 39 c2 76 08 41 89 c1 42 c6 04 0e 2e ff c0 <45> 8b 48 0c 41 89 ca 44 89 4c 24 04 45 31 c9 46 8a 5c 0c 07 45 84
[    4.063451] host_name kernel: RSP: 0000:ffffb831c1eefa00 EFLAGS: 00010207
[    4.063456] host_name kernel: RAX: 000000000000000a RBX: 0000000000000001 RCX: 0000000000000001
[    4.063460] host_name kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9d4069e07ca8
[    4.063465] host_name kernel: RBP: 0000000000000000 R08: 0000000300000001 R09: fffffffffffffffc
[    4.063469] host_name kernel: R10: 0000000000000000 R11: 0000000000000040 R12: 0000000000000428
[    4.063473] host_name kernel: R13: ffff9d4069e07ca8 R14: ffff9d40696e5f88 R15: 0000000000000001
[    4.063478] host_name kernel: FS:  00007fbbd9c62940(0000) GS:ffff9d406fa00000(0000) knlGS:0000000000000000
[    4.063483] host_name kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    4.063487] host_name kernel: CR2: 000000030000000d CR3: 000000046bc3c000 CR4: 00000000001006f0
[    4.063491] host_name kernel: Call Trace:
[    4.063501] host_name kernel:  acpi_ns_get_normalized_pathname+0x1f/0x6d
[    4.063508] host_name kernel:  acpi_ut_check_address_range+0x8f/0x118
[    4.063514] host_name kernel:  acpi_check_address_range+0x40/0x59
[    4.063522] host_name kernel:  acpi_check_resource_conflict+0x3a/0x50
[    4.063533] host_name kernel:  lpc_ich_probe+0x26c/0x7ea [lpc_ich]
[    4.063540] host_name kernel:  local_pci_probe+0x41/0x90
[    4.063546] host_name kernel:  pci_device_probe+0x188/0x1a0
[    4.063553] host_name kernel:  really_probe+0x235/0x3a0
[    4.063560] host_name kernel:  driver_probe_device+0xb3/0xf0
[    4.063566] host_name kernel:  __driver_attach+0xdd/0x110
[    4.063571] host_name kernel:  ? driver_probe_device+0xf0/0xf0
[    4.063577] host_name kernel:  bus_for_each_dev+0x76/0xc0
[    4.063584] host_name kernel:  ? klist_add_tail+0x3b/0x60
[    4.063589] host_name kernel:  bus_add_driver+0x152/0x230
[    4.063594] host_name kernel:  ? 0xffffffffc044d000
[    4.063599] host_name kernel:  driver_register+0x6b/0xb0
[    4.063604] host_name kernel:  ? 0xffffffffc044d000
[    4.063610] host_name kernel:  do_one_initcall+0x46/0x1c3
[    4.063617] host_name kernel:  ? free_unref_page_commit+0x9b/0x110
[    4.063624] host_name kernel:  ? _cond_resched+0x15/0x30
[    4.063630] host_name kernel:  ? kmem_cache_alloc_trace+0x15f/0x1e0
[    4.063636] host_name kernel:  do_init_module+0x5a/0x210
[    4.063642] host_name kernel:  load_module+0x205d/0x22c0
[    4.063649] host_name kernel:  ? __do_sys_init_module+0x13d/0x180
[    4.063654] host_name kernel:  __do_sys_init_module+0x13d/0x180
[    4.063661] host_name kernel:  do_syscall_64+0x5b/0x160
[    4.063667] host_name kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[    4.063672] host_name kernel: RIP: 0033:0x7fbbda91d0ee
[    4.063678] host_name kernel: Code: 48 8b 0d 9d 1d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6a 1d 0c 00 f7 d8 64 89 01 48
[    4.063686] host_name kernel: RSP: 002b:00007ffe7b12f6a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[    4.063692] host_name kernel: RAX: ffffffffffffffda RBX: 00005625c7b4ac10 RCX: 00007fbbda91d0ee
[    4.063697] host_name kernel: RDX: 00007fbbdaa9384d RSI: 000000000000b746 RDI: 00005625c835e6e0
[    4.063701] host_name kernel: RBP: 00007fbbdaa9384d R08: 00005625c7b44180 R09: 0000000000000005
[    4.063706] host_name kernel: R10: 0000000000000006 R11: 0000000000000246 R12: 00005625c835e6e0
[    4.063711] host_name kernel: R13: 00005625c7b43a50 R14: 0000000000020000 R15: 0000000000000000
[    4.063716] host_name kernel: Modules linked in: i2c_ismt(+) lpc_ich(+) fjes(+) pcc_cpufreq(-) crc32c_intel
[    4.063728] host_name kernel: CR2: 000000030000000d
[    4.063734] host_name kernel: fbcon: Taking over console
[    4.063740] host_name kernel: ---[ end trace a1d8459f05c05555 ]---
[    4.085352] host_name kernel: RIP: 0010:acpi_ns_build_normalized_path+0x76/0x108
[    4.085366] host_name kernel: Code: 31 c0 48 85 ff 74 de 31 d2 49 89 f8 31 c0 4c 39 05 ff 5b 57 01 74 61 4c 39 c7 74 0e 39 c2 76 08 41 89 c1 42 c6 04 0e 2e ff c0 <45> 8b 48 0c 41 89 ca 44 89 4c 24 04 45 31 c9 46 8a 5c 0c 07 45 84
[    4.085375] host_name kernel: RSP: 0000:ffffb831c1eefa00 EFLAGS: 00010207
[    4.085380] host_name kernel: RAX: 000000000000000a RBX: 0000000000000001 RCX: 0000000000000001
[    4.085385] host_name kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9d4069e07ca8
[    4.085390] host_name kernel: RBP: 0000000000000000 R08: 0000000300000001 R09: fffffffffffffffc
[    4.085394] host_name kernel: R10: 0000000000000000 R11: 0000000000000040 R12: 0000000000000428
[    4.085399] host_name kernel: R13: ffff9d4069e07ca8 R14: ffff9d40696e5f88 R15: 0000000000000001
[    4.085404] host_name kernel: FS:  00007fbbd9c62940(0000) GS:ffff9d406fa00000(0000) knlGS:0000000000000000
[    4.085410] host_name kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    4.085414] host_name kernel: CR2: 000000030000000d CR3: 000000046bc3c000 CR4: 00000000001006f0
[    4.096755] host_name kernel: dca service started, version 1.12.1
[    4.134595] host_name kernel: igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[    4.134607] host_name kernel: igb: Copyright (c) 2007-2014 Intel Corporation.

And I'm not here to irritate people, so if you think this is an upstream issue please point me towards the correct upstream bug tracker.

Details of hardware: - Avoton Atom system - Intel(R) Atom(TM) CPU C2750 @ 2.40GHz

This update has been pushed to testing.

3 years ago
User Icon mmarusak provided feedback 3 years ago
karma
User Icon atim provided feedback 3 years ago
karma
User Icon markec commented & provided feedback 3 years ago
karma

Looks good on X260

User Icon bojan commented & provided feedback 3 years ago
karma

Works on T450s and XS35GTv2 (Atom CPU).

User Icon xvitaly commented & provided feedback 3 years ago
karma

WFM.

User Icon imabug provided feedback 3 years ago
karma
karma
User Icon g6avk commented & provided feedback 3 years ago
karma

Works for me.. The Default and Performance Regression tests pass OK.
AMD 965, x86_64 work station, Plasma DE, X-server, nVidia card GTX 650 (GK107) + nVidia RPM's from Negativo17.

User Icon nivag commented & provided feedback 3 years ago
karma

wfm: desktop 16GB Intel i7-3770 CPU, laptop 8GB Intel i5-2520M CPU Lenovo T420 - all using the Mate Desktop Environment (regression tests okay, apart from the laptop taking 106m9s, more than 10 times longer than for kernel-4.19.5-300.fc29 9m49s)

User Icon nivag commented & provided feedback 3 years ago
karma

wfm: desktop 16GB Intel i7-3770 CPU, laptop 8GB Intel i5-2520M CPU Lenovo T420 - all using the Mate Desktop Environment (regression tests okay, apart from the laptop taking 106m9s, more than 10 times longer than for the desktop 9m49s)

--- previously did a cut & paste with minimal checking! ;-(

Hi anonymous user,

And I'm not here to irritate people, so if you think this is an upstream issue please point me towards the correct upstream bug tracker.

To start with, please file a bug report on https://bugzilla.redhat.com/. It's almost certainly an upstream issue, but we can narrow down who to contact on the bug report.

This update has been submitted for batched by jcline.

3 years ago

Also, when you file the bug report, it would be helpful to know if the kernel at https://koji.fedoraproject.org/koji/taskinfo?taskID=31411873 resolves your issue or not. Thanks!

This update has been submitted for stable by jcline.

3 years ago

Does this contain the fix for the block layer data corruption bug described in https://lwn.net/Articles/774440/ and https://bugzilla.kernel.org/show_bug.cgi?id=201685 ?

Does this contain the fix for the block layer data corruption bug described in https://lwn.net/Articles/774440/ and https://bugzilla.kernel.org/show_bug.cgi?id=201685 ?

Yes

This update has been pushed to stable.

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

Fedora 4.19 kernels before 4.19.5 and after show an acpi crash for me on an old HP/compaq 6715b laptop with an AMD Turion. Same crash with 4.19.8, whereas 4.19.5 did work. Low and behold: the koji build https://koji.fedoraproject.org/koji/taskinfo?taskID=31411873 ("atomacpi") works, the kernel boots as usual. acpitool -c says:

CPU type : AMD Turion(tm) 64 X2 Mobile Technology TL-60 Min/Max frequency : 800/2000 MHz Current frequency : 800 MHz Frequency governor : ondemand Freq. scaling driver : powernow-k8 Cache size : 512 KB Bogomips : 3989.80 Bogomips : 3989.80 Function Show_CPU_Info : could not read directory /proc/acpi/processor/ Make sure your kernel has ACPI processor support enabled.

(addition to the previous comment: 4.19.3 worked as well, the 4.19. kernel before that did not)

User Icon nomos commented & provided feedback 3 years ago
karma

Tested on local machine with AMD Ryzen 5 2400G.

Fedora 4.19 kernels before 4.19.5 and after show an acpi crash for me on an old HP/compaq 6715b laptop with an AMD Turion. Same crash with 4.19.8, whereas 4.19.5 did work. Low and behold: the koji build https://koji.fedoraproject.org/koji/taskinfo?taskID=31411873 ("atomacpi") works, the kernel boots as usual.

Hi @mjg,

Thanks for testing that. Please file a bug in Bugzilla and include kernel logs from a crashed boot (journalctl --no-hostname -k -b <bootnumber>) so we can track this. Hopefully the anonymous commenter will also comment on that bug and verify if that kernel works for them.

User Icon ozeszty commented & provided feedback 3 years ago
karma

No regressions spotted.

https://bugzilla.redhat.com/show_bug.cgi?id=1659225 filed (@jcline let me know if you need more).

@mjg , thanks for making the bugzilla ticket.

@jcline , I can also verify that the atomacpi kernel does not panic on the Atom system I'm testing on.


Please login to add feedback.

Metadata
Type
bugfix
Karma
11
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

Automated Test Results

Test Cases

0 6 Test Case kernel regression