Unigine-Heaven-3.0 Command: "./heaven_x64 -project Heaven -video_app opengl -data_path ../ -engine_config ../data/heaven_4.0.cfg -system_script demos/heaven/unigine.cpp -sound_app openal -video_fullscreen 1 -video_mode -1 -video_width 1920 -video_height 1080 -extern_define PHORONIX,RELEASE"
ENV1: OS: ubuntu 18.04 lts Kernel: https://github.com/rantogno/linux/commits/drm-tip-CI_DRM_7923 Mesa: https://gitlab.freedesktop.org/rantogno/mesa/-/commits/tgl-wip-2020-02-26 Build parameter: meson configure build -Dgallium-drivers="swrast,iris" -Dvulkan-drivers=intel -Dbuildtype=release -Dprefix=/usr
ENV2: OS: ubuntu 18.04 lts Kernel: https://github.com/intel/linux-intel-lts/commit/0d758b0d30f387630ee28d912b7516611a07c841 Mesa: a933934e Build parameter: meson configure build -Dgallium-drivers="swrast,iris" -Dvulkan-drivers=intel -Dbuildtype=release -Dprefix=/usr
@nchery no I no longer seeing this issue with recent mesa. I will close this issue now.
drmtip commit hash: 1d63cb5a7f02df241021731ce1ed8de3e3379bef Kernel version: 5.11 platform: TGL-U
Monitors brand: DELL P2415Q DELL P2314H DELL U2415
Steps to reproduce scenario 1: Assuming the monitor is being daisy-chained and first time need to enable the MST on parent's monitor (The monitor that attached to the board). On the Monitor's OSD menu, enable the MST Observe the monitor screen
Expected Result: The screen is extended/ MST feature enabled
Actual Result: Blank screen / black screen at first. Then, the monitors fall to sleep. The screen is not waking up as we moved the mouse. Additional info: from ssh terminal, if we send some event 'startx' for example, the monitor will works as expected result.
Steps to reproduce for scenario 2 Assuming the monitor is being daisy-chained and has being enabled the MST on parent's monitor (The monitor that attached to the board). On the Monitor's OSD menu, disable the MST Observe the monitor screen
Expected Result: The screen is extended/ MST feature disabled
Actual Result: Blank screen / black screen at first. Then, the monitors fall to sleep. The screen is not waking up as we moved the mouse. Additional info: from ssh terminal, if we send some event 'startx' for example, the monitor will works as expected result.
dmesg_startx_afterenabledmstatmonitor.txtdmesg_enabledMSTfrommonitor.txt
Hi @jani.saarinen The issue is no longer reproducible with the latest drmtip. Sorry for late responds
@kwg yes. The issue will no longer reproducible if we export INTEL_DEBUG=nohiz
. However, I do have some query and concerned regarding nohiz
From the doc, nohiz means disable HIZ for depthstencil images. Should it will cause weird sorting result due to no depth and stencil buffer?
@imirkin and @kwg, we did tried the latest mesa commit 48d48fbf. It seems like the issue is still reproducible. We tried to bisect and found out that the first bad commit is 5088caa1.
"Note that a later commit did fix a practical issue in iris with these scissored clears (clamping them to the dimensions of the viewport). But I think you're testing from after that fix went in."
I believed you meant by the latest master commit which has this merged !9867 (merged). Unfortunately, with current latest mesa, I am still seeing the flickering
Hazwan Arif Mazlan (3ea46f93) at 24 Apr 19:40
Hi @p12tic Done checked the check box "Allow commits from members who can merge to the target branch"
Hazwan Arif Mazlan (09f9da96) at 24 Apr 19:18
dri2: Sync i965_pci_ids.h from mesa iris_pci_ids.h
... and 172 more commits
Hi @imirkin Do you have any feedback that we could bisect this issue? From my bisecting, it seems like the issue started to happened after the 5088caa1 !8905 (merged) being pushed to master
Does not seems like !9867 (merged) resolved the issue. The latest master is also does not resolving the issue
OS: Yocto OS
Affected platform: ADL-S, TGL-U and TGL-H
kernel: drm-tip commit hash: 232731931d https://anongit.freedesktop.org/git/drm-tip.git
weston rev: weston 9.0.0 (Build: 9.0.0-48-gacb16b7)
affected mesa commit: 48d48fbf
suspected first bad commit: 5088caa1 !8905
Description:- Some pixel flickering seeing when running the Fuji Cluster application.
Steps to reproduce