Description of problem: I see the message "BUG: unable to handle kernel paging request at xxxx" and get a kernel panic. Version-Release number of selected component (if applicable): Linux kernels 4.11.3-200.fc25.x86_64 and 4.11.3.202.fc25.x86_64. How reproducible: 100% of the time. Steps to Reproduce: Boot into either of the above kernels. Actual results: The kernel panics with the following stack trace: https://imgur.com/a/fHTCk Expected results: Kernel should boot. Additional info: 1. If I press "e" at the GRUB menu, remove "quiet" from the boot parameters, and press Ctrl+X to continue, the kernel boots successfully. 2. I tried to get a kernel core dump using kdump, but nothing appears in /var/crash. If I manually trigger a panic with "echo c > /proc/sysrq-trigger", then I do see a core file. 3. There is an additional discussion here: https://ask.fedoraproject.org/en/question/106433/fail-to-boot-after-the-last-two-kernel-updates/ 4. Output of lspci on my computer: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.6 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 (rev c4) 00:1c.7 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 660] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GK106 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Broadcom Limited BCM43228 802.11a/b/g/n 04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
I've discovered that blacklisting nouveau allows my computer to finish booting.
Can you capture more of the stacktrace right after the "nvkm_timer_alarm_trigger" line? That will help give more information
The issue is known, and a patch has been sent upstream. I believe Greg has queued it for the various stable trees already, but I don't see it in a tagged release yet.
*** Bug 1461211 has been marked as a duplicate of this bug. ***
Just as an FYI, this bug still appears in kernel-4.11.4-200.fc25.x86_64
I believe 4.11.5 should have the fix so please test https://bodhi.fedoraproject.org/updates/FEDORA-2017-c283e18644
(In reply to Laura Abbott from comment #6) > I believe 4.11.5 should have the fix so please test > https://bodhi.fedoraproject.org/updates/FEDORA-2017-c283e18644 Hi Laura, I can confirm that I can boot, and run the 4.11.5 kernel.
kernel-4.11.5-200.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-c283e18644
*** Bug 1445312 has been marked as a duplicate of this bug. ***
I can confirm that 4.11.5 fixes this problem for me.
kernel-4.11.5-200.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.