Created attachment 127741 [details] dmesg Original report: https://bugzilla.redhat.com/show_bug.cgi?id=1070009 I have ThinkPad X1 Carbon. I've plugged miniDP<->D-SUB adapter and connected monitor over D-SUB. When I plug/unplug/reboot it's giving to me kerneloops. Some of it I can't send, because they contains TAINED flag. BUT, one I've sent to RHBZ Additional info: reporter: libreport-2.1.12 WARNING: CPU: 2 PID: 974 at drivers/gpu/drm/i915/intel_display.c:9457 intel_modeset_check_state+0x688/0x7d0 [i915]() encoder's hw state doesn't match sw tracking (expected 1, found 0) Modules linked in: fuse ipt_MASQUERADE xt_CHECKSUM tun ip6t_rpfilter ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables bnep iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw iTCO_wdt iTCO_vendor_support vfat fat x86_pkg_temp_thermal coretemp kvm_intel kvm uvcvideo arc4 videobuf2_vmalloc videobuf2_memops iwldvm videobuf2_core videodev crct10dif_pclmul crc32_pclmul mac80211 media btusb crc32c_intel bluetooth cdc_mbim 6lowpan_iphc snd_hda_codec_hdmi iwlwifi ghash_clmulni_intel cdc_wdm cdc_ncm cdc_acm snd_hda_codec_realtek sdhci_pci microcode sdhci snd_hda_codec_generic cfg80211 mmc_core serio_raw snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device wmi tpm_tis snd_pcm thinkpad_acpi tpm rfkill snd_timer mei_me snd mei lpc_ich soundcore shpchp i2c_i801 mfd_core nfsd auth_rpcgss nfs_acl lockd sunrpc asix usbnet mii i915 i2c_algo_bit drm_kms_helper drm i2c_core video CPU: 2 PID: 974 Comm: Xorg Not tainted 3.14.0-0.rc4.git0.1.fc21.x86_64 #1 Hardware name: LENOVO 3444FHG/3444FHG, BIOS G6ET96WW (2.56 ) 04/29/2013 0000000000000000 00000000f108af91 ffff88021148f8d0 ffffffff816ed0d5 ffff88021148f918 ffff88021148f908 ffffffff8108a06d 0000000000000001 ffff88021148f998 ffff8800d4629ae8 ffff8802100cc000 ffff8800d4629800 Call Trace: [<ffffffff816ed0d5>] dump_stack+0x45/0x56 [<ffffffff8108a06d>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8108a0ec>] warn_slowpath_fmt+0x5c/0x80 [<ffffffffa00b0488>] intel_modeset_check_state+0x688/0x7d0 [i915] [<ffffffffa00b0665>] intel_set_mode+0x25/0x30 [i915] [<ffffffffa00b0f1b>] intel_crtc_set_config+0x7bb/0x990 [i915] [<ffffffffa0038a2d>] drm_mode_set_config_internal+0x5d/0xe0 [drm] [<ffffffffa000af21>] drm_fb_helper_set_par+0x71/0xf0 [drm_kms_helper] [<ffffffff810bbcbc>] ? resched_task+0x4c/0x60 [<ffffffff813b1847>] fb_set_var+0x197/0x440 [<ffffffff810bc7e5>] ? check_preempt_curr+0x85/0xa0 [<ffffffff810bc819>] ? ttwu_do_wakeup+0x19/0xc0 [<ffffffff810bc96d>] ? ttwu_do_activate.constprop.95+0x5d/0x70 [<ffffffff810c7d57>] ? update_curr+0x67/0x160 [<ffffffff813bd2f1>] fbcon_blank+0x1f1/0x2f0 [<ffffffff81436c28>] do_unblank_screen+0xb8/0x1f0 [<ffffffff8142c7aa>] complete_change_console+0x5a/0xe0 [<ffffffff8142d805>] vt_ioctl+0xfd5/0x1190 [<ffffffff811a219c>] ? handle_mm_fault+0x65c/0xe50 [<ffffffffa002c7f5>] ? drm_ioctl+0xf5/0x620 [drm] [<ffffffff81421279>] tty_ioctl+0x289/0xb80 [<ffffffff816f7f64>] ? __do_page_fault+0x214/0x560 [<ffffffff811fc180>] do_vfs_ioctl+0x2e0/0x4a0 [<ffffffff811fc3e1>] SyS_ioctl+0xa1/0xc0 [<ffffffff816fd4e9>] system_call_fastpath+0x16/0x1b
Reference to dmesg: it contains more than one kernel oops, but all of that related to this bug.
Please boot with drm.degug=0xe added to your kernel bootline, reproduce the issue and then attach a new, complete dmesg.
Created attachment 127811 [details] journalctl -b
I've attached `journalctl -b`, because couldn't find kernel oops in dmesg.
Link training failures, hooray. Can you please retest with latest drm-intel-nightly from http://cgit.freedesktop.org/drm-intel that should have patches to shut up things and keep the dp output working a bit better. Besides the WARNINGs, is there any issue with your dp->vga dongle?
(In reply to Daniel Vetter from comment #5) > Link training failures, hooray. > > Can you please retest with latest drm-intel-nightly from > > http://cgit.freedesktop.org/drm-intel > > that should have patches to shut up things and keep the dp output working a > bit better. Ok. I'll try tonight. > Besides the WARNINGs, is there any issue with your dp->vga dongle? I think no, because it's new from ThinkPad X1 Carbon kit
I have an x1 carbon and the mini DP->VGA dongle that came with it works just fine for me. Well, it has one issue where the VGA HPD only works one time, and then if I disconnect and reconnect the VGA connector, I actually have to disconnect+reconnect the entire dongle to detect the display. But that could be a problem of the dongle itself, since VGA HPD works just fine the first time. Otherwise the dongle seems to work without issues, and no link training failures for me. This is what is written on my mini DP->VGA dongle: Model P/N: STM STDP3100 ASM P/N: 0A 36579 FRU P/N: 03X 6601 REV: 1.3
(In reply to Ville Syrjala from comment #7) > I have an x1 carbon and the mini DP->VGA dongle that came with it works just > fine for me. Well, it has one issue where the VGA HPD only works one time, > and then if I disconnect and reconnect the VGA connector, I actually have to > disconnect+reconnect the entire dongle to detect the display. But that could > be a problem of the dongle itself, since VGA HPD works just fine the first > time. Otherwise the dongle seems to work without issues, and no link > training failures for me. > > This is what is written on my mini DP->VGA dongle: > Model P/N: STM STDP3100 > ASM P/N: 0A 36579 > FRU P/N: 03X 6601 > REV: 1.3 Where you found this parameters?
(In reply to Igor Gnatenko from comment #8) > (In reply to Ville Syrjala from comment #7) > > I have an x1 carbon and the mini DP->VGA dongle that came with it works > just > > fine for me. Well, it has one issue where the VGA HPD only works one time, > > and then if I disconnect and reconnect the VGA connector, I actually have > to > > disconnect+reconnect the entire dongle to detect the display. But that > could > > be a problem of the dongle itself, since VGA HPD works just fine the first > > time. Otherwise the dongle seems to work without issues, and no link > > training failures for me. > > > > This is what is written on my mini DP->VGA dongle: > > Model P/N: STM STDP3100 > > ASM P/N: 0A 36579 > > FRU P/N: 03X 6601 > > REV: 1.3 > Where you found this parameters? It's written on the dongle.
I've triee this dongle on windows. It works ok there....
Sorry. Forget about this bug. Will try again on Fedora with latest git.
(In reply to Igor Gnatenko from comment #11) > Sorry. Forget about this bug. Will try again on Fedora with latest git. Okay.