Bug 1622339 - [abrt] finish_wait: WARNING: CPU: 1 PID: 2262 at drivers/gpu/drm/drm_vblank.c:1084 drm_wait_one_vblank+0x16e/0x180 [drm]
Summary: [abrt] finish_wait: WARNING: CPU: 1 PID: 2262 at drivers/gpu/drm/drm_vblank.c...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 27
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:38da075223f478493d84ed3de5c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-26 13:29 UTC by Nir Gilboa
Modified: 2019-10-30 13:29 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-30 23:02:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (83.62 KB, text/plain)
2018-08-26 13:29 UTC, Nir Gilboa
no flags Details

Description Nir Gilboa 2018-08-26 13:29:40 UTC
Additional info:
reporter:       libreport-2.9.3
WARNING: CPU: 1 PID: 2262 at drivers/gpu/drm/drm_vblank.c:1084 drm_wait_one_vblank+0x16e/0x180 [drm]
Modules linked in: xt_REDIRECT nf_nat_redirect nf_conntrack_netlink xt_addrtype br_netfilter overlay rfcomm fuse ccm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack cmac 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 binfmt_misc bnep vfat fat arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp mei_wdt kvm_intel iTCO_wdt iTCO_vendor_support uvcvideo wmi_bmof intel_wmi_thunderbolt
 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common kvm videodev btusb btrtl btbcm btintel media bluetooth snd_usb_audio iwlmvm snd_hda_codec_hdmi snd_usbmidi_lib snd_rawmidi mac80211 irqbypass snd_hda_codec_realtek intel_cstate ecdh_generic snd_hda_codec_generic intel_uncore intel_rapl_perf iwlwifi snd_hda_intel snd_hda_codec cfg80211 snd_hda_core joydev snd_hwdep rtsx_pci_ms snd_seq snd_seq_device memstick snd_pcm mei_me snd_timer mei i2c_i801 intel_pch_thermal shpchp thinkpad_acpi wmi snd soundcore rfkill acpi_pad pcc_cpufreq auth_rpcgss sunrpc dm_crypt hid_plantronics hid_multitouch i915 rtsx_pci_sdmmc crct10dif_pclmul mmc_core crc32_pclmul crc32c_intel i2c_algo_bit drm_kms_helper e1000e nvme drm ghash_clmulni_intel serio_raw nvme_core rtsx_pci video
CPU: 1 PID: 2262 Comm: Xorg Not tainted 4.17.12-100.fc27.x86_64 #1
Hardware name: LENOVO 20J7S02801/20J7S02801, BIOS R0FET39W (1.19 ) 12/20/2017
RIP: 0010:drm_wait_one_vblank+0x16e/0x180 [drm]
RSP: 0018:ffffb9a3c115fad8 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff97d491a40000 RCX: 0000000000000006
RDX: 0000000000000007 RSI: 0000000000000092 RDI: ffff97d4a1496930
RBP: 0000000000000000 R08: 0000000000000423 R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: 00000000000caede R14: ffff97d492f8c808 R15: ffff97d34f191c00
FS:  00007fb920850a80(0000) GS:ffff97d4a1480000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000021d28813f010 CR3: 000000024eac0003 CR4: 00000000003606e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 ? finish_wait+0x80/0x80
 skl_update_crtcs+0x1c2/0x270 [i915]
 intel_atomic_commit_tail+0x1d4/0xc60 [i915]
 intel_atomic_commit+0x29c/0x2d0 [i915]
 drm_atomic_connector_commit_dpms+0xe5/0xf0 [drm]
 drm_mode_obj_set_property_ioctl+0x174/0x290 [drm]
 ? drm_mode_connector_set_obj_prop+0x70/0x70 [drm]
 drm_mode_connector_property_set_ioctl+0x3e/0x60 [drm]
 drm_ioctl_kernel+0x5b/0xb0 [drm]
 drm_ioctl+0x2c3/0x360 [drm]
 ? drm_mode_connector_set_obj_prop+0x70/0x70 [drm]
 ? signal_setup_done+0x67/0xb0
 ? do_signal+0x194/0x610
 do_vfs_ioctl+0xa4/0x620
 ksys_ioctl+0x70/0x80
 __x64_sys_ioctl+0x16/0x20
 do_syscall_64+0x5b/0x160
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7fb91db3c0f7
RSP: 002b:00007ffc975a1048 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fb91db3c0f7
RDX: 00007ffc975a1080 RSI: 00000000c01064ab RDI: 000000000000000c
RBP: 00007ffc975a1080 R08: 0000000001c88fb0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c01064ab
R13: 000000000000000c R14: 0000000001b0b280 R15: 000000000084b3e0
Code: 2d ff ff ff e8 54 3a e7 f2 48 89 e6 4c 89 f7 e8 e9 c8 eb f2 45 85 e4 0f 85 0a ff ff ff 89 ee 48 c7 c7 98 73 25 c0 e8 a2 37 e7 f2 <0f> 0b e9 f5 fe ff ff 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 

Potential duplicate: bug 1577381

Comment 1 Nir Gilboa 2018-08-26 13:29:58 UTC
Created attachment 1478773 [details]
File: dmesg

Comment 2 Laura Abbott 2018-10-01 21:24:45 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 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.18.10-100.fc27.  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 28 or Fedora 29, and are still experiencing this issue, please change the version to Fedora 28 or 29.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Ben Cotton 2018-11-27 14:12:24 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 23:02:50 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.