Bug#925334: vc4: CMA fills up and screen not updated anymore on raspi3
Package: src:linux
Version: 4.19.28-2
Followup-For: Bug #925334
Dear Maintainer,
the bug is still present in the current version. It took a freshly
booted, idle system 3304 seconds for the bug to occur, though,
so this time rather an hour (than 10-30min as stated before).
After the bug has happened, I get the following information from sysfs:
| root@rpi3:/sys/bus/platform/drivers/vc4_v3d# for I in enabled status active_time suspended_time; do echo -n "$I=$(cat 3fc00000.v3d/power/runtime_$I) "; done; echo
| enabled=enabled status=error active_time=16800 suspended_time=55464216
And again:
| enabled=enabled status=error active_time=16800 suspended_time=55479160
So vc4_v3d which reported the error seems to be in status=error
and counts as suspended. Manual attempts to get it to resume again,
now that more cma is free again, failed, but there are probably ways
I don't know about.
"echo on > .../power/control" changed runtime_enabled=forbidden
(and echo auto > control changed it back to runtime_enabled=enabled),
but runtime_status remained at "error".
Regards, Fabian
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: arm64 (aarch64)
Kernel: Linux 4.19.0-4-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Reply to: