https://bugs.kde.org/show_bug.cgi?id=429125
Pierre C <pie...@carru.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pie...@carru.fr
--- Comment #15 from Pierre C <pie...@carru.fr> ---
Hi,
Exact same setup as #14. Raspberry Pi 400, original SD, upgraded today,
`gcompris` freezes, `gcompris -m` working.
Not sure why gcompris triggers this only with audio.
This seems related to reclocking the v3d core. If I understand correctly the
linux kernel changes the frequency of the v3d core (gpu) down, which is done by
talking to a firmware. This fails and the system freezes, maybe due to not
comprehensive error handling in the kernel side (mutex taken?) or the firmware
getting stuck.
The firmware communication layer seems to be used all the time (rpi_firmware_*)
so not surprising that if something gets stuck the system freezes.
It's possible that the reclock fails because a previous audio related message
to the firmware crashed it, but there's no logs about this.
v3d_clock_down_work:
https://github.com/raspberrypi/linux/blob/31d364af258ff9754a1a9c7d8ea532da962797bd/drivers/gpu/drm/v3d/v3d_gem.c#L23-L32
v3d_clock_up_put: reclocks down after 100ms of no one holding the "clock up"
https://github.com/raspberrypi/linux/blob/31d364af258ff9754a1a9c7d8ea532da962797bd/drivers/gpu/drm/v3d/v3d_gem.c#L51-L60
--
You are receiving this mail because:
You are watching all bug changes.
