Bug 1636332 - [abrt] __intel_display_resume: WARNING: CPU: 1 PID: 16482 at drivers/gpu/drm/drm_atomic_helper.c:3135 drm_atomic_helper_commit_duplicated_state+0xfb/0x110 [drm_kms_helper] [i915]
Summary: [abrt] __intel_display_resume: WARNING: CPU: 1 PID: 16482 at drivers/gpu/drm/...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 29
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:a22370ca812ae5c6017eca79bf2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-05 07:02 UTC by lray+redhatbugzilla
Modified: 2019-10-26 12:21 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-09-17 20:05:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (125.04 KB, text/plain)
2018-10-05 07:03 UTC, lray+redhatbugzilla
no flags Details

Description lray+redhatbugzilla 2018-10-05 07:02:54 UTC
Additional info:
reporter:       libreport-2.9.5
WARNING: CPU: 1 PID: 16482 at drivers/gpu/drm/drm_atomic_helper.c:3135 drm_atomic_helper_commit_duplicated_state+0xfb/0x110 [drm_kms_helper]
Modules linked in: uas usb_storage usblp rfcomm fuse ccm xt_CHECKSUM ipt_MASQUERADE tun bridge stp llc devlink nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat 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 iptable_mangle iptable_raw iptable_security nf_conntrack libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep sunrpc dm_crypt rmi_smbus rmi_core vfat fat hid_logitech ff_memless intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel arc4 kvm mei_wdt iwlmvm iTCO_wdt iTCO_vendor_support uvcvideo wmi_bmof mac80211 irqbypass videobuf2_vmalloc crct10dif_pclmul
 crc32_pclmul videobuf2_memops videobuf2_v4l2 ghash_clmulni_intel intel_cstate videobuf2_common intel_uncore intel_rapl_perf videodev iwlwifi btusb btrtl media btbcm btintel bluetooth cfg80211 snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic joydev snd_hda_intel ecdh_generic rtsx_pci_ms mmc_block snd_hda_codec memstick mei_me lpc_ich intel_pch_thermal i2c_i801 snd_hda_core mei snd_seq snd_hwdep snd_seq_device snd_pcm thinkpad_acpi wmi snd_timer rfkill snd soundcore pcc_cpufreq binfmt_misc i915 rtsx_pci_sdmmc mmc_core i2c_algo_bit drm_kms_helper e1000e drm crc32c_intel serio_raw rtsx_pci video
CPU: 1 PID: 16482 Comm: kworker/u16:63 Not tainted 4.18.10-300.fc29.x86_64 #1
Hardware name: LENOVO 20CMCTO1WW/20CMCTO1WW, BIOS N10ET36W (1.15 ) 06/19/2015
Workqueue: events_unbound async_run_entry_fn
RIP: 0010:drm_atomic_helper_commit_duplicated_state+0xfb/0x110 [drm_kms_helper]
Code: 85 c9 74 0b 48 8b 89 f0 03 00 00 48 89 48 10 83 c2 01 39 57 28 7f da e9 23 13 f4 ff 0f 0b e9 6e ff ff ff 0f 0b e9 59 ff ff ff <0f> 0b e9 41 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 0f 
RSP: 0000:ffffaf1189727d60 EFLAGS: 00010286
RAX: ffff93febea49100 RBX: ffff93ff9d988000 RCX: 0000000000000008
RDX: ffff93ff9d024c00 RSI: ffff93ff4ec40d00 RDI: ffff93ff9ee2a000
RBP: ffff93ff9ee2a000 R08: 0000000000000000 R09: 0000000000000000
R10: ffff93ff9d988008 R11: 0000000000000002 R12: ffffaf1189727d98
R13: 0000000000000000 R14: 0000000000000010 R15: ffffffff9f13b283
FS:  0000000000000000(0000) GS:ffff93ffadc40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000012f20a001 CR4: 00000000003606e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 __intel_display_resume+0x7b/0xc0 [i915]
 intel_display_resume+0xc3/0x110 [i915]
 ? pci_pm_thaw+0x90/0x90
 i915_drm_resume+0xb3/0x100 [i915]
 dpm_run_callback+0x59/0x150
 device_resume+0xac/0x1f0
 async_resume+0x19/0x30
 async_run_entry_fn+0x39/0x160
 process_one_work+0x1a1/0x350
 worker_thread+0x30/0x380
 ? pwq_unbound_release_workfn+0xd0/0xd0
 kthread+0x112/0x130
 ? kthread_create_worker_on_cpu+0x70/0x70
 ret_from_fork+0x35/0x40

Comment 1 lray+redhatbugzilla 2018-10-05 07:03:10 UTC
Created attachment 1490763 [details]
File: dmesg

Comment 2 Anton Bakken 2018-11-01 15:10:54 UTC
Description of problem:
When I remove my laptop from my docking station, which has two external monitors connected to it, everything seems to work fine. However when I close the lid of the laptop and let it go into hybrid sleep, I will have an issue when I go to open the laptop again. It will come out of sleep but I have a blank screen. The screen will not show up again until I reconnect it to the docking station. This is on a Dell Latitude E5470 running Fedora 29 Cinnamon spin, connecting to a Dell PR02X Docking station. 

Version-Release number of selected component:
kernel-core-4.18.16-300.fc29

Additional info:
reporter:       libreport-2.9.6
cmdline:        BOOT_IMAGE=/vmlinuz-4.18.16-300.fc29.x86_64 root=/dev/mapper/fedora-root ro resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/root rd.luks.uuid=luks-943b8e04-4f82-4019-8dde-4d9e63b61a11 rd.lvm.lv=fedora/swap rhgb quiet LANG=en_CA.UTF-8
crash_function: __intel_display_resume
kernel:         4.18.16-300.fc29.x86_64
runlevel:       N 5
type:           Kerneloops

Truncated backtrace:
#1 __intel_display_resume in i915
#2 intel_display_resume in i915
#3 ? pci_pm_thaw
#4 i915_drm_resume in i915
#5 dpm_run_callback
#6 device_resume
#7 async_resume
#8 async_run_entry_fn
#9 ? pwq_unbound_release_workfn
#10 ? kthread_create_worker_on_cpu

Comment 3 Jeremy Cline 2018-12-03 17:32:17 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.
 
Fedora 29 has now been rebased to 4.19.5-300.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.

Comment 4 Anton Bakken 2018-12-07 22:32:39 UTC
I have upgraded to kernel 4.19.5-300.fc29 and this issue still persists.

Comment 5 Laura Abbott 2019-04-09 20:44:57 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.
 
Fedora XX has now been rebased to 5.0.6  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30.
 
If you experience different issues, please open a new bug report for those.

Comment 6 Justin M. Forbes 2019-09-17 20:05:10 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


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