Description of problem: After I updated my system, it occured Additional info: reporter: libreport-2.9.5 WARNING: CPU: 2 PID: 106 at drivers/gpu/drm/i915/intel_display.c:10429 intel_plane_atomic_calc_changes+0x1cb/0x5f0 [i915] Modules linked in: i915 rtsx_usb_sdmmc mmc_core i2c_algo_bit rtsx_usb drm_kms_helper crct10dif_pclmul crc32_pclmul drm crc32c_intel r8169 ghash_clmulni_intel serio_raw mii i2c_hid video CPU: 2 PID: 106 Comm: kworker/u16:1 Not tainted 4.18.9-200.fc28.x86_64 #1 Hardware name: Dell Inc. Latitude 3490/04HCMV, BIOS 1.5.0 03/16/2018 Workqueue: events_unbound async_run_entry_fn RIP: 0010:intel_plane_atomic_calc_changes+0x1cb/0x5f0 [i915] Code: 00 84 c0 0f 84 c7 fe ff ff 48 c7 c6 a8 73 41 c0 48 c7 c7 a5 66 41 c0 4c 89 5c 24 20 44 88 54 24 18 88 54 24 10 e8 6f 49 d3 f5 <0f> 0b 31 c0 4c 8b 5c 24 20 44 0f b6 54 24 18 0f b6 54 24 10 e9 8d RSP: 0018:ffff98fd427ab928 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff8ab927727200 RCX: 0000000000000006 RDX: 0000000000000007 RSI: 0000000000000002 RDI: ffff8ab93f496930 RBP: ffff8ab926df5800 R08: 0000000b090e431a R09: 000000003fbe8c58 R10: ffffffffb79a19c0 R11: 000000000002f874 R12: ffff8ab92687b400 R13: 0000000000000001 R14: ffff8ab92690f000 R15: ffff8ab92cbe4000 FS: 0000000000000000(0000) GS:ffff8ab93f480000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005574ee701070 CR3: 000000039b20a004 CR4: 00000000003606e0 Call Trace: intel_plane_atomic_check_with_state+0x16c/0x240 [i915] drm_atomic_helper_check_planes+0xa0/0x1b0 [drm_kms_helper] intel_atomic_check+0x4c1/0x10e0 [i915] drm_atomic_check_only+0x360/0x510 [drm] drm_atomic_commit+0x13/0x50 [drm] restore_fbdev_mode_atomic+0x1a8/0x210 [drm_kms_helper] drm_fb_helper_restore_fbdev_mode_unlocked+0x45/0x90 [drm_kms_helper] drm_fb_helper_set_par+0x29/0x50 [drm_kms_helper] intel_fbdev_set_par+0x16/0x60 [i915] fbcon_init+0x488/0x600 visual_init+0xd5/0x130 do_bind_con_driver+0x1d9/0x2b0 do_take_over_console+0x120/0x180 do_fbcon_takeover+0x58/0xb0 notifier_call_chain+0x47/0x70 blocking_notifier_call_chain+0x3e/0x60 register_framebuffer+0x250/0x340 __drm_fb_helper_initial_config_and_unlock+0x213/0x420 [drm_kms_helper] ? __switch_to_asm+0x34/0x70 intel_fbdev_initial_config+0x14/0x30 [i915] 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 Potential duplicate: bug 1571911
Created attachment 1490869 [details] File: dmesg
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.
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.