Comment 39 for bug 1726548

Confirm on Ubuntu 23.04, with quite odd results.

- Screen is attached via DisplayPort (to MiniDP on the box)
- trying to sleep for the Monitor most of the time goes okay
- reawakening puts the whole desktop into a small rectangle (top left corner) or with very low res (1024x768?) over the whole screen. Switching VTs doesn't resolve it.

One additional data point: This started with connecting the right GPIO to the Display Port in the DTS file (the box is Windows Dev Kit 2023, ARM64). Before this, wakeup worked with the right resolution, but unresposive (mouse stuck). Switching VT revived the session.

This is the dmesg -W from the wakeup:

[ 5903.388522] Console: switching to colour frame buffer device 80x30
[ 5903.388537] msm_dpu ae01000.display-controller: [drm] fb0: msmdrmfb frame buffer device
[ 5935.605411] audit: type=1400 audit(1690982650.836:68): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/19459/usr/lib/snapd/snap-confine" pid=4354 comm="snap-confine" capability=12 capname="net_admin"
[ 5935.605419] audit: type=1400 audit(1690982650.836:69): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/19459/usr/lib/snapd/snap-confine" pid=4354 comm="snap-confine" capability=38 capname="perfmon"
[ 5935.702043] event_q is full: pndx=0 gndx=1
[ 5938.771963] event_q is full: pndx=2 gndx=3
[ 5940.414504] event_q is full: pndx=7 gndx=0
[ 5955.299032] event_q is full: pndx=2 gndx=3
[ 5955.319046] event_q is full: pndx=2 gndx=3
[ 6027.273560] event_q is full: pndx=4 gndx=5
[ 6028.478737] event_q is full: pndx=5 gndx=6
[ 6073.971299] event_q is full: pndx=4 gndx=5
[ 6076.535566] audit: type=1400 audit(1690982791.760:70): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/19459/usr/lib/snapd/snap-confine" pid=4817 comm="snap-confine" capability=12 capname="net_admin"
[ 6076.535582] audit: type=1400 audit(1690982791.760:71): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/19459/usr/lib/snapd/snap-confine" pid=4817 comm="snap-confine" capability=38 capname="perfmon"
[ 6076.633963] event_q is full: pndx=2 gndx=3

and this is the dmesg regarding display:

sudo dmesg|grep display
[ 2.154537] msm-mdss ae00000.display-subsystem: Adding to iommu group 5
[ 2.208948] platform ae90000.displayport-controller: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000/ports/port@0/endpoint
[ 2.263689] platform ae98000.displayport-controller: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000/ports/port@4/endpoint
[ 2.294782] platform ae9a000.displayport-controller: Fixed dependency cycle(s) with /dp2-connector/port/endpoint
[ 2.294798] platform ae9a000.displayport-controller: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/display-controller@ae01000/ports/port@6/endpoint
[ 2.347632] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with ae90000.displayport-controller
[ 2.359000] qcom_pmic_glink pmic-glink: Failed to create device link (0x180) with ae98000.displayport-controller
[ 2.378904] msm_dpu ae01000.display-controller: bound ae90000.displayport-controller (ops dp_display_comp_ops [msm])
[ 2.388794] msm_dpu ae01000.display-controller: bound ae98000.displayport-controller (ops dp_display_comp_ops [msm])
[ 2.405143] msm_dpu ae01000.display-controller: bound ae9a000.displayport-controller (ops dp_display_comp_ops [msm])
[ 2.442730] msm_dpu ae01000.display-controller: bound 3d00000.gpu (ops a3xx_ops [msm])
[ 2.462696] [drm] Initialized msm 1.10.0 20130625 for ae01000.display-controller on minor 0
[ 2.463353] msm_dpu ae01000.display-controller: [drm:adreno_request_fw [msm]] loaded qcom/a660_sqe.fw from new location
[ 2.463709] msm_dpu ae01000.display-controller: [drm:adreno_request_fw [msm]] loaded qcom/a690_gmu.bin from new location
[ 2.507379] msm_dpu ae01000.display-controller: [drm] Cannot find any crtc or sizes

So, this appears to be an unfortunate connection of events IMO. I will go and look if detection of screen size can be made to work. On initial bootup it actually does come up with the right resolution (3840x2160, 60Hz).