Freezeups occur on Raspberry Pi when running Visual Code and some Videos

Ask Fedora
, , , ,
1

Hi All,

I’m running the Desktop edition of Fedora 38 on a Raspberry Pi4 with 8GB RAM and Firefox 117.0.1.
I’m experiencing freezeups when running Visual Code 1.82.2 and am unable run videos for the Modern C++ OReilly course.

Running journalctl -f shows the following MMU/Memory related errors:
v3d fec00000.gpu: MMU error from client L2T (0) at 0x66c1000, pte invalid
Couldn’t sanitize RENDERER device: V3D 4.2
vc4-drm gpu: swiotlb buffer is full (sz: 3248128 bytes), total 32768 (slots), used 2456 (slots)
MediaDecoderStateMachine #3] WARNING: Decoder=aaaade78ca30 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR

In an attempt to fix these problems, I entered the following line at the bottom of /boot/efi/context.txt and then rebooted:
dtoverlay=cma,cma-256

Unfortunately, “grep Cma /proc/meminfo” doesn’t show any change (increase) to the Cma after modifying the config.txt file. The Cma is still the following:
CmaTotal: 65536 kB
CmaFree: 36780 kB

Does anyone have any ideas on how to increase the Cma value?

Thanks.

2

First off, welcome to the Fedora Discussion site!

Yeah, doing this from a Raspberry Pi might be the practical definition of trying to squeeze blood from a turnip, but you’re in good company here :sweat_smile: !

It looks like it’s not able to use hardware acceleration to its advantage which isn’t helping for the performance either:

Running journalctl -f shows the following MMU/Memory related errors:
v3d fec00000.gpu: MMU error from client L2T (0) at 0x66c1000, pte invalid
Couldn’t sanitize RENDERER device: V3D 4.2
vc4-drm gpu: swiotlb buffer is full (sz: 3248128 bytes), total 32768 (slots), used 2456 (slots)
MediaDecoderStateMachine #3] WARNING: Decoder=aaaade78ca30 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR

I’ve compiled a number of C++ projects on Pi4’s and it most definitely requires a lot of patience.

If you haven’t already, definitely install heat sinks and fans on your Pi4 unit. That can definitely help with avoiding total lock-ups. C++ compiling and video software decoding are both very CPU intensive tasks and Pi4’s are notorious for heating up under load.

3

Scott, You gave me a great lead about using hardware acceleration. I came across a link providing directions on how to disable hardware acceleration for Visual Code. I followed the directions and Visual Code isn’t freezing up anymore! So thanks for the hardware acceleration lead!

Here’s the link in case you’re interested:

Some Other Issues, I plan to pursue later:
I’m still seeing the following error:
v3d fec00000.gpu: MMU error from client L2T (0) at 0x66c1000, pte invalid

And entered characters aren’t echoed back consistently, when running the Rust Analyzer extension in Visual Code. This isn’t a problem when running the cmake extension.

1 Like