drm:intel_dp_start_link_train [i915] *ERROR* failed to enable link training
Submitted by Chris Murphy
Assigned to Intel GFX Bugs mailing list
Link to original bug (#109522)
Description
Summary: Often during wake from sleep there is a brief display flicker (black to GDM login screen, back to black for about 1s, back to GDM login screen), and also there is this error in red text found in dmesg/journalctl -k
Jan 31 08:37:41 flap.local kernel: [drm:intel_dp_start_link_train [i915]] ERROR failed to enable link training
The flicker is cosmetic. And I'm not sure if the red text is even related to the flicker.
Reproducible: 75%
Hardware:
HP Spectre (circa 2016), Firmware Version: F.42 Release Date: 10/25/2018, is current.
Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller])
External display: NEC MultiSync PA241W. Connection is USB-C Thunderbolt 3 to HDMI adapter, HDMI to DVI adapter, DVI cable to display.
Activity
added Community Needs Information feature: display/Other platform: SKL priority::medium severity::normal + 1 deleted label
kernel 5.0.0-0.rc4.git1.1.fc30.x86_64 is git 4aa9fc2a435a
drm.debug=0x1e is applied
These times are based on a cellphone; the laptop hasn't yet raised wifi to sync with NTP so its clock could be off by multiple seconds.
8:37:31 - approximate time spacebar is pushed to wake laptop
8:37:42 - approximate time of flicker
This journal contains everything from the time of wake through login; about 90 seconds.Attachment 143263, "journalctl":
109522-journalctl.txtacpidump > acpidump.bin
Attachment 143264, "acpidump":
109522-acpidump.bindmidecode > dmidecode.txt
Attachment 143265, "dmidecode":
109522-dmidecode.txtlspci -vvnn > lspcivvnn.txt
Attachment 143266, "lspci":
109522-lscpivvnn.txt
@l4kshmisaid:Is this issue duplicate to Bug 105998?
Actually in bug 105998 comment 4 suggests I open a new bug, as it's unclear if what I'm seeing in comment 3 is really the same problem as that bug. Anyway, I can test with i915.disable_power_well=0 if that's helpful.
5.0.0-0.rc7.git2.1 - This is linux git 2137397c92ae
wakeup and error happens at
[ 362.025567] flap.local kernel: [drm:intel_dp_start_link_train [i915]] ERROR failed to enable link trainingAttachment 143444, "dmesg":
dmesg.txtGetting this on ArchLinux with kernel 5.1.3-g7cb9c5d341b9, i7-8700k CPU, no discrete graphics card, motherboard Asus Prime Z370-A, using BIOS version Version 1002 2018/07/06 8.76 MBytes (latest BIOS being Version 2001 2019/05/15 10.31 MBytes, please don't ask me to update), intel-ucode 20190514.a-1 (ie. the MDS one), mesa 19.0.4-1, NOTE: NOT using: xf86-video-intel, libva-intel-driver, libva1-intel-driver.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop)<br> 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller<br> ```<br> <br> I think this is why I also get:<br> ```<br> $ xrandr --verbose|grep -C2 -w 85|grep --color=always Bad|head -1<br> link-status: Bad <br> <br> $ grep -A1 DP-1 /home/user/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml|grep -e 'Active' -e 'false'<br> <property name="Active" type="bool" value="false"/><br> ```<br> <br> seemingly at/after the times when monitor was turned off(or went to sleep?):<br> ```<br> [ 4373.521845] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training<br> [ 6979.762718] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training<br> ```<br> <br> Something from `Xorg.0.log`:<br> ```<br> ...<br> [ 32.021] (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) <br> ...<br> [ 2974.053] (II) modeset(0): Modeline "1280x800"x0.0 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync (49.7 kHz e)<br> [ 4374.136] (WW) modeset(0): hotplug event: connector 85's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...<br> [ 4374.719] (WW) modeset(0): hotplug event: connector 85's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...<br> [ 4378.425] (II) modeset(0): EDID vendor "GSM", prod id 23305<br> ...<br> [ 4442.760] (WW) modeset(0): hotplug event: connector 85's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...<br> ...<br> [ 4445.432] (II) modeset(0): Modeline "1280x800"x0.0 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync (49.7 kHz e)<br> [ 6980.360] (WW) modeset(0): hotplug event: connector 85's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...<br> [ 6980.926] (WW) modeset(0): hotplug event: connector 85's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...<br> [ 6980.976] (WW) modeset(0): hotplug event: connector 85's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...<br> [ 6981.172] (II) modeset(0): EDID vendor "GSM", prod id 23305<br> ...<br> [ 6990.753] (WW) modeset(0): hotplug event: connector 85's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...<br>Can't manually reproduce it, I tried turning monitor off, then back on; tried:
sleep 1; xset dpms force suspend; sleep 1; xset dpms force off; sleep 1; xset dpms force standby<br> setterm --blank force<br> ```<br> <br> They all seemed to work so far, so the dmesg output with this patch:<br> ```diff<br> $ git diff drivers/gpu/drm/i915/intel_dp_link_training.c|tee<br> diff --git a/drivers/gpu/drm/i915/intel_dp_link_training.c b/drivers/gpu/drm/i915/intel_dp_link_training.c<br> index b59c87daa4f7..e69b2198af89 100644<br> --- a/drivers/gpu/drm/i915/intel_dp_link_training.c<br> +++ b/drivers/gpu/drm/i915/intel_dp_link_training.c<br> @@ -87,6 +87,7 @@ intel_dp_set_link_train(struct intel_dp *intel_dp,<br> ret = drm_dp_dpcd_write(&intel_dp->aux, DP_TRAINING_PATTERN_SET,<br> buf, len);<br> <br> + DRM_ERROR("ret=%d len=%d\n", ret, len);<br> return ret == len;<br> }<br> <br> ```<br> <br> apparently right after the monitor turns on, I get these 5,5,1 each time on dmesg:<br> ```<br> $ dmesg --level err<br> [ 3.844322] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 3.846020] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 3.848732] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=1 len=1<br> [ 56.871626] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 56.873573] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 56.874693] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=1 len=1<br> [ 58.212665] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 58.214381] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 58.217124] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=1 len=1<br> [ 103.393851] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 103.395610] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 103.398358] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=1 len=1<br> ```<br> <br> So this is when it works normally!<br> <br> When it doesn't work..., I'll have to update in a next comment when I hit it again. Curious what ret&len I'll get.ok I got it:
- first turn off monitor
- while monitor is off, run that
monoffscript from the prev. comment, yes this:
sleep 1; xset dpms force suspend; sleep 1; xset dpms force off; sleep 1; xset dpms force standby<br> setterm --blank force<br> ```<br> 3. wait a few seconds to be sure<br> 4. press Ctrl key to wake up desktop<br> 5. turn on monitor<br> <br> got:<br> ```<br> [ 694.869217] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=-110 len=5<br> [ 694.869243] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training<br> [ 695.138593] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=-110 len=1<br> [ 696.768921] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 696.770645] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 696.773386] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=1 len=1<br> ```<br> <br> Ok I tried it again, but left 10 seconds before actually doing step 5:<br> <br> ```<br> [ 887.319215] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=-110 len=5<br> [ 887.319254] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training<br> [ 887.588579] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=-110 len=1<br> [ 898.050275] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 898.052012] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 898.054707] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=1 len=1<br> ```<br> <br> So looks like link is Good afterwards(after step 5 that is), but something keeps track of link as being still Bad (via xrandr) if it once was Bad (10 seconds ago).- first turn off monitor
linux-stable/usr/include/asm-generic/errno.h
#define ETIMEDOUT 110 /* Connection timed out */
that's the -110 for the ret
it obviously times out because the monitor is physically(from the button) off.
But as soon as it's turned on, all is good again, however thatxrandr --verbosestill reports connection as Bad... unsure if this is an issue in something else.tl;dr: for some reason running xrandr every second prevents this from happening.
ok the only reason that I couldn't reproduce it is because(/when) I was running the following in another terminal:$ while true; do (date; cat /proc/uptime; xrandr --verbose|grep -w 85 -C 2|grep 'link-status: Bad'|| echo "good"); sleep 1; done<br> ```<br> <br> So while that is running, there's no way I can reproduce it with Comment 13 steps!<br> As soon as I C-c (aka stop) it, bam, steps are good to reproduce.<br> Start that while again and again can't reproduce!<br> <br> So, I guess that's a workaround?ok I have another way to reproduce that bypasses the xrandr run, and it involves switching step 1 with step 2 in Comment 13. So with this, it doesn't matter if xrandr is ran in a
whileloop, the -110 will happen nonetheless. Kernel tested 5.1.10
The monitor is LG(something) and is connected via the DisplayPort to the ASUS Prime Z370-A motherboard connector and I've no dedicated gfx card, it's using the integrated one from Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (oh I see I've mentioned this in Comment 11 already, the BIOS is the same version still because the next one is probably trojaned xD)
Ok so to summarize, steps from Comment 13 will only work(to reproduce the issue) if you're not running xrandr in a while loop like:
$ while true; do (date; cat /proc/uptime; xrandr --verbose --dryrun --nograb|grep -w 85 -C 2|grep 'link-status: Bad'|| echo "good"); sleep 1; done
but, if you insist on running xrandr like that(or even without --dryrun --nograb) then simply switching step 1 with step 2(aka run 'monoff' first then turn off monitor) then xrandr will have no effect and the issue can be reproduced 100% (or so it seems, to me).
By reproduce the issue I mean:
[ 3946.388708] [drm:intel_dp_set_link_train [i915]] ERROR ret=-110 len=5
[ 3946.388736] [drm:intel_dp_start_link_train [i915]] ERROR failed to enable link training
[ 3946.658135] [drm:intel_dp_set_link_train [i915]] ERROR ret=-110 len=1
...
[ 3950.951159] [drm:intel_dp_set_link_train [i915]] ERROR ret=5 len=5
[ 3950.952869] [drm:intel_dp_set_link_train [i915]] ERROR ret=5 len=5
[ 3950.955573] [drm:intel_dp_set_link_train [i915]] ERROR ret=1 len=1
And in the case when xrandr is ran in awhileloop using Comment 13 steps (without swapping steps 1 and 2), only the last 3 dmesg messages from above appear, meaning the issue doesn't occurr.
I'm up for trying any patches/tries that you want me to test, even if they lockup/oops/panic, I have kdump set up and we'll get nice stacktrace and stuff;-) just like in this bug for example: https://bugzilla.kernel.org/show_bug.cgi?id=203849
Cheers!i915.disable_power_well=0does not help, ie.:
$ dmesg|grep -e '0000:00:02.0' -e 'i915'<br> [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux-stable root=UUID=2b8b9ab8-7ac5-4586-aa42-d7ffb12de92a rw root_trim=yes rd.luks.allow-discards rd.luks.options=discard ipv6.disable=1 ipv6.disable_ipv6=1 ipv6.autoconf=0 loglevel=15 log_buf_len=16M ignore_loglevel printk.always_kmsg_dump=y printk.time=y printk.devkmsg=on mminit_loglevel=4 memory_corruption_check=1 fbcon=scrollback:4096k fbcon=font:ProFont6x11 net.ifnames=0 nolvm dobtrfs console=tty1 earlyprintk=vga audit=0 systemd.log_target=kmsg systemd.journald.forward_to_console=1 enforcing=0 udev.children-max=1256 rd.udev.children-max=1256 nohz=on oops=panic crashkernel=256M panic=0 page_poison=1 psi=1 sysrq_always_enabled random.trust_cpu=off logo.nologo lpj=0 mce=bootlog reboot=force,cold noexec=on nohibernate scsi_mod.use_blk_mq=1 consoleblank=120 mitigations=off nospectre_v1 nospectre_v2 spectre_v2=off nospec_store_bypass_disable kvm-intel.vmentry_l1d_flush=never l1tf=off nopti pti=off no_stf_barrier noibrs noibpb ssbd=force-off spectre_v2_user=off noretpoline mds=off rd.log=all noefi cpuidle.governor=menu zram.num_devices=3 zswap.enabled=0 zswap.same_filled_pages_enabled=1 zswap.compressor=zstd zswap.max_pool_percent=40 zswap.zpool=z3fold i915.alpha_support=1 i915.fastboot=1 i915.disable_power_well=0<br> [ 0.351304] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-stable root=UUID=2b8b9ab8-7ac5-4586-aa42-d7ffb12de92a rw root_trim=yes rd.luks.allow-discards rd.luks.options=discard ipv6.disable=1 ipv6.disable_ipv6=1 ipv6.autoconf=0 loglevel=15 log_buf_len=16M ignore_loglevel printk.always_kmsg_dump=y printk.time=y printk.devkmsg=on mminit_loglevel=4 memory_corruption_check=1 fbcon=scrollback:4096k fbcon=font:ProFont6x11 net.ifnames=0 nolvm dobtrfs console=tty1 earlyprintk=vga audit=0 systemd.log_target=kmsg systemd.journald.forward_to_console=1 enforcing=0 udev.children-max=1256 rd.udev.children-max=1256 nohz=on oops=panic crashkernel=256M panic=0 page_poison=1 psi=1 sysrq_always_enabled random.trust_cpu=off logo.nologo lpj=0 mce=bootlog reboot=force,cold noexec=on nohibernate scsi_mod.use_blk_mq=1 consoleblank=120 mitigations=off nospectre_v1 nospectre_v2 spectre_v2=off nospec_store_bypass_disable kvm-intel.vmentry_l1d_flush=never l1tf=off nopti pti=off no_stf_barrier noibrs noibpb ssbd=force-off spectre_v2_user=off noretpoline mds=off rd.log=all noefi cpuidle.governor=menu zram.num_devices=3 zswap.enabled=0 zswap.same_filled_pages_enabled=1 zswap.compressor=zstd zswap.max_pool_percent=40 zswap.zpool=z3fold i915.alpha_support=1 i915.fastboot=1 i915.disable_power_well=0<br> [ 2.757573] pci 0000:00:02.0: [8086:3e92] type 00 class 0x030000<br> [ 2.757741] pci 0000:00:02.0: reg 0x10: [mem 0xde000000-0xdeffffff 64bit]<br> [ 2.757906] pci 0000:00:02.0: reg 0x18: [mem 0xc0000000-0xcfffffff 64bit pref]<br> [ 2.758133] pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f]<br> [ 2.758318] device: '0000:00:02.0': device_add<br> [ 2.758446] bus: 'pci': add device 0000:00:02.0<br> [ 2.758609] PM: Adding info for pci:0000:00:02.0<br> [ 2.904428] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]<br> [ 5.653546] bus: 'pci': add driver i915<br> [ 5.653711] bus: 'pci': driver_probe_device: matched device 0000:00:02.0 with driver i915<br> [ 5.653938] bus: 'pci': really_probe: probing driver i915 with device 0000:00:02.0<br> [ 5.654166] i915 0000:00:02.0: no default pinctrl state<br> [ 5.654329] i915 0000:00:02.0: runtime IRQ mapping not provided by arch<br> [ 5.657558] i2c i2c-1: adapter [i915 gmbus dpc] registered<br> [ 5.658289] i2c i2c-2: adapter [i915 gmbus dpb] registered<br> [ 5.658975] i2c i2c-3: adapter [i915 gmbus dpd] registered<br> [ 5.659613] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)<br> [ 5.944140] device: 'i915': device_add<br> [ 5.944304] bus: 'event_source': add device i915<br> [ 5.944466] PM: Adding info for event_source:i915<br> [ 5.948208] [drm] Initialized i915 1.6.0 20190207 for 0000:00:02.0 on minor 0<br> [ 5.952289] i915 0000:00:02.0: adding component (ops i915_audio_component_bind_ops [i915])<br> [ 5.952878] snd_hda_intel 0000:00:1f.3: found component 0000:00:02.0, duplicate 0<br> [ 5.953119] snd_hda_intel 0000:00:1f.3: binding 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])<br> [ 5.953732] snd_hda_intel 0000:00:1f.3: Linked as a consumer to 0000:00:02.0<br> [ 5.953909] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])<br> [ 5.954339] driver: 'i915': driver_bound: bound to device '0000:00:02.0'<br> [ 5.954507] bus: 'pci': really_probe: bound device 0000:00:02.0 to driver i915<br> [ 5.995964] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 5.997663] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 6.000374] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=1 len=1<br> [ 6.062740] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device<br> ```<br> <br> ```<br> ...<br> [ 5.648405] Setting dangerous option disable_power_well - tainting kernel<br> ...<br> [ 140.419975] gpg-agent[1102]: handler 0x7a423a6ff700 for fd 10 started<br> [ 140.477095] gpg-agent[1102]: handler 0x7a423a6ff700 for fd 10 terminated<br> [ 200.482440] gpg-agent[1102]: handler 0x7a4239efe700 for fd 10 started<br> [ 200.543903] gpg-agent[1102]: handler 0x7a4239efe700 for fd 10 terminated<br> [ 201.779269] user[2626]: '/home/user/bin/monoff' is executing: 'sleep 1'<br> [ 202.782765] user[2633]: '/home/user/bin/monoff' is executing: 'xset dpms force suspend'<br> [ 202.886388] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D0<br> [ 202.898494] snd_hda_intel 0000:00:1f.3: PME# disabled<br> [ 202.911455] snd_hda_intel 0000:00:1f.3: PME# enabled<br> [ 202.923592] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D3hot<br> [ 202.946158] user[2635]: '/home/user/bin/monoff' is executing: 'sleep 1'<br> [ 203.900374] user[2642]: '/home/user/bin/monoff' is executing: 'xset dpms force off'<br> [ 204.009111] user[2644]: '/home/user/bin/monoff' is executing: 'sleep 1'<br> [ 205.015169] user[2651]: '/home/user/bin/monoff' is executing: 'xset dpms force standby'<br> [ 205.124020] user[2653]: '/home/user/bin/monoff' is executing: 'setterm --blank force'<br> [ 220.715002] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=-110 len=5<br> [ 220.715016] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training<br> [ 220.984404] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=-110 len=1<br> [ 220.984787] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D0<br> [ 220.996593] snd_hda_intel 0000:00:1f.3: PME# disabled<br> [ 221.009573] snd_hda_intel 0000:00:1f.3: PME# enabled<br> [ 221.022464] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D3hot<br> [ 221.320977] i2c i2c-2: NAK from device addr 0x50 msg #0<br> [ 221.324827] i2c i2c-1: NAK from device addr 0x50 msg #0<br> [ 221.328677] i2c i2c-3: NAK from device addr 0x50 msg #0<br> [ 221.600815] i2c i2c-2: NAK from device addr 0x50 msg #0<br> [ 221.604597] i2c i2c-1: NAK from device addr 0x50 msg #0<br> [ 221.608409] i2c i2c-3: NAK from device addr 0x50 msg #0<br> [ 221.904445] i2c i2c-2: NAK from device addr 0x50 msg #0<br> [ 221.908255] i2c i2c-1: NAK from device addr 0x50 msg #0<br> [ 221.912065] i2c i2c-3: NAK from device addr 0x50 msg #0<br> [ 222.183955] i2c i2c-2: NAK from device addr 0x50 msg #0<br> [ 222.187592] i2c i2c-1: NAK from device addr 0x50 msg #0<br> [ 222.191224] i2c i2c-3: NAK from device addr 0x50 msg #0<br> [ 222.544129] i2c i2c-2: NAK from device addr 0x50 msg #0<br> [ 222.547899] i2c i2c-1: NAK from device addr 0x50 msg #0<br> [ 222.551550] i2c i2c-3: NAK from device addr 0x50 msg #0<br> [ 222.585170] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D0<br> [ 222.596599] snd_hda_intel 0000:00:1f.3: PME# disabled<br> [ 222.609442] snd_hda_intel 0000:00:1f.3: PME# enabled<br> [ 222.621440] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D3hot<br> [ 232.057307] i2c i2c-2: NAK from device addr 0x50 msg #0<br> [ 232.366672] i2c i2c-2: NAK from device addr 0x50 msg #0<br> [ 232.378634] i2c i2c-2: NAK from device addr 0x50 msg #0<br> [ 232.382283] i2c i2c-1: NAK from device addr 0x50 msg #0<br> [ 232.385931] i2c i2c-3: NAK from device addr 0x50 msg #0<br> [ 232.397218] i2c i2c-2: NAK from device addr 0x50 msg #0<br> [ 232.400973] i2c i2c-1: NAK from device addr 0x50 msg #0<br> [ 232.404723] i2c i2c-3: NAK from device addr 0x50 msg #0<br> [ 232.443129] i2c i2c-2: NAK from device addr 0x50 msg #0<br> [ 232.446689] i2c i2c-1: NAK from device addr 0x50 msg #0<br> [ 232.450356] i2c i2c-3: NAK from device addr 0x50 msg #0<br> [ 232.457487] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 232.459178] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=5 len=5<br> [ 232.461879] [drm:intel_dp_set_link_train [i915]] *ERROR* ret=1 len=1<br> [ 232.462209] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D0<br> [ 232.473474] snd_hda_intel 0000:00:1f.3: PME# disabled<br> [ 232.486275] snd_hda_intel 0000:00:1f.3: PME# enabled<br> [ 232.497460] snd_hda_intel 0000:00:1f.3: power state changed by ACPI to D3hot<br> [ 260.543548] gpg-agent[1102]: handler 0x7a423a6ff700 for fd 10 started<br> [ 260.627503] gpg-agent[1102]: handler 0x7a423a6ff700 for fd 10 terminated<br> [ 301.490986] user[3150]: okiedokie<br> <br> <br> ```<br> <br> at [ 220.715002] I pressed Ctrl key to wake up the software but the monitor was still off! got the ret=-110 messages.<br> 10 seconds later(so at [ 232.057307] I'm guessing) I turned on monitor, got the normal ret=5 messages.<br> <br> `drm.debug=0x1e` spews just too many messages, not sure what to do with it... not even sure if it would log all of them during the test or they would just get overwritten due to the ring property of the dmesg(kmsg?) buffer. Maybe I'll retry.
