Description of problem: rebooted and kernel-4.9.0-0.rc0.git1.2.fc26 stopped loading (I noticed a stracktrace but it dissapeared really fast). I had to do hard reset and booted to 4.8.0-0.rc8.git0.1.fc26.x86_64 and found this stacktrace in the logs. Additional info: reporter: libreport-2.8.0.15.g4cb8 WARNING: CPU: 0 PID: 4 at lib/kobject.c:244 kobject_add_internal+0x101/0x320 kobject_add_internal failed for card1-DP-3 (error: -2 parent: card1) Modules linked in: nouveau(+) i915(+) mxm_wmi ttm crct10dif_pclmul crc32_pclmul crc32c_intel i2c_algo_bit drm_kms_helper ghash_clmulni_intel drm e1000e serio_raw sdhci_pci sdhci mmc_core ptp pps_core wmi fjes video CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.8.0-0.rc8.git0.1.fc26.x86_64 #1 Hardware name: LENOVO 20EGS0R60R/20EGS0R60R, BIOS GNET72WW (2.20 ) 02/26/2015 Workqueue: events_long drm_dp_mst_link_probe_work [drm_kms_helper] 0000000000000286 0000000027859927 ffff949e2c29b900 ffffffff913e588d ffff949e2c29b950 0000000000000000 ffff949e2c29b940 ffffffff910a0e4b 000000f42c269f00 ffff949e275db010 0000000000000000 ffff949e27642810 Call Trace: [<ffffffff913e588d>] dump_stack+0x63/0x86 [<ffffffff910a0e4b>] __warn+0xcb/0xf0 [<ffffffff910a0ecf>] warn_slowpath_fmt+0x5f/0x80 [<ffffffff913e8231>] kobject_add_internal+0x101/0x320 [<ffffffff913f2137>] ? vsnprintf+0x2d7/0x500 [<ffffffff913e8975>] kobject_add+0x75/0xd0 [<ffffffff9152a643>] ? device_private_init+0x23/0x70 [<ffffffff9152a804>] device_add+0x174/0x660 [<ffffffff9152aee0>] device_create_groups_vargs+0xe0/0xf0 [<ffffffff9152afc6>] device_create_with_groups+0x46/0x60 [<ffffffffc01ab414>] ? drm_modeset_lock+0x84/0xd0 [drm] [<ffffffffc0197fe6>] drm_sysfs_connector_add+0x56/0xb0 [drm] [<ffffffffc019b64b>] drm_connector_register+0x2b/0xb0 [drm] [<ffffffffc03587a1>] intel_dp_register_mst_connector+0x41/0x50 [i915] [<ffffffffc0232071>] drm_dp_add_port+0x231/0x4a0 [drm_kms_helper] [<ffffffffc035d6fd>] ? intel_dp_aux_transfer+0x13d/0x210 [i915] [<ffffffffc022aebe>] ? drm_dp_dpcd_access+0xce/0x110 [drm_kms_helper] [<ffffffffc022af1b>] ? drm_dp_dpcd_write+0x1b/0x20 [drm_kms_helper] [<ffffffffc0232467>] drm_dp_send_link_address+0x187/0x220 [drm_kms_helper] [<ffffffff9110f972>] ? add_timer_on+0xe2/0x1c0 [<ffffffffc02325ab>] drm_dp_check_and_send_link_address+0xab/0xb0 [drm_kms_helper] [<ffffffffc0232607>] drm_dp_mst_link_probe_work+0x57/0xb0 [drm_kms_helper] [<ffffffff910baa34>] process_one_work+0x184/0x430 [<ffffffff910bad2e>] worker_thread+0x4e/0x480 [<ffffffff910bace0>] ? process_one_work+0x430/0x430 [<ffffffff910c0bc8>] kthread+0xd8/0xf0 [<ffffffff9180277f>] ret_from_fork+0x1f/0x40 [<ffffffff910c0af0>] ? kthread_worker_fn+0x180/0x180
Created attachment 1207934 [details] File: dmesg
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.