Bug 1636663 - [abrt] fwtable_read32: WARNING: CPU: 0 PID: 2386 at drivers/gpu/drm/i915/intel_uncore.c:1077 __unclaimed_reg_debug+0x4d/0x70 [i915] [i915]
Summary: [abrt] fwtable_read32: WARNING: CPU: 0 PID: 2386 at drivers/gpu/drm/i915/inte...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 28
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:8dde13dba2252d99bf292e77444...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-06 11:50 UTC by otis
Modified: 2019-05-28 22:46 UTC (History)
4 users (show)

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


Attachments (Terms of Use)
File: dmesg (72.40 KB, text/plain)
2018-10-06 11:50 UTC, otis
no flags Details

Description otis 2018-10-06 11:50:42 UTC
Additional info:
reporter:       libreport-2.9.5
WARNING: CPU: 0 PID: 2386 at drivers/gpu/drm/i915/intel_uncore.c:1077 __unclaimed_reg_debug+0x4d/0x70 [i915]
Modules linked in: fuse rfcomm xt_CHECKSUM ipt_MASQUERADE tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack devlink ccm 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 intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel uvcvideo kvm snd_hda_codec_hdmi videobuf2_vmalloc arc4 videobuf2_memops snd_hda_codec_realtek irqbypass videobuf2_v4l2 asus_nb_wmi ath9k videobuf2_common asus_wmi videodev
 crc32_pclmul sparse_keymap iTCO_wdt iTCO_vendor_support intel_cstate ath9k_common ath3k media ath9k_hw snd_hda_codec_generic btusb snd_hda_intel snd_hda_codec snd_hda_core mac80211 btrtl ath cfg80211 snd_hwdep rtsx_pci_ms memstick snd_seq hci_uart btqca btbcm joydev btintel snd_seq_device snd_pcm wmi bluetooth snd_timer asus_wireless ecdh_generic snd rfkill_gpio mei_txe soundcore lpc_ich rfkill mei dw_dmac i2c_i801 pcc_cpufreq rtsx_pci_sdmmc mmc_core i915 crc32c_intel r8169 i2c_algo_bit drm_kms_helper syscopyarea serio_raw rtsx_pci sysfillrect mii sysimgblt ata_generic fb_sys_fops drm pata_acpi video pwm_lpss_platform pwm_lpss i2c_hid
CPU: 0 PID: 2386 Comm: kworker/u4:24 Not tainted 4.18.11-200.fc28.i686 #1
Hardware name: ASUSTeK COMPUTER INC. X553MA/X553MA, BIOS X553MA.214 08/03/2015
Workqueue: events_unbound async_run_entry_fn
EIP: __unclaimed_reg_debug+0x4d/0x70 [i915]
Code: 5e 5f 5d c3 89 f6 8d bc 27 00 00 00 00 89 f8 ba 08 c0 9c f7 56 84 c0 b8 fe bf 9c f7 0f 44 c2 50 68 11 c0 9c f7 e8 b7 50 33 d3 <0f> 0b 83 2d 28 59 9f f7 01 83 c4 0c 8d 65 f4 5b 5e 5f 5d c3 eb 0d 
EAX: 00000025 EBX: 00000000 ECX: f6b2edd0 EDX: 00000007
ESI: 001f0034 EDI: 00000001 EBP: ec81fcd8 ESP: ec81fcc0
DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00210096
CR0: 80050033 CR2: b1501db6 CR3: 0b92c000 CR4: 001006d0
Call Trace:
 fwtable_read32+0x170/0x1d0 [i915]
 ? gen5_read64+0x140/0x140 [i915]
 ? fwtable_read16+0x1d0/0x1d0 [i915]
 vlv_program_watermarks+0x3e7/0x670 [i915]
 vlv_optimize_watermarks+0xe1/0xf0 [i915]
 intel_atomic_commit_tail+0x3e2/0xd80 [i915]
 ? complete+0x3f/0x50
 ? finish_wait+0x70/0x70
 ? finish_wait+0x70/0x70
 intel_atomic_commit+0x285/0x2c0 [i915]
 ? intel_atomic_commit+0x285/0x2c0 [i915]
 ? intel_atomic_commit_tail+0xd80/0xd80 [i915]
 drm_atomic_commit+0x3a/0x50 [drm]
 drm_atomic_helper_commit_duplicated_state+0xd4/0x110 [drm_kms_helper]
 __intel_display_resume+0x75/0xd0 [i915]
 intel_display_resume+0xbc/0xf0 [i915]
 i915_drm_resume+0xa3/0xf0 [i915]
 i915_pm_resume+0x19/0x30 [i915]
 pci_pm_resume+0x5b/0x90
 dpm_run_callback+0x63/0x140
 ? pci_add_dynid+0xb0/0xb0
 device_resume+0x95/0x1d0
 ? device_resume+0x1d0/0x1d0
 async_resume+0x1b/0x30
 async_run_entry_fn+0x3a/0x160
 process_one_work+0x178/0x300
 worker_thread+0x39/0x3c0
 kthread+0xf0/0x110
 ? pwq_unbound_release_workfn+0xc0/0xc0
 ? kthread_create_worker_on_cpu+0x20/0x20
 ret_from_fork+0x2e/0x38

Comment 1 otis 2018-10-06 11:50:51 UTC
Created attachment 1491081 [details]
File: dmesg

Comment 2 Ben Cotton 2019-05-02 20:44:09 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-28 22:46:21 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.