Public bug reported:
[ Impact ]
* This issue impact devices which enable FBC and using damage to update
display. The framebuffer ID is 0 in the damage information cause driver
reject the submission.
[ Test Plan ]
* enable FBC on device
* cat /sys/kernel/debug/dri/{num}/*fbc* to make sure FBC is enabled
* using bpftrace to tracking what info pass to kernel
```
sudo bpftrace -e '
kprobe:drm_mode_dirtyfb_ioctl
{
$fb_id = *(uint32)(arg1 + 0);
$num = *(uint32)(arg1 + 12);
$clipptr = *(uint64)(arg1 + 16);
printf("kernel DirtyFB fb_id=%u num_clips=%u comm=%s\n", $fb_id, $num,
comm);
if ($num > 0 && $clipptr != 0) {
printf(" clip[0] x1=%u y1=%u x2=%u y2=%u\n",
*(uint16)($clipptr + 0),
*(uint16)($clipptr + 2),
*(uint16)($clipptr + 4),
*(uint16)($clipptr + 6));
}
}'
```
[ Where problems could occur ]
* The image maybe disorder, broken or black screen if wrong region info
is passed.
** Affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2146867
Title:
[SRU] Fixing screen rotation failure when using FBC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2146867/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
