Bug 1561327 - [abrt] nvkm_pci_intr: WARNING: CPU: 2 PID: 0 at drivers/gpu/drm/nouveau/nvkm/subdev/mc/base.c:72 nvkm_mc_intr+0x166/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: 27
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:5f179164b8991474b79a6e5bfe7...
: 1564127 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-28 06:34 UTC by f.alexander.wilms
Modified: 2018-11-30 20:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 20:49:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (75.29 KB, text/plain)
2018-03-28 06:34 UTC, f.alexander.wilms
no flags Details

Description f.alexander.wilms 2018-03-28 06:34:31 UTC
Additional info:
reporter:       libreport-2.9.3
WARNING: CPU: 2 PID: 0 at drivers/gpu/drm/nouveau/nvkm/subdev/mc/base.c:72 nvkm_mc_intr+0x166/0x180 [nouveau]
Modules linked in: fuse ccm rfcomm ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables bnep sunrpc vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass iwldvm snd_hda_codec snd_hda_core mac80211 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hwdep btusb btrtl uvcvideo btbcm btintel bluetooth videobuf2_vmalloc intel_cstate
 videobuf2_memops intel_uncore videobuf2_v4l2 videobuf2_core intel_rapl_perf snd_seq videodev media iwlwifi iTCO_wdt iTCO_vendor_support tpm_infineon ecdh_generic snd_seq_device cfg80211 snd_pcm rfkill joydev snd_timer tpm_tis tpm_tis_core acpi_als kfifo_buf snd soundcore tpm industrialio shpchp mei_me mei lpc_ich i2c_i801 i915 nouveau mxm_wmi ttm i2c_algo_bit drm_kms_helper crc32c_intel drm serio_raw r8169 mii video wmi
CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.15.10-300.fc27.x86_64 #1
Hardware name: SAMSUNG ELECTRONICS CO., LTD. 700Z3C/700Z5C/SAMSUNG_NP1234567890, BIOS P05AAG 02/07/2013
RIP: 0010:nvkm_mc_intr+0x166/0x180 [nouveau]
RSP: 0018:ffff88407f283ea8 EFLAGS: 00010046
RAX: 00000000ffffffff RBX: ffff88406fd20480 RCX: ffffb12f40ce3ea8
RDX: ffffb12f49088068 RSI: ffff88407f283f07 RDI: ffffb12f49000104
RBP: ffff8840706d7000 R08: 0000000000000000 R09: 0000000000000000
R10: ffff88407f283f88 R11: 0000000000000000 R12: 00000000ffffffff
R13: ffff88407f283f6c R14: ffff88406e87c8a0 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff88407f280000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000847e1ca6170 CR3: 00000001db20a004 CR4: 00000000001606e0
Call Trace:
 <IRQ>
 nvkm_pci_intr+0x5b/0x90 [nouveau]
 __handle_irq_event_percpu+0x40/0x190
 handle_irq_event_percpu+0x30/0x70
 handle_irq_event+0x27/0x50
 handle_edge_irq+0x73/0x190
 handle_irq+0xaf/0x120
 do_IRQ+0x41/0xc0
 common_interrupt+0x87/0x87
 </IRQ>
RIP: 0010:cpuidle_enter_state+0xa2/0x2e0
RSP: 0018:ffffb12f40ce3ea8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdc
RAX: ffff88407f2a0a80 RBX: 00000089390161e0 RCX: 000000000000001f
RDX: 00000089390161e0 RSI: fffffffe828f806c RDI: 0000000000000000
RBP: ffff88407f2aa340 R08: 0000000000001b26 R09: 0000000000000014
R10: ffffb12f40ce3e88 R11: 000000000000002d R12: 0000000000000002
R13: ffffffffac2d1378 R14: 0000000000000000 R15: 0000008933f7c87b
 ? cpuidle_enter_state+0x92/0x2e0
 do_idle+0x17b/0x1d0
 cpu_startup_entry+0x6f/0x80
 start_secondary+0x1a2/0x1f0
 secondary_startup_64+0xa5/0xb0
Code: 89 f9 48 c7 c6 57 66 3e c0 48 8b 14 c5 60 f0 3e c0 49 8b 46 10 48 8b 78 10 e8 d7 8a 2e eb 0f b6 54 24 0f 48 8b 04 24 88 10 eb b1 <0f> 0b 45 31 e4 c6 44 24 0f 00 e9 e7 fe ff ff e8 c6 53 e0 ea 66

Comment 1 f.alexander.wilms 2018-03-28 06:34:42 UTC
Created attachment 1413994 [details]
File: dmesg

Comment 2 miguelsantoscruz95 2018-04-05 12:32:24 UTC
*** Bug 1564127 has been marked as a duplicate of this bug. ***

Comment 3 Ben Cotton 2018-11-27 16:19:40 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 2018-11-30 20:49:09 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.