[nemo87]

Buongiorno a tutti, ho una raspberry 4 4GB con installato Raspberry pi OS (lie) 64bit, su cui ci ho poi installato xorg, xinitrc, i3 firefox e chromium (all'inizio era una "prova" per passare il tempo in lockdown), successivamente ho iniziato ad usarlo sempre più spesso in sostituzione del portatile (per seguire corsi o riunioni on-line)...

Fino a ieri nessun problema di alcun genere, da ieri ogni tanto il sistema si blocca senza alcun motivo apparente, (si blocca quando magari sto navigando o, mentre modifico file) questo il risultato se digito: grep -i "Error" /var/log/syslog

Codice:

pi@raspberrypi:~ $ grep -i "Error" /var/log/syslog[/font][/size][/color]
May 30 08:14:51 raspberrypi kernel: [  421.778655] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:14:51 raspberrypi kernel: [  421.778992] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:14:51 raspberrypi kernel: [  421.780868] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:14:51 raspberrypi kernel: [  421.811236] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:14:51 raspberrypi kernel: [  421.811729] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:14:51 raspberrypi kernel: [  421.813527] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:14:51 raspberrypi kernel: [  421.813724] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:14:52 raspberrypi kernel: [  422.603779] v3d fec00000.v3d: MMU error from client L2T (0) at 0x2c41000, pte invalid

May 30 08:46:02 raspberrypi kernel: [    9.026454] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2

May 30 08:48:43 raspberrypi kernel: [  172.937536] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:48:43 raspberrypi kernel: [  172.937902] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:48:43 raspberrypi kernel: [  172.939607] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:48:43 raspberrypi kernel: [  172.970091] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:48:43 raspberrypi kernel: [  172.970594] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:48:43 raspberrypi kernel: [  172.971959] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:48:43 raspberrypi kernel: [  172.972130] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 08:49:25 raspberrypi kernel: [  215.244380] v3d fec00000.v3d: MMU error from client L2T (0) at 0x55a1000, pte invalid

May 30 10:41:25 raspberrypi kernel: [    6.544801] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2

May 30 10:44:07 raspberrypi udisksd[432]: Error initializing polkit authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.PolicyKit1': timed out (service_start_timeout=25000ms) (g-dbus-error-quark, 20)

May 30 10:45:58 raspberrypi kernel: [  282.290309] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:45:58 raspberrypi kernel: [  282.291733] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:45:58 raspberrypi kernel: [  282.293389] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:45:58 raspberrypi kernel: [  282.326010] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:45:58 raspberrypi kernel: [  282.326733] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:45:58 raspberrypi kernel: [  282.328323] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:45:58 raspberrypi kernel: [  282.328500] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:46:45 raspberrypi kernel: [  329.264005] v3d fec00000.v3d: MMU error from client L2T (0) at 0x9181000, pte invalid

May 30 10:52:09 raspberrypi kernel: [    6.560442] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2

May 30 10:55:10 raspberrypi kernel: [  190.622079] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:55:10 raspberrypi kernel: [  190.622482] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:55:10 raspberrypi kernel: [  190.624096] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:55:10 raspberrypi kernel: [  190.655916] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:55:10 raspberrypi kernel: [  190.656461] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:55:10 raspberrypi kernel: [  190.657879] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:55:10 raspberrypi kernel: [  190.658185] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

May 30 10:55:34 raspberrypi kernel: [  214.324262] v3d fec00000.v3d: MMU error from client L2T (0) at 0x2ec1000, pte invalid

Il file binario /var/log/syslog corrisponde
[color=#555555][size=small][font=Roboto, Arial, Helvetica, sans-serif]

Avete qualche idea?

[Enrico Sartori]

se non è cambiato nulla ed è sempre andato, direi che la SD perde colpi.
si potrebbe clonare su una chiavetta usb, e fare il boot da li.
o testare la schedina con qualche tool su pc

[Zzed]

La versione 64 bit è pur sempre una beta, consiglio di usare quella a 32bit

[nemo87]

Ho provato a colmarla su una chiavetta usb 3.0 lexar 13mb/s… per disperazione sono tornato a scheda sd ?
Comunque ho re installato ex novo il sistema, ad ora non si è bloccato una volta