Additional info: reporter: libreport-2.9.5 WARNING: CPU: 2 PID: 0 at drivers/gpu/drm/nouveau/nvkm/subdev/mc/base.c:72 nvkm_mc_intr+0x163/0x180 [nouveau] Modules linked in: nouveau i915 mxm_wmi ttm rtsx_pci_sdmmc i2c_algo_bit mmc_core drm_kms_helper crc32c_intel drm r8169 serio_raw rtsx_pci mii video wmi CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.18.5-300.fc29.x86_64 #1 Hardware name: HP HP Pavilion Gaming Notebook/816B, BIOS F.88 06/27/2018 RIP: 0010:nvkm_mc_intr+0x163/0x180 [nouveau] Code: f1 48 c7 c6 0b 9d 72 c0 48 8b 14 c5 60 30 73 c0 49 8b 47 10 48 8b 78 10 e8 3a 1a 01 d3 48 8b 04 24 0f b6 54 24 0f 88 10 eb b1 <0f> 0b 45 31 e4 c6 44 24 0f 00 e9 ea fe ff ff e8 09 5e ae d2 66 0f RSP: 0018:ffff9d4182483ea0 EFLAGS: 00010046 RAX: 00000000ffffffff RBX: ffff9d4170a963c0 RCX: 0000000000000000 RDX: ffffbf8584000144 RSI: ffff9d4182483eff RDI: ffffbf8584000104 RBP: ffff9d4173096400 R08: ffff9d418249dee0 R09: ffffffff93125a80 R10: 0000000000000000 R11: 0000000000000000 R12: 00000000ffffffff R13: ffff9d4182483f64 R14: 0000000000000000 R15: ffff9d4170b3e600 FS: 0000000000000000(0000) GS:ffff9d4182480000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005642ba57d008 CR3: 000000019520a002 CR4: 00000000003606e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <IRQ> nvkm_pci_intr+0x4c/0x90 [nouveau] __handle_irq_event_percpu+0x40/0x180 handle_irq_event_percpu+0x30/0x80 handle_irq_event+0x27/0x44 handle_fasteoi_irq+0x7f/0x120 handle_irq+0xbf/0x100 do_IRQ+0x49/0xd0 common_interrupt+0xf/0xf </IRQ> RIP: 0010:cpuidle_enter_state+0xb7/0x2a0 Code: e8 ee b6 98 ff 80 7c 24 03 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 d7 01 00 00 31 ff e8 80 5a 9e ff fb 66 0f 1f 44 00 00 <48> b8 ff ff ff ff f3 01 00 00 4c 29 f3 ba ff ff ff 7f 48 39 c3 7f RSP: 0018:ffffbf8580d2fe98 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffde RAX: ffff9d41824a0e80 RBX: 0000000256e0af9d RCX: 000000000000001f RDX: 0000000256e0af9d RSI: 0000000000000000 RDI: 0000000000000000 RBP: 0000000000000002 R08: 000002da06967c68 R09: 00000000000003db R10: 00000000000003db R11: ffff9d418249fce8 R12: ffff9d41824ab700 R13: ffffffff942d4278 R14: 0000000256d94fae R15: 0000000000000000 ? cpuidle_enter_state+0x92/0x2a0 do_idle+0x21d/0x260 cpu_startup_entry+0x6f/0x80 start_secondary+0x1a7/0x200 secondary_startup_64+0xa5/0xb0 Potential duplicate: bug 1601125
Created attachment 1488166 [details] File: dmesg
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.