Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
A number of employees at my company have been reporting an issue with i915 that appears to still be present on the latest upstream Linux kernel (as of writing this, v5.15-rc7), where after a number of DPMS on/off cycles with an external HDMI display the LSPCON appears to stop responding and die. This issue has been observed on a ThinkPad P1 3rd Gen, and if there's any questions about firmware issues here I should be able to get Lenovo involved.
I've attached a dmesg, note that the dmesg does appear to be truncated - however it still appears to show the LSPCON failure so I don't think it should be an issue. ounsal-dmesg. As well, the CPU here is a i7-10850H so the GPU should be CML.
If you need any more info let me know, and I'll be happy to help.
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
I haven't heard anything back from the person who reported this to me originally so I would assume yes. I will double check though.
Let me know if there's any info they can give you to help figure this out
I'm running into this issue. Let me know if you need any more information.
Tested against HEAD (ae085d7f9365de7da27ab5c0d16b12d51ea7fca9), will test on drm-tip and update.
The display I can trigger this bug with is 1440p native. If it's plugged in to a gnome-shell session and driven at 1080p things work fine. Switching to 1440p, switching to a TTY and booting with it plugged in all trigger the bug.
@Leautp Can you share the boot logs, along with the dmesg logs when the issue occur.
There are two LSPCON chips with these platforms one from MCA other from Parade.
Boot logs will help understand if there is any issue during initialization.
Also request you to get the i915_display_info which will help to the F/W version that is flashed.
cat /sys/kernel/debug/dri/0/i915_display_info
@Leautp For drm logs the drm.debug level should be change in the linux command line. Can you please add drm.debug=0x10e log_buf_len=1M to Linux commandline and then capture the boot and dmesg logs. This will help to get drm logs along with DPCD read and writes right from boot.
Also request you to capture i915_display_info when you have connected the display through hdmi cable.
Sorry to have missed to share this information earlier.
Thanks @Leautp I see from the logs :
The LSPCON chip is Parade with FW version : 8.53
The issue is after resume, we are expecting the LSPCON to settle in PCON mode, but it seems to remain in LS mode.
This seem to be like an earlier issue https://bugs.freedesktop.org/show_bug.cgi?id=107503.
At that time this seem to be fixed by increasing the timeout to 400ms.
@swick thanks for trying this out. Can you also share the dmesg logs and display info.
Also wanted to see if this issue is specific to certain LsPCON and F/W version, is it the latest f/w revision?
@jani I was wondering, what should be right amount of timeout, I had just given an arbitrary value of 1000msec, increasing from 400msec, which itself was increased from 100msec.
The patch also mentions that with 1000msec timeout, there are concerns about delaying valid timeout cases. https://patchwork.freedesktop.org/patch/245162/?series=48414&rev=1
Ran into some weirdness when I tried to get the logs and decided to test the patch again. With the patch when the display is plugged in when the shell has started everything works fine, unplugging and re-plugging multiple times all without any issue. dmesg_drm_tip_patch_display_added.log
When booting with the display plugged in the display is flickering slightly but then the shell starts with the right mode and without glitches. Re-plugging the display messes up the mode though. dmesg_drm_tip_patch_display_boot_replugged.log
@swick There has been some fixes in the AUX timeout when trying during AUX power down/up cycle. Can you please try on the latest drm-tip and share the logs?