Bug 1580139 - [abrt] init_table_: WARNING: CPU: 2 PID: 142 at drivers/gpu/drm/nouveau/include/nvkm/subdev/i2c.h:170 nvkm_dp_acquire+0x9bd/0xc90 [nouveau] [nouveau]
Summary: [abrt] init_table_: WARNING: CPU: 2 PID: 142 at drivers/gpu/drm/nouveau/inclu...
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:5b5d215020bc51b56edfb040afb...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-20 16:01 UTC by Manuel Quarneti
Modified: 2019-05-28 23:01 UTC (History)
6 users (show)

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


Attachments (Terms of Use)
File: dmesg (71.60 KB, text/plain)
2018-05-20 16:01 UTC, Manuel Quarneti
no flags Details

Description Manuel Quarneti 2018-05-20 16:01:33 UTC
Description of problem:
I booted the system and Fedora warned me about this error.

Additional info:
reporter:       libreport-2.9.4
WARNING: CPU: 2 PID: 142 at drivers/gpu/drm/nouveau/include/nvkm/subdev/i2c.h:170 nvkm_dp_acquire+0x9bd/0xc90 [nouveau]
Modules linked in: fuse devlink nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT 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 sunrpc vfat fat snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iTCO_wdt snd_hda_codec_realtek iTCO_vendor_support snd_hda_codec_generic irqbypass crct10dif_pclmul crc32_pclmul uvcvideo snd_hda_intel snd_usb_audio ghash_clmulni_intel snd_hda_codec intel_cstate videobuf2_vmalloc
 intel_uncore videobuf2_memops intel_rapl_perf snd_hda_core snd_usbmidi_lib snd_rawmidi snd_hwdep videobuf2_v4l2 snd_seq videobuf2_common snd_seq_device snd_pcm videodev xpad joydev media ff_memless snd_timer snd soundcore i2c_i801 mei_me mei intel_pch_thermal shpchp acpi_pad uas usb_storage nouveau i2c_algo_bit drm_kms_helper ttm e1000e mxm_wmi drm crc32c_intel ptp pps_core wmi video
CPU: 2 PID: 142 Comm: kworker/u16:3 Not tainted 4.16.3-301.fc28.x86_64 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z170A-X1/3.1, BIOS P7.20 10/20/2016
Workqueue: nvkm-disp gf119_disp_super [nouveau]
RIP: 0010:nvkm_dp_acquire+0x9bd/0xc90 [nouveau]
RSP: 0018:ffffc0df02137d00 EFLAGS: 00010297
RAX: 0000000000000000 RBX: ffff9de19de5b800 RCX: 0000000000000000
RDX: ffffc0df0300d9a4 RSI: ffffc0df0300d9a4 RDI: 0000000001009000
RBP: ffff9de1a3909800 R08: ffffc0df02137d4f R09: ffffc0df02137d50
R10: 0000000000000000 R11: 0000000010624dd3 R12: 0000000000000000
R13: 000000000006cc3c R14: ffff9de19e5c31e0 R15: ffffffffc05dbfa8
FS:  0000000000000000(0000) GS:ffff9de1b6480000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fadd5d40380 CR3: 00000002fe20a004 CR4: 00000000003606e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 ? init_table_+0xd6/0x1b0 [nouveau]
 ? init_rd32+0xa2/0x2e0 [nouveau]
 ? init_condition_met+0x70/0x100 [nouveau]
 ? init_mask+0x100/0x300 [nouveau]
 ? nvbios_rd32+0x20/0x40 [nouveau]
 ? init_wr32+0xa5/0x2d0 [nouveau]
 ? nvbios_rd08+0x20/0x40 [nouveau]
 nv50_disp_super_2_2+0x70/0x4a0 [nouveau]
 gf119_disp_super+0x17e/0x2d0 [nouveau]
 process_one_work+0x187/0x340
 worker_thread+0x2e/0x380
 ? pwq_unbound_release_workfn+0xd0/0xd0
 kthread+0x112/0x130
 ? kthread_create_worker_on_cpu+0x70/0x70
 ret_from_fork+0x35/0x40
Code: 8d 4c 24 50 4c 8d 44 24 4f b9 00 06 00 00 48 89 ef ba 09 00 00 00 be 01 00 00 00 e8 8e 10 fd ff 85 c0 75 6b 80 7c 24 50 01 74 02 <0f> 0b 48 89 ef e8 69 0e fd ff 0f b6 44 24 4f 89 c2 83 e2 03 80

Comment 1 Manuel Quarneti 2018-05-20 16:01:43 UTC
Created attachment 1439230 [details]
File: dmesg

Comment 2 Ben Cotton 2019-05-02 19:22:26 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 3 Ben Cotton 2019-05-02 20:34:29 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-28 23:01:24 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.