Hide Forgot
Description of problem: I docked the laptop. Additional info: reporter: libreport-2.6.4 general protection fault: 0000 [#1] SMP Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack fuse tun bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables ccm bnep intel_rapl iosf_mbi x86_pkg_temp_thermal coretemp arc4 kvm_intel kvm iTCO_wdt iTCO_vendor_support vfat fat iwlmvm irqbypass mac80211 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi iwlwifi uvcvideo snd_hda_intel videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_hda_codec videobuf2_core cfg80211 rtsx_pci_ms v4l2_common joydev btusb videodev btrtl snd_hda_core btbcm i2c_i801 intel_pch_thermal snd_hwdep btintel memstick snd_seq media lpc_ich bluetooth shpchp snd_seq_device snd_pcm mei_me mei snd_timer thinkpad_acpi wmi snd soundcore rfkill tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt i915 rtsx_pci_sdmmc mmc_core crct10dif_pclmul i2c_algo_bit crc32_pclmul drm_kms_helper crc32c_intel drm e1000e serio_raw rtsx_pci ptp pps_core fjes video CPU: 0 PID: 10586 Comm: Xorg Not tainted 4.4.4-301.fc23.x86_64 #1 Hardware name: LENOVO 20BWS1KY0H/20BWS1KY0H, BIOS JBET49WW (1.14 ) 05/21/2015 task: ffff8802b3d4bc00 ti: ffff88027aa14000 task.ti: ffff88027aa14000 RIP: 0010:[<ffffffffa0112edd>] [<ffffffffa0112edd>] drm_dp_payload_send_msg.isra.14+0x10d/0x1b0 [drm_kms_helper] RSP: 0018:ffff88027aa17a98 EFLAGS: 00010286 RAX: ffff8802b3d4bc00 RBX: 6c28276c933cf685 RCX: ffff88034c19b908 RDX: 0000000080000000 RSI: 6c28276c933cf685 RDI: ffff88034c19b908 RBP: ffff88027aa17ad8 R08: 00000000c305017d R09: ffffffffa0112e86 R10: ffffea000c3e8000 R11: 0000000000000000 R12: 000000000000002b R13: ffff88009702dc30 R14: 0000000000000001 R15: ffff88034c19b650 FS: 00007f1daa4eba00(0000) GS:ffff88035dc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f4530e2eb90 CR3: 000000032ecf1000 CR4: 00000000003406f0 Stack: ffff88027aa17aff ffff88034c19b908 4dc5feb6c305017d 0000000000000001 ffff88034ae57450 ffff88034c19b650 0000000000000001 ffff88034c19b9a0 ffff88027aa17b18 ffffffffa01134d8 ffff88027aa17b18 ffff88003f9c0000 Call Trace: [<ffffffffa01134d8>] drm_dp_update_payload_part2+0xc8/0x130 [drm_kms_helper] [<ffffffffa020c6e7>] intel_mst_enable_dp+0xe7/0x110 [i915] [<ffffffffa01eec01>] haswell_crtc_enable+0x421/0x870 [i915] [<ffffffffa01ea6e2>] intel_atomic_commit+0x492/0x1420 [i915] [<ffffffffa00b81be>] ? drm_atomic_check_only+0x18e/0x590 [drm] [<ffffffffa00b85f7>] drm_atomic_commit+0x37/0x60 [drm] [<ffffffffa01174c6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper] [<ffffffffa00a7b62>] drm_mode_set_config_internal+0x62/0x100 [drm] [<ffffffffa00abee2>] drm_mode_setcrtc+0x3d2/0x4f0 [drm] [<ffffffffa009d602>] drm_ioctl+0x152/0x540 [drm] [<ffffffffa00abb10>] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [<ffffffff8133fc2c>] ? selinux_file_ioctl+0x10c/0x1c0 [<ffffffff81241168>] do_vfs_ioctl+0x298/0x480 [<ffffffff813374a3>] ? security_file_ioctl+0x43/0x60 [<ffffffff812413c9>] SyS_ioctl+0x79/0x90 [<ffffffff810b31de>] ? SyS_rt_sigprocmask+0x8e/0xc0 [<ffffffff817a012e>] entry_SYSCALL_64_fastpath+0x12/0x71 Code: 41 5e 41 5f 5d c3 49 8d 8f b8 02 00 00 49 8b 5d 00 48 89 cf 48 89 4d c8 e8 f1 ae 68 e1 49 83 bf e8 02 00 00 00 48 8b 4d c8 74 54 <48> 8b 43 28 48 85 c0 74 4b 48 3b 58 20 74 30 48 8b 98 30 04 00 RIP [<ffffffffa0112edd>] drm_dp_payload_send_msg.isra.14+0x10d/0x1b0 [drm_kms_helper] RSP <ffff88027aa17a98>
Created attachment 1137325 [details] File: dmesg
I got exactly the same backtrace twice in the last couple of days after updating from kernel-4.4.3-300.fc23.x86_64 to kernel-4.4.5-300.fc23.x86_64. The steps differ: Dock a suspended x240, unsuspend it, Xfce pops up a display-settings menu, activate one of the previously inactive displays, everything freezes.
Created attachment 1141133 [details] stack trace I have the same problem after upgrading to f23 with kernel-4.4.4-301.fc23.x86_64 (unfortunately, downgrading back to kernel-4.4.4-200.fc22.x86_64 or upgrading to kernel-4.5.0-0.rc7.git0.2.fc24.x86_64 doesn't help). The scenario is similar to the previous ones - I dock my laptop and call xrandr, to connect external monitors, which results in frozen system.
(In reply to Frantisek Sumsal from comment #3) > I have the same problem after upgrading to f23 with > kernel-4.4.4-301.fc23.x86_64 (unfortunately, downgrading back to > kernel-4.4.4-200.fc22.x86_64 or upgrading to > kernel-4.5.0-0.rc7.git0.2.fc24.x86_64 doesn't help). For me, downgrading to 4.4.3-300.fc23.x86_64 helped.
(In reply to Tomas Heinrich from comment #4) > For me, downgrading to 4.4.3-300.fc23.x86_64 helped. Thank you, Tomas, downgrading to 4.4.3-300.fc23.x86_64 indeed helped.
Created attachment 1145155 [details] Stack trace from Lenovo W541 with same issue
Comment on attachment 1145155 [details] Stack trace from Lenovo W541 with same issue I'm also having the same issue; This is on a Lenovo W541 laptop. I dock and boot up the laptop, set up my external displays, then undock, enable the built-in display and close the lid. When I dock it again, I go to set up my external displays and it hangs with the attached stack trace.
Also, I would love to downgrade my kernel to 4.4.3-300.fc23.x86_64, but I can't find the RPMs anywhere. Could someone link those so I can at least work around the issue until it's addressed? This is extraordinarily disruptive for me. :(
I used RPMs from this koji build [1]. Then I just downloaded all the RPMs with koji download-build 739250 and force-installed them with rpm --force -i --nodeps kernel*.x86_64.rpm, because dnf somehow doesn't like installing older kernels. There's probably a better way, but it worked for me. Hope it helps. [1] http://koji.fedoraproject.org/koji/buildinfo?buildID=739250
(In reply to Frantisek Sumsal from comment #9) Thanks, this seems to have worked for me. I was able to downgrade through dnf with these steps: * booting into an older kernel * dnf remove kernel-4.4.6-300.fc23.x86_64 kernel-devel-4.4.6-300.fc23.x86_64 kernel-modules-4.4.6-300.fc23.x86_64 kernel-core-4.4.6-300.fc23.x86_64 * dnf install ./kernel-core-4.4.3-300.fc23.x86_64 ./kernel-modules-4.4.3-300.fc23.x86_64 ./kernel-4.4.3-300.fc23.x86_64 * dnf downgrade ./kernel-tools-libs-4.4.3-300.fc23.x86_64 ./kernel-tools-4.4.3-300.fc23.x86_64 * dnf downgrade ./kernel-headers-4.4.3-300.fc23.x86_64 So far so good.
Additional data point, I also saw this problem while booted into kernel-4.4.6-200.fc22.x86_64.
Description of problem: Probably happened while docking/undocking my laptop Version-Release number of selected component: kernel Additional info: reporter: libreport-2.6.4 cmdline: BOOT_IMAGE=/vmlinuz-4.4.8-300.fc23.x86_64 root=UUID=e5007330-6c61-43b0-8b65-2796ba7ea391 ro vconsole.font=latarcyrheb-sun16 rhgb quiet LANG=de_DE.UTF-8 kernel: 4.4.8-300.fc23.x86_64 runlevel: N 5 type: Kerneloops Truncated backtrace: #1 drm_dp_payload_send_msg.isra.14 in drm_kms_helper #2 drm_dp_update_payload_part2 in drm_kms_helper #3 intel_mst_enable_dp in i915 #4 haswell_crtc_enable in i915 #5 ? intel_frontbuffer_flush in i915 #6 intel_atomic_commit in i915 #7 ? drm_atomic_check_only in drm #8 drm_atomic_commit in drm #9 restore_fbdev_mode in drm_kms_helper #10 drm_fb_helper_restore_fbdev_mode_unlocked in drm_kms_helper
New kernel for Fedora rawhide (4.6 RC-6) seems to be working bit better on my laptop. Still sometimes after docking/undocking stay black screen, but now works all monitors connected to dock station and works properly and I haven't got any kernel panic recently.
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.