Description of problem: i have a probleme with my driver intel Additional info: reporter: libreport-2.6.3 WARNING: CPU: 0 PID: 91 at drivers/gpu/drm/drm_atomic.c:491 drm_atomic_check_only+0x4bf/0x5a0 [drm]() Modules linked in: i915 uas i2c_algo_bit drm_kms_helper syscopyarea serio_raw sysfillrect sysimgblt fb_sys_fops usb_storage drm r8169 mii fjes video CPU: 0 PID: 91 Comm: kworker/u4:5 Not tainted 4.3.3-300.fc23.i686 #1 Hardware name: TOSHIBA Satellite L450/NBWAA, BIOS V1.40 03/25/2010 Workqueue: events_unbound async_run_entry_fn c0d69967 60903911 00000000 f31edb80 c071ecd0 00000000 f31edbb0 c045f3d7 c0c80108 00000000 0000005b f7dafb98 000001eb f7da0f4f f7da0f4f f3289800 f68ae170 00000000 f31edbc0 c045f4e2 00000009 00000000 f31edc0c f7da0f4f Call Trace: [<c071ecd0>] dump_stack+0x41/0x61 [<c045f3d7>] warn_slowpath_common+0x87/0xc0 [<f7da0f4f>] ? drm_atomic_check_only+0x4bf/0x5a0 [drm] [<f7da0f4f>] ? drm_atomic_check_only+0x4bf/0x5a0 [drm] [<c045f4e2>] warn_slowpath_null+0x22/0x30 [<f7da0f4f>] drm_atomic_check_only+0x4bf/0x5a0 [drm] [<f7da0239>] ? drm_atomic_set_crtc_for_plane+0x69/0x100 [drm] [<f7da1118>] ? drm_atomic_set_fb_for_plane+0x28/0xa0 [drm] [<f7da1046>] drm_atomic_commit+0x16/0x60 [drm] [<f8276f27>] intel_get_load_detect_pipe+0x417/0x5f0 [i915] [<c048c9f1>] ? pick_next_entity+0x71/0x110 [<f82aed26>] intel_tv_detect+0x106/0x660 [i915] [<f7d9baf0>] ? drm_get_edid+0x30/0x400 [drm] [<f7ce1beb>] drm_helper_probe_single_connector_modes_merge_bits+0x20b/0x480 [drm_kms_helper] [<f7ce1e77>] drm_helper_probe_single_connector_modes+0x17/0x20 [drm_kms_helper] [<f7ced092>] drm_fb_helper_initial_config+0x72/0x3e0 [drm_kms_helper] [<c0497169>] ? pick_next_task_fair+0x429/0x4e0 [<f82879c9>] intel_fbdev_initial_config+0x19/0x20 [i915] [<c047ce4e>] async_run_entry_fn+0x4e/0x170 [<c04751c5>] process_one_work+0x145/0x380 [<c0475439>] worker_thread+0x39/0x430 [<c0475400>] ? process_one_work+0x380/0x380 [<c047a776>] kthread+0xa6/0xc0 [<c0ac53c1>] ret_from_kernel_thread+0x21/0x30 [<c047a6d0>] ? kthread_worker_fn+0x130/0x130 Potential duplicate: bug 1262555
Created attachment 1115086 [details] File: dmesg
Description of problem: trying to connect mobile broadband connection Version-Release number of selected component: kernel Additional info: reporter: libreport-2.6.3 cmdline: BOOT_IMAGE=/vmlinuz-4.3.3-300.fc23.x86_64 root=UUID=75a49e7b-9685-4a32-8144-9ee353412544 ro rhgb quiet LANG=en_IN.UTF-8 kernel: 4.3.3-300.fc23.x86_64 runlevel: unknown type: Kerneloops Truncated backtrace: WARNING: CPU: 1 PID: 94 at drivers/gpu/drm/drm_atomic.c:491 drm_atomic_check_only+0x46e/0x540 [drm]() Modules linked in: i915 tg3(+) serio_raw firewire_ohci(+) ata_generic i2c_algo_bit pata_acpi drm_kms_helper firewire_core yenta_socket crc_itu_t drm ptp pps_core fjes video CPU: 1 PID: 94 Comm: kworker/u4:5 Not tainted 4.3.3-300.fc23.x86_64 #1 Hardware name: Hewlett-Packard HP Compaq 6510b (RJ559AV)/30C0, BIOS 68DDU Ver. F.16 08/09/2010 Workqueue: events_unbound async_run_entry_fn 0000000000000000 00000000bd5c8c91 ffff88013985ba38 ffffffff813a626f 0000000000000000 ffff88013985ba70 ffffffff810a07c2 ffff8800368f0000 ffff880036960000 0000000000000001 0000000000000000 ffff880036b08e00 Call Trace: [<ffffffff813a626f>] dump_stack+0x44/0x55 [<ffffffff810a07c2>] warn_slowpath_common+0x82/0xc0 [<ffffffff810a090a>] warn_slowpath_null+0x1a/0x20 [<ffffffffa004b60e>] drm_atomic_check_only+0x46e/0x540 [drm] [<ffffffffa004b7cd>] ? drm_atomic_set_fb_for_plane+0x2d/0x90 [drm] [<ffffffffa004b6f7>] drm_atomic_commit+0x17/0x60 [drm] [<ffffffffa0190415>] intel_get_load_detect_pipe+0x3d5/0x530 [i915] [<ffffffffa01c870d>] intel_tv_detect+0x13d/0x5e0 [i915] [<ffffffffa0045f2e>] ? drm_get_edid+0x3e/0x3f0 [drm] [<ffffffff81780586>] ? schedule_hrtimeout_range_clock.part.23+0xa6/0x150 [<ffffffffa00c7d15>] drm_helper_probe_single_connector_modes_merge_bits+0x235/0x4d0 [drm_kms_helper] [<ffffffffa00c7fc3>] drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper] [<ffffffffa00d3853>] drm_fb_helper_initial_config+0x83/0x400 [drm_kms_helper] [<ffffffff810146f1>] ? __switch_to+0x261/0x4b0 [<ffffffffa01a143b>] intel_fbdev_initial_config+0x1b/0x20 [i915] [<ffffffff810c171a>] async_run_entry_fn+0x4a/0x140 [<ffffffff810b8cde>] process_one_work+0x19e/0x3f0 [<ffffffff810b8f7e>] worker_thread+0x4e/0x450 [<ffffffff810b8f30>] ? process_one_work+0x3f0/0x3f0 [<ffffffff810bede8>] kthread+0xd8/0xf0 [<ffffffff810bed10>] ? kthread_worker_fn+0x160/0x160 [<ffffffff8178199f>] ret_from_fork+0x3f/0x70 [<ffffffff810bed10>] ? kthread_worker_fn+0x160/0x160
Description of problem: After using the internet for about 25 minutes, the wireless connection suddenly loses its connectiong and the wireless symbol turns into a question mark. It seems the driver crashes. Using a Dell Latitude D530 with a Intel Core 2 Duo 2 ghz processor and 1490 Dell Wireless controller. Version-Release number of selected component: kernel Additional info: reporter: libreport-2.6.3 cmdline: BOOT_IMAGE=/vmlinuz-4.3.3-300.fc23.x86_64 root=/dev/mapper/fedora_granpa-root ro rd.lvm.lv=fedora_granpa/root rd.lvm.lv=fedora_granpa/swap rhgb quiet LANG=en_US.UTF-8 kernel: 4.3.3-300.fc23.x86_64 runlevel: unknown type: Kerneloops Truncated backtrace: WARNING: CPU: 1 PID: 89 at drivers/gpu/drm/drm_atomic.c:491 drm_atomic_check_only+0x46e/0x540 [drm]() Modules linked in: i915(+) tg3 serio_raw firewire_ohci firewire_core yenta_socket ata_generic pata_acpi i2c_algo_bit drm_kms_helper crc_itu_t drm ptp pps_core video CPU: 1 PID: 89 Comm: kworker/u4:3 Not tainted 4.3.3-300.fc23.x86_64 #1 Hardware name: Dell Inc. Latitude D530 /0HP728, BIOS A05 04/03/2008 Workqueue: events_unbound async_run_entry_fn 0000000000000000 00000000efca0fcc ffff88009830fa38 ffffffff813a626f 0000000000000000 ffff88009830fa70 ffffffff810a07c2 ffff8800983fb000 ffff88009b50a000 0000000000000001 0000000000000000 ffff8800366d4200 Call Trace: [<ffffffff813a626f>] dump_stack+0x44/0x55 [<ffffffff810a07c2>] warn_slowpath_common+0x82/0xc0 [<ffffffff810a090a>] warn_slowpath_null+0x1a/0x20 [<ffffffffa004860e>] drm_atomic_check_only+0x46e/0x540 [drm] [<ffffffffa00487cd>] ? drm_atomic_set_fb_for_plane+0x2d/0x90 [drm] [<ffffffffa00486f7>] drm_atomic_commit+0x17/0x60 [drm] [<ffffffffa018c415>] intel_get_load_detect_pipe+0x3d5/0x530 [i915] [<ffffffffa01c470d>] intel_tv_detect+0x13d/0x5e0 [i915] [<ffffffffa0096d15>] drm_helper_probe_single_connector_modes_merge_bits+0x235/0x4d0 [drm_kms_helper] [<ffffffffa0096fc3>] drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper] [<ffffffffa00a2853>] drm_fb_helper_initial_config+0x83/0x400 [drm_kms_helper] [<ffffffff810146f1>] ? __switch_to+0x261/0x4b0 [<ffffffffa019d43b>] intel_fbdev_initial_config+0x1b/0x20 [i915] [<ffffffff810c171a>] async_run_entry_fn+0x4a/0x140 [<ffffffff810b8cde>] process_one_work+0x19e/0x3f0 [<ffffffff810b8f7e>] worker_thread+0x4e/0x450 [<ffffffff810b8f30>] ? process_one_work+0x3f0/0x3f0 [<ffffffff810bede8>] kthread+0xd8/0xf0 [<ffffffff810bed10>] ? kthread_worker_fn+0x160/0x160 [<ffffffff8178199f>] ret_from_fork+0x3f/0x70 [<ffffffff810bed10>] ? kthread_worker_fn+0x160/0x160
A user mentioned (in the Debian bug report) that upgrading to kernel 4.4 worked for him.
Just for the sake of completeness: I think there are similar reports for Ubuntu (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525509) and upstream (https://bugs.freedesktop.org/show_bug.cgi?id=92718).
My problem happens when I start the system. I couldn't notice if it was caused by wireless connection or not. $ uname -a Linux wilma.bedrock 4.3.4-300.fc23.x86_64 #1 SMP Mon Jan 25 13:39:23 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux [ 103.845372] ------------[ cut here ]------------ [ 103.845404] WARNING: CPU: 0 PID: 1994 at drivers/gpu/drm/drm_atomic.c:491 drm_atomic_check_only+0x46e/0x540 [drm]() [ 103.845406] Modules linked in: fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ccm nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_broute bridge stp llc ebtable_nat ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_raw ip6table_mangle ip6table_security ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_raw iptable_mangle iptable_security arc4 iTCO_wdt iwl3945 iTCO_vendor_support snd_hda_codec_hdmi coretemp gpio_ich dell_laptop ppdev dell_wmi sparse_keymap dcdbas snd_hda_codec_idt iwlegacy joydev snd_hda_codec_generic dell_smm_hwmon mac80211 lpc_ich snd_hda_intel snd_hda_codec cfg80211 i2c_i801 snd_hda_core snd_hwdep parport_pc [ 103.845457] snd_seq snd_seq_device acpi_cpufreq rfkill parport wmi snd_pcm tpm_tis irda tpm snd_timer crc_ccitt snd soundcore shpchp nfsd auth_rpcgss nfs_acl lockd grace sunrpc i915 i2c_algo_bit drm_kms_helper drm tg3 serio_raw firewire_ohci firewire_core yenta_socket ata_generic ptp pata_acpi crc_itu_t pps_core video [ 103.845487] CPU: 0 PID: 1994 Comm: Xorg Tainted: G W 4.3.4-300.fc23.x86_64 #1 [ 103.845489] Hardware name: Dell Inc. Latitude D530 /0HP727, BIOS A02 01/14/2008 [ 103.845492] 0000000000000000 00000000c8c6a843 ffff880099f5f9b8 ffffffff813a625f [ 103.845496] 0000000000000000 ffff880099f5f9f0 ffffffff810a07c2 ffff880036ac7000 [ 103.845499] ffff880036ab4800 0000000000000002 0000000000000000 ffff880098dd1000 [ 103.845502] Call Trace: [ 103.845510] [<ffffffff813a625f>] dump_stack+0x44/0x55 [ 103.845514] [<ffffffff810a07c2>] warn_slowpath_common+0x82/0xc0 [ 103.845517] [<ffffffff810a090a>] warn_slowpath_null+0x1a/0x20 [ 103.845532] [<ffffffffa00b465e>] drm_atomic_check_only+0x46e/0x540 [drm] [ 103.845549] [<ffffffffa00b481d>] ? drm_atomic_set_fb_for_plane+0x2d/0x90 [drm] [ 103.845564] [<ffffffffa00b4747>] drm_atomic_commit+0x17/0x60 [drm] [ 103.845606] [<ffffffffa017d855>] intel_get_load_detect_pipe+0x3d5/0x530 [i915] [ 103.845635] [<ffffffffa01b5b5d>] intel_tv_detect+0x13d/0x5e0 [i915] [ 103.845644] [<ffffffffa00e9d15>] drm_helper_probe_single_connector_modes_merge_bits+0x235/0x4d0 [drm_kms_helper] [ 103.845649] [<ffffffff8110b47f>] ? hrtimer_start_range_ns+0x1bf/0x3b0 [ 103.845655] [<ffffffffa00e9fc3>] drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper] [ 103.845671] [<ffffffffa00a798f>] drm_mode_getconnector+0x31f/0x370 [drm] [ 103.845674] [<ffffffff810ac206>] ? dequeue_signal+0x36/0x170 [ 103.845686] [<ffffffffa0099408>] drm_ioctl+0x138/0x500 [drm] [ 103.845700] [<ffffffffa00a7670>] ? drm_mode_getcrtc+0x140/0x140 [drm] [ 103.845704] [<ffffffff8133572c>] ? ioctl_has_perm+0xbc/0xf0 [ 103.845709] [<ffffffff81236bd5>] do_vfs_ioctl+0x295/0x470 [ 103.845712] [<ffffffff813357b0>] ? selinux_file_ioctl+0x50/0xd0 [ 103.845715] [<ffffffff813298e3>] ? security_file_ioctl+0x43/0x60 [ 103.845718] [<ffffffff81236e29>] SyS_ioctl+0x79/0x90 [ 103.845722] [<ffffffff8178182e>] entry_SYSCALL_64_fastpath+0x12/0x71 [ 103.845725] ---[ end trace dec5b4c36de6a936 ]---
Btw: Upgrading to 4.5rc2 (Fedora mainline copr) does not fix the bug for me. Instead I'm seeing the same symptoms but with a slightly different backtrace. The (new) backtrace was already reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=93782 I guess everyone here is using an old Intel chipset such as GM965/GL960GM?
Description of problem: System reboot Version-Release number of selected component: kernel Additional info: reporter: libreport-2.6.4 cmdline: BOOT_IMAGE=/vmlinuz-4.3.5-300.fc23.i686 root=UUID=f9369c4c-b3ef-4d86-b7c2-b9da0ef21b03 ro rhgb quiet LANG=en_US.UTF-8 kernel: 4.3.5-300.fc23.i686 runlevel: unknown type: Kerneloops Truncated backtrace: WARNING: CPU: 0 PID: 85 at drivers/gpu/drm/drm_atomic.c:491 drm_atomic_check_only+0x4bf/0x5a0 [drm]() Modules linked in: i915 tg3 firewire_ohci firewire_core ata_generic i2c_algo_bit drm_kms_helper serio_raw ptp syscopyarea sysfillrect sysimgblt pata_acpi crc_itu_t fb_sys_fops yenta_socket drm pps_core fjes video CPU: 0 PID: 85 Comm: kworker/u4:3 Not tainted 4.3.5-300.fc23.i686 #1 Hardware name: LENOVO 9457A51/9457A51, BIOS 7CET47WW (1.02 ) 04/11/2006 Workqueue: events_unbound async_run_entry_fn c0d69967 24d2510d 00000000 f6999b80 c071ee40 00000000 f6999bb0 c045f437 c0c80228 00000000 00000055 f7e04b98 000001eb f7df5fbf f7df5fbf f43b2800 f6980840 00000000 f6999bc0 c045f542 00000009 00000000 f6999c0c f7df5fbf Call Trace: [<c071ee40>] dump_stack+0x41/0x61 [<c045f437>] warn_slowpath_common+0x87/0xc0 [<f7df5fbf>] ? drm_atomic_check_only+0x4bf/0x5a0 [drm] [<f7df5fbf>] ? drm_atomic_check_only+0x4bf/0x5a0 [drm] [<c045f542>] warn_slowpath_null+0x22/0x30 [<f7df5fbf>] drm_atomic_check_only+0x4bf/0x5a0 [drm] [<f7df52a9>] ? drm_atomic_set_crtc_for_plane+0x69/0x100 [drm] [<f7df6188>] ? drm_atomic_set_fb_for_plane+0x28/0xa0 [drm] [<f7df60b6>] drm_atomic_commit+0x16/0x60 [drm] [<f804a217>] intel_get_load_detect_pipe+0x417/0x5f0 [i915] [<c048ca51>] ? pick_next_entity+0x71/0x110 [<f8082026>] intel_tv_detect+0x106/0x660 [i915] [<f7df0b60>] ? drm_get_edid+0x30/0x400 [drm] [<f7da4beb>] drm_helper_probe_single_connector_modes_merge_bits+0x20b/0x480 [drm_kms_helper] [<c044c12d>] ? vmalloc_fault+0xdd/0x120 [<f805aca0>] ? intel_fbdev_init+0x530/0x530 [i915] [<f7da4e77>] drm_helper_probe_single_connector_modes+0x17/0x20 [drm_kms_helper] [<f7db0092>] drm_fb_helper_initial_config+0x72/0x3e0 [drm_kms_helper] [<c044c6b0>] ? __do_page_fault+0x470/0x470 [<c044c6ca>] ? do_page_fault+0x1a/0x20 [<f805acb9>] intel_fbdev_initial_config+0x19/0x20 [i915] [<c047ceae>] async_run_entry_fn+0x4e/0x170 [<c0475225>] process_one_work+0x145/0x380 [<c0475499>] worker_thread+0x39/0x430 [<c0475460>] ? process_one_work+0x380/0x380 [<c047a7d6>] kthread+0xa6/0xc0 [<c0ac5cc1>] ret_from_kernel_thread+0x21/0x30 [<c047a730>] ? kthread_worker_fn+0x130/0x130
945GM here same issue on kernel 4.3.5-300.fc23.x86_64
Description of problem: After kernel upgrade from 4.2.8 to 4.3.5 and reboot, login to GNOME and kernel error message. GNOME shell responds very slowly most of the times. Multiple intel video driver backtraces are shown in dmesg. Video chipset is i945 GM. Note that this CPU does not support PAT, and kernel 4.2 to 4.3 phased out MTRR in favor of PAT. The same behavior was observed with kernel 4.3.3 Tried with kernel 4.4.1-300.vanilla.knurd.1.fc23.i686+PAE, seems better responding, but still multiple backtraces are shown in dmesg. Version-Release number of selected component: kernel Additional info: reporter: libreport-2.6.3 cmdline: BOOT_IMAGE=/vmlinuz-4.3.5-300.fc23.i686+PAE root=UUID=2ba417a6-91cc-4fea-b2eb-2ed1c5b3eb99 ro rd.md=0 rd.lvm=0 rd.dm=0 vconsle.font=True vconsole.keymap=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet kernel: 4.3.5-300.fc23.i686+PAE runlevel: unknown type: Kerneloops Truncated backtrace: WARNING: CPU: 0 PID: 56 at drivers/gpu/drm/drm_atomic.c:491 drm_atomic_check_only+0x4bf/0x5a0 [drm]() Modules linked in: cdc_mbim cdc_ncm usbnet cdc_wdm mii i915 tg3 ata_generic yenta_socket serio_raw i2c_algo_bit ptp drm_kms_helper pata_acpi drm pps_core video CPU: 0 PID: 56 Comm: kworker/u4:1 Not tainted 4.3.5-300.fc23.i686+PAE #1 Hardware name: Dell Inc. Latitude D620 /0TD761, BIOS A10 05/16/2008 Workqueue: events_unbound async_run_entry_fn c0db2967 055306e3 00000000 f6875b80 c07326e0 00000000 f6875bb0 c046f567 c0cc2484 00000000 00000038 f852fb98 000001eb f85211ef f85211ef f6916000 f65be240 00000000 f6875bc0 c046f672 00000009 00000000 f6875c0c f85211ef Call Trace: [<c07326e0>] dump_stack+0x41/0x61 [<c046f567>] warn_slowpath_common+0x87/0xc0 [<f85211ef>] ? drm_atomic_check_only+0x4bf/0x5a0 [drm] [<f85211ef>] ? drm_atomic_check_only+0x4bf/0x5a0 [drm] [<c046f672>] warn_slowpath_null+0x22/0x30 [<f85211ef>] drm_atomic_check_only+0x4bf/0x5a0 [drm] [<f85204d9>] ? drm_atomic_set_crtc_for_plane+0x69/0x100 [drm] [<f85213b8>] ? drm_atomic_set_fb_for_plane+0x28/0xa0 [drm] [<f85212e6>] drm_atomic_commit+0x16/0x60 [drm] [<f8702697>] intel_get_load_detect_pipe+0x417/0x5f0 [i915] [<c073dfc1>] ? vsnprintf+0x2f1/0x3f0 [<f872ff10>] ? set_data+0x30/0x90 [i915] [<f873a506>] intel_tv_detect+0x106/0x660 [i915] [<f851bd70>] ? drm_get_edid+0x30/0x400 [drm] [<f8183beb>] drm_helper_probe_single_connector_modes_merge_bits+0x20b/0x480 [drm_kms_helper] [<f8183e77>] drm_helper_probe_single_connector_modes+0x17/0x20 [drm_kms_helper] [<f818f092>] drm_fb_helper_initial_config+0x72/0x3e0 [drm_kms_helper] [<c04a7b19>] ? pick_next_task_fair+0x429/0x4e0 [<f8713199>] intel_fbdev_initial_config+0x19/0x20 [i915] [<c048d7fe>] async_run_entry_fn+0x4e/0x170 [<c0485b75>] process_one_work+0x145/0x380 [<c0485de9>] worker_thread+0x39/0x430 [<c0485db0>] ? process_one_work+0x380/0x380 [<c048b126>] kthread+0xa6/0xc0 [<c0afca01>] ret_from_kernel_thread+0x21/0x30 [<c048b080>] ? kthread_worker_fn+0x130/0x130
Just coming here to say "me too", with an error essentially identical to the above, with similarly old hardware. Kernel: 4.3.5-300.fc23.x86_64 Hardware name: Dell Inc. Inspiron 1420 /0DT492, BIOS A10 12/19/2008 VGA info from lspci -nn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086 :2a02] (rev 0c) Processor: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz (family: 0x6, model: 0x17, stepping: 0x6)
*** Bug 1310060 has been marked as a duplicate of this bug. ***
I'm still seeing a similar error on the hardware described in Comment 11 after upgrading to 4.4.2-301.fc23.x86_64. But instead of being found in "drivers/gpu/drm/drm_atomic.c:491 drm_atomic_check_only+0x4bf/0x5a0 [drm]()", mine is found in "drivers/gpu/drm/drm_irq.c:1268 drm_wait_one_vblank+0x1b5/0x1c0 [drm]()". I'll see if the reporting system will let me file an additional report with my details.
*** Bug 1316218 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.