Bug 1601125 - [abrt] nvkm_pci_intr: WARNING: CPU: 2 PID: 0 at drivers/gpu/drm/nouveau/nvkm/subdev/mc/base.c:72 nvkm_mc_intr+0x163/0x180 [nouveau] [nouveau]
Summary: [abrt] nvkm_pci_intr: WARNING: CPU: 2 PID: 0 at drivers/gpu/drm/nouveau/nvkm/...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:079fef24599b6816e9f64a49d85...
: 1646622 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-14 00:21 UTC by Pablo Viva
Modified: 2019-05-28 23:13 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:13:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (82.30 KB, text/plain)
2018-07-14 00:21 UTC, Pablo Viva
no flags Details

Description Pablo Viva 2018-07-14 00:21:27 UTC
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: i915 nouveau rtsx_pci_sdmmc mmc_core ttm i2c_algo_bit mxm_wmi drm_kms_helper r8169 drm mii serio_raw rtsx_pci crc32c_intel i2c_hid video wmi
CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.17.5-200.fc28.x86_64 #1
Hardware name: ASUSTeK COMPUTER INC. X541UJ/X541UJ, BIOS X541UJ.301 12/26/2016
RIP: 0010:nvkm_mc_intr+0x163/0x180 [nouveau]
RSP: 0018:ffff9881eed03ea0 EFLAGS: 00010046
RAX: 00000000ffffffff RBX: ffff9881db3429c0 RCX: 0000000000000000
RDX: ffffad5783000144 RSI: ffff9881eed03eff RDI: ffffad5783000104
RBP: ffff9881da6b4800 R08: ffff9881eed1de60 R09: ffffffff83480130
R10: 000000005b4915fe R11: 0000000000000000 R12: 00000000ffffffff
R13: ffff9881eed03f64 R14: 0000000000000000 R15: ffff9881d7f6d780
FS:  0000000000000000(0000) GS:ffff9881eed00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc0b377bc8 CR3: 000000013520a003 CR4: 00000000003606e0
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+0x41/0xc0
 common_interrupt+0xf/0xf
 </IRQ>
RIP: 0010:cpuidle_enter_state+0xb7/0x2a0
RSP: 0018:ffffad5781953e98 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffde
RAX: ffff9881eed20cc0 RBX: 00000001fa081642 RCX: 000000000000001f
RDX: 00000001fa081642 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000008 R08: 0000000b1e6d4c77 R09: 000000000000036e
R10: 000000000000afc7 R11: ffff9881eed1fae8 R12: ffff9881eed2b700
R13: ffffffff842d2dd8 R14: 00000001f75e2a79 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
Code: 89 f1 48 c7 c6 dd bf 40 c0 48 8b 14 c5 60 50 41 c0 49 8b 47 10 48 8b 78 10 e8 6a 15 30 c3 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 b9 45 de c2 66 

Potential duplicate: bug 1562482

Comment 1 Pablo Viva 2018-07-14 00:21:37 UTC
Created attachment 1458813 [details]
File: dmesg

Comment 2 Metehan 2018-11-05 19:10:15 UTC
*** Bug 1646622 has been marked as a duplicate of this bug. ***

Comment 3 Ben Cotton 2019-05-02 19:22:34 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.

Comment 4 Ben Cotton 2019-05-02 20:22:16 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.

Comment 5 Ben Cotton 2019-05-28 23:13:46 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.


Note You need to log in before you can comment on or make changes to this bug.