Description of problem: Problem occurred on boot immediately after upgrade to Fedora 28 Additional info: reporter: libreport-2.9.5 WARNING: CPU: 0 PID: 0 at arch/x86/kernel/cpu/mtrr/cleanup.c:978 mtrr_trim_uncached_memory+0x2d8/0x30d Modules linked in: CPU: 0 PID: 0 Comm: swapper Not tainted 4.18.11-200.fc28.i686 #1 Hardware name: Compaq Presario 061 P8656K-ABA S4000T NA230/Stingray , BIOS 3.28 08/27/2004 EIP: mtrr_trim_uncached_memory+0x2d8/0x30d Code: 84 72 fd ff ff 8b 7d c0 8b 75 bc 0f ac fe 14 c1 ef 14 57 56 68 58 1e e4 d6 e8 33 e6 47 ff 83 c4 0c 83 3d e0 fa 09 d7 00 75 02 <0f> 0b 68 e4 1b e4 d6 e8 1b e6 47 ff e8 ed a7 ff ff 58 c7 45 b4 01 EAX: 0000004a EBX: 00000000 ECX: 00000001 EDX: d713d5e8 ESI: 00000003 EDI: 00000000 EBP: d6f57f28 ESP: d6f57ec8 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00210046 CR0: 80050033 CR2: 00000000 CR3: 1712c000 CR4: 00000600 Call Trace: setup_arch+0x573/0xb52 ? vprintk_default+0x17/0x20 ? vprintk_func+0x33/0xba start_kernel+0x5c/0x4b7 ? early_idt_handler_common+0x44/0x44 i386_start_kernel+0x98/0x9c startup_32_smp+0x164/0x168 random: get_random_bytes called from print_oops_end_marker+0x2c/0x50 with crng_init=0 Potential duplicate: bug 1570170
Created attachment 1491527 [details] File: dmesg
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.20.5-100.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.