Bug 1385340 - [abrt] WARNING: CPU: 2 PID: 920 at drivers/gpu/drm/drm_modeset_lock.c:343 drm_modeset_lock+0xca/0xd0 [drm]
Summary: [abrt] WARNING: CPU: 2 PID: 920 at drivers/gpu/drm/drm_modeset_lock.c:343 drm...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 25
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:7fe5febb3d67330d46b30786197...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-16 11:05 UTC by Kamil Páral
Modified: 2017-12-12 10:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:56:13 UTC
Type: ---


Attachments (Terms of Use)
File: dmesg (55.56 KB, text/plain)
2016-10-16 11:05 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2016-10-16 11:05:04 UTC
Description of problem:
Just booted and logged in.

Additional info:
reporter:       libreport-2.8.0
WARNING: CPU: 2 PID: 920 at drivers/gpu/drm/drm_modeset_lock.c:343 drm_modeset_lock+0xca/0xd0 [drm]
Modules linked in: vhost_net vhost macvtap macvlan ccm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_REJECT nf_reject_ipv6 fuse xt_conntrack ip6t_rpfilter ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_mangle ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_security ip6table_raw iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables bnep vfat fat intel_rapl arc4 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iTCO_wdt iTCO_vendor_support iwlmvm mei_wdt mac80211 irqbypass intel_cstate intel_uncore intel_rapl_perf snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi
 iwlwifi uvcvideo snd_hda_intel btusb videobuf2_vmalloc joydev videobuf2_memops cfg80211 btrtl snd_hda_codec btbcm rtsx_pci_ms videobuf2_v4l2 btintel i2c_i801 memstick videobuf2_core snd_hda_core i2c_smbus intel_pch_thermal videodev lpc_ich bluetooth shpchp snd_hwdep media snd_seq snd_seq_device snd_pcm mei_me mei snd_timer wmi thinkpad_acpi snd soundcore rfkill tpm_tis tpm_tis_core tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt i915 rtsx_pci_sdmmc mmc_core crct10dif_pclmul i2c_algo_bit crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel e1000e drm serio_raw ptp rtsx_pci pps_core fjes video
CPU: 2 PID: 920 Comm: systemd-logind Not tainted 4.8.1-1.fc25.x86_64 #1
Hardware name: LENOVO 20BWS1KY0H/20BWS1KY0H, BIOS JBET49WW (1.14 ) 05/21/2015
 0000000000000286 000000000546d7e1 ffffa144023978d8 ffffffffb03e5acd
 0000000000000000 0000000000000000 ffffa14402397918 ffffffffb00a0e4b
 00000157000c0800 ffffa143b6529e80 ffffa1440b5f0258 ffffa1440b5f0288
Call Trace:
 [<ffffffffb03e5acd>] dump_stack+0x63/0x86
 [<ffffffffb00a0e4b>] __warn+0xcb/0xf0
 [<ffffffffb00a0f7d>] warn_slowpath_null+0x1d/0x20
 [<ffffffffc02a545a>] drm_modeset_lock+0xca/0xd0 [drm]
 [<ffffffffc02a5bf2>] drm_atomic_get_connector_state+0x32/0x180 [drm]
 [<ffffffffc034cabe>] __drm_atomic_helper_set_config+0x29e/0x360 [drm_kms_helper]
 [<ffffffffc034ecfe>] restore_fbdev_mode+0x13e/0x270 [drm_kms_helper]
 [<ffffffffc0350884>] drm_fb_helper_restore_fbdev_mode_unlocked+0x34/0x80 [drm_kms_helper]
 [<ffffffffc03508fd>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper]
 [<ffffffffc044c71a>] intel_fbdev_set_par+0x1a/0x60 [i915]
 [<ffffffffb0467466>] fb_set_var+0x236/0x460
 [<ffffffffb00e4614>] ? __wake_up+0x44/0x50
 [<ffffffffb0800082>] ? down_write+0x12/0x40
 [<ffffffffb04d5850>] ? tty_unthrottle+0x50/0x60
 [<ffffffffb045d28f>] fbcon_blank+0x30f/0x350
 [<ffffffffb04e5fb2>] do_unblank_screen+0xd2/0x1a0
 [<ffffffffb04dbc87>] vt_ioctl+0x507/0x12a0
 [<ffffffffb0226b01>] ? __slab_free+0xa1/0x2a0
 [<ffffffffb04d00fa>] tty_ioctl+0x35a/0xc50
 [<ffffffffb04cf5b4>] ? tty_release+0x1f4/0x6a0
 [<ffffffffb0264c23>] do_vfs_ioctl+0xa3/0x5f0
 [<ffffffffb02651e9>] SyS_ioctl+0x79/0x90
 [<ffffffffb0003c57>] do_syscall_64+0x67/0x160
 [<ffffffffb0802621>] entry_SYSCALL64_slow_path+0x25/0x25

Comment 1 Kamil Páral 2016-10-16 11:05:12 UTC
Created attachment 1210950 [details]
File: dmesg

Comment 2 Fedora End Of Life 2017-11-16 15:35:31 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 Fedora End Of Life 2017-12-12 10:56:13 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.