ForoRaspberry.es

Foro Soporte NO OFICIAL Raspberry Pi en Español
https://www.fororaspberry.es/

RPi3B+ se reinicia

https://www.fororaspberry.es/viewtopic.php?t=17659

Página 1 de 1

RPi3B+ se reinicia

Publicado: 10 Ene 2025, 08:27
por walkandtalkblues
Buenas a todos.
Tengo una RPI3B+ con raspbian y nodered funcionando. Es una Rp que uso para gestionar varias cosas en mi casa. Es un servidor MQTt con el que interactuan dos arduinos. Además la raspberry hace una serie de operaciones y automatizaciones para gestionar un sistema de energía solar.

El problema que tengo es que se reinicia sola, cada cierto tiempo. Siempre he creído que era por falta de alimentación, de hecho estaba mal alimentada ya que al conectarme en remoto a ella aparecía el anucio de "low voltage". Además he comprobado que el comando "cvgencmd get_throttled" daba positivo, estaba permanentemente capándolo. He visto que los alimentadores oficiales de RPI dan 5,1V en lugar de 5V y he leído que esa es la principal causa de reinicios así que he probado lo siguiente. He usado un convertidor DC-DC (3 amperios) para alimentar la rpi (ya que el origen de la energía es la batería conectada a los paneles solares) y le he regulado el voltaje a 5,15V (antes del cable usb, no sé cuanto puede caer al final de éste). Ya no sale el cartelito de low voltage, "...trottled" da 0x0 y la temperatura no supera los 38ºC. Pero se sigue reiniciando, y me atrevo a decir que con mayor frecuencia (unas horas). Mientras escribo esto se me está ocurriendo que quizá debería medir tensiones en los GPIO a ver cuanto se acercan a 5V.

La cosa es que no sé qué más puedo comprobar. Entiendo que habrá alguna especie de log donde se registren los eventos de reinicio pero no tengo ni idea de donde está ni que buscar en él. A ver si alguien puede echarme un cable con eso para confirmar o descartar que siga siendo un problema de alimentación.

Muchas gracias

Re: RPi3B+ se reinicia

Publicado: 10 Ene 2025, 17:49
por egrueda
Sería bueno ver qué está haciendo la raspi antes de reiniciarse.
El primer lugar para mirar es en /var/log/syslog
Quizá tengas que instalar rsyslog para guardar los logs y luego reiniciar
También dmesg te dará información.
Por último, monitorizar uso de memoria, cpu, temperatura, etc para ver qué valores tenía la raspi justo cuando se ha reiniciado.

Re: RPi3B+ se reinicia

Publicado: 10 Ene 2025, 22:38
por walkandtalkblues
Gracias por la respuesta, la verdad es que viendo el syslog no termino de ver lo que pasa. No identifico donde empieza el reinicio ni lo que ocurre antes de que se dé. Comparto aquí las líneas del log donde me parece que se da un reinicio a las 6:48. y escribo esto sin haberse dado un reinicio en unas 14h....se ha reiniciado al conectarme por vnc tras haberse congelado

Código: Seleccionar todo

Jan 10 06:17:01 A51SERVER CRON[30657]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan 10 06:25:01 A51SERVER CRON[31635]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Jan 10 06:45:46 A51SERVER vncserver-x11[513,root]: SModuleUpdateNotification: Last checked for updates more than 365 days ago
Jan 10 06:49:51 A51SERVER systemd[1]: Starting Daily apt upgrade and clean activities...
Jan 10 06:49:55 A51SERVER systemd[1]: apt-daily-upgrade.service: Succeeded.
Jan 10 06:49:55 A51SERVER systemd[1]: Started Daily apt upgrade and clean activities.
Jan 10 06:48:42 A51SERVER systemd-modules-load[112]: Inserted module 'i2c_dev'
Jan 10 06:48:42 A51SERVER fake-hwclock[120]: vie ene 10 05:17:01 UTC 2025
Jan 10 06:48:42 A51SERVER systemd-fsck[138]: e2fsck 1.44.5 (15-Dec-2018)
Jan 10 06:48:42 A51SERVER systemd-fsck[138]: rootfs: clean, 154220/941616 files, 1492273/3822976 blocks
Jan 10 06:48:42 A51SERVER systemd[1]: Started File System Check on Root Device.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Remount Root and Kernel File Systems...
Jan 10 06:48:42 A51SERVER systemd[1]: Started udev Coldplug all Devices.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Helper to synchronize boot up for ifupdown...
Jan 10 06:48:42 A51SERVER systemd[1]: Started Helper to synchronize boot up for ifupdown.
Jan 10 06:48:42 A51SERVER systemd[1]: Started Remount Root and Kernel File Systems.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Flush Journal to Persistent Storage...
Jan 10 06:48:42 A51SERVER systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Load/Save Random Seed...
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Create System Users...
Jan 10 06:48:42 A51SERVER systemd[1]: Started Set the console keyboard layout.
Jan 10 06:48:42 A51SERVER systemd[1]: Started Load/Save Random Seed.
Jan 10 06:48:42 A51SERVER systemd[1]: Started Flush Journal to Persistent Storage.
Jan 10 06:48:42 A51SERVER systemd[1]: Started Create System Users.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Create Static Device Nodes in /dev...
Jan 10 06:48:42 A51SERVER systemd[1]: Started Create Static Device Nodes in /dev.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting udev Kernel Device Manager...
Jan 10 06:48:42 A51SERVER systemd[1]: Reached target Local File Systems (Pre).
Jan 10 06:48:42 A51SERVER systemd[1]: Started udev Kernel Device Manager.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Show Plymouth Boot Screen...
Jan 10 06:48:42 A51SERVER systemd[1]: Received SIGRTMIN+20 from PID 165 (plymouthd).
Jan 10 06:48:42 A51SERVER systemd[1]: Started Show Plymouth Boot Screen.
Jan 10 06:48:42 A51SERVER systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
Jan 10 06:48:42 A51SERVER systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
Jan 10 06:48:42 A51SERVER systemd[1]: Reached target Local Encrypted Volumes.
Jan 10 06:48:42 A51SERVER mtp-probe: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.1"
Jan 10 06:48:42 A51SERVER mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
Jan 10 06:48:42 A51SERVER mtp-probe: bus: 1, device: 4 was not an MTP device
Jan 10 06:48:42 A51SERVER mtp-probe: bus: 1, device: 5 was not an MTP device
Jan 10 06:48:42 A51SERVER systemd[1]: Found device /dev/disk/by-partuuid/c7f6f68d-01.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting File System Check on /dev/disk/by-partuuid/c7f6f68d-01...
Jan 10 06:48:42 A51SERVER systemd-udevd[161]: Using default interface naming scheme 'v240'.
Jan 10 06:48:42 A51SERVER systemd-fsck[243]: fsck.fat 4.1 (2017-01-24)
Jan 10 06:48:42 A51SERVER systemd-fsck[243]: 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Jan 10 06:48:42 A51SERVER systemd-fsck[243]:  Automatically removing dirty bit.
Jan 10 06:48:42 A51SERVER systemd-fsck[243]: Performing changes.
Jan 10 06:48:42 A51SERVER systemd-fsck[243]: /dev/mmcblk0p1: 352 files, 100280/516190 clusters
Jan 10 06:48:42 A51SERVER systemd[1]: Started File System Check on /dev/disk/by-partuuid/c7f6f68d-01.
Jan 10 06:48:42 A51SERVER systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jan 10 06:48:42 A51SERVER systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
Jan 10 06:48:42 A51SERVER systemd[1]: Condition check resulted in Huge Pages File System being skipped.
Jan 10 06:48:42 A51SERVER systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Jan 10 06:48:42 A51SERVER systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Jan 10 06:48:42 A51SERVER systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
Jan 10 06:48:42 A51SERVER systemd[1]: Mounting /boot...
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Load/Save RF Kill Switch Status...
Jan 10 06:48:42 A51SERVER systemd[1]: Started Load/Save RF Kill Switch Status.
Jan 10 06:48:42 A51SERVER systemd[1]: Mounted /boot.
Jan 10 06:48:42 A51SERVER systemd[1]: Reached target Local File Systems.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Raise network interfaces...
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Set console font and keymap...
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Preprocess NFS configuration...
Jan 10 06:48:42 A51SERVER systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Create Volatile Files and Directories...
Jan 10 06:48:42 A51SERVER systemd[1]: Started Set console font and keymap.
Jan 10 06:48:42 A51SERVER systemd[1]: nfs-config.service: Succeeded.
Jan 10 06:48:42 A51SERVER systemd[1]: Started Preprocess NFS configuration.
Jan 10 06:48:42 A51SERVER systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
Jan 10 06:48:42 A51SERVER systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
Jan 10 06:48:42 A51SERVER systemd[1]: Reached target NFS client services.
Jan 10 06:48:42 A51SERVER systemd[1]: Reached target Remote File Systems (Pre).
Jan 10 06:48:42 A51SERVER systemd[1]: Reached target Remote File Systems.
Jan 10 06:48:42 A51SERVER systemd[1]: Started Create Volatile Files and Directories.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Network Time Synchronization...
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Jan 10 06:48:42 A51SERVER systemd[1]: Started Update UTMP about System Boot/Shutdown.
Jan 10 06:48:42 A51SERVER systemd[1]: Received SIGRTMIN+20 from PID 165 (plymouthd).
Jan 10 06:48:42 A51SERVER systemd[1]: plymouth-read-write.service: Succeeded.
Jan 10 06:48:42 A51SERVER systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Jan 10 06:48:42 A51SERVER systemd[1]: Started Raise network interfaces.
Jan 10 06:48:42 A51SERVER systemd-timesyncd[336]: System clock time unset or jumped backwards, restoring from recorded timestamp: Fri 2025-01-10 06:48:41 CET
Jan 10 06:48:42 A51SERVER systemd[1]: Started Network Time Synchronization.
Jan 10 06:48:42 A51SERVER systemd[1]: Reached target System Initialization.
Jan 10 06:48:42 A51SERVER systemd[1]: Started CUPS Scheduler.
Jan 10 06:48:42 A51SERVER systemd[1]: Reached target Paths.
Jan 10 06:48:42 A51SERVER systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Jan 10 06:48:42 A51SERVER systemd[1]: Listening on CUPS Scheduler.
Jan 10 06:48:42 A51SERVER systemd[1]: Listening on triggerhappy.socket.
Jan 10 06:48:42 A51SERVER systemd[1]: Listening on D-Bus System Message Bus Socket.
Jan 10 06:48:42 A51SERVER systemd[1]: Reached target Sockets.
Jan 10 06:48:42 A51SERVER systemd[1]: Reached target Basic System.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Login Service...
Jan 10 06:48:42 A51SERVER systemd[1]: Starting dphys-swapfile - set up, mount/unmount, and delete a swap file...
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Check for Raspberry Pi EEPROM updates...
Jan 10 06:48:42 A51SERVER systemd[1]: Started Node-RED graphical event wiring tool.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Configure Bluetooth Modems connected by UART...
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Jan 10 06:48:42 A51SERVER systemd[1]: Starting Check for v3d driver...
Jan 10 06:48:42 A51SERVER systemd[1]: Starting LSB: Switch to ondemand cpu governor (unless shift key is pressed)...
Jan 10 06:48:42 A51SERVER systemd[1]: Started Daily Cleanup of Temporary Directories.
Jan 10 06:48:42 A51SERVER systemd[1]: Started Regular background program processing daemon.
Jan 10 06:48:42 A51SERVER systemd[1]: Starting triggerhappy global hotkey daemon...
Jan 10 06:48:42 A51SERVER rpi-eeprom-update[364]: This tool only works with a Raspberry Pi 4
Jan 10 06:48:42 A51SERVER systemd[1]: Starting System Logging Service...
Jan 10 06:48:42 A51SERVER systemd[1]: Started Manage Sound Card State (restore and store).

Re: RPi3B+ se reinicia

Publicado: 10 Ene 2025, 23:29
por egrueda
Puedes ver los reinicios que ha habido usando el comando last. A ver qué te dice.

Y también tienes el potente comando journalctl donde puedes ver logs de inicios previos.

journalctl --list-boots

Y mucha más info de este comando aquí:
https://www.loggly.com/ultimate-guide/using-journalctl/

A ver si así vemos qué pasa *antes* de que se reinicie, o al menos confirmar que se ha reiniciado

Re: RPi3B+ se reinicia

Publicado: 11 Ene 2025, 12:13
por walkandtalkblues
las reboot:

Código: Seleccionar todo

reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00   still running
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00   still running
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00   still running
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)
reboot   system boot  5.10.103-v7+     Thu Jan  1 01:00 - 21:10 (20098+20:09)

journalctl --list-boots:

Código: Seleccionar todo

 0 7a9ab7f2e43b4b86b2d66f15ff469cab Thu 2019-02-14 11:11:59 CET—Sat 2025-01-11 1
lines 1-1/1 (END)...skipping...
 0 7a9ab7f2e43b4b86b2d66f15ff469cab Thu 2019-02-14 11:11:59 CET—Sat 2025-01-11 11:38:31 CET

Re: RPi3B+ se reinicia

Publicado: 11 Ene 2025, 12:42
por walkandtalkblues
sudo less /var/log/messages:

Código: Seleccionar todo

Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Booting Linux on physical CPU 0x0
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Linux version 5.10.103-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, G
NU ld (GNU Binutils for Ubuntu) 2.34) #1529 SMP Tue Mar 8 12:21:37 GMT 2022
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] CPU: div instructions available: patching division code
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] random: fast init done
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Memory policy: Data cache writealloc
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Reserved memory: created CMA memory pool at 0x37400000, size 64 MiB
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Jan 11 01:17:05 A51SERVER mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
Jan 11 01:17:05 A51SERVER mtp-probe: bus: 1, device: 4 was not an MTP device
Jan 11 01:17:05 A51SERVER mtp-probe: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.1"
Jan 11 01:17:05 A51SERVER mtp-probe: bus: 1, device: 5 was not an MTP device
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Zone ranges:
Jan 11 01:17:05 A51SERVER kernel: [    0.000000]   DMA      [mem 0x0000000000000000-0x000000003b3fffff]
Jan 11 01:17:05 A51SERVER kernel: [    0.000000]   Normal   empty
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Movable zone start for each node
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Early memory node ranges
Jan 11 01:17:05 A51SERVER kernel: [    0.000000]   node   0: [mem 0x0000000000000000-0x000000003b3fffff]
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003b3fffff]
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] percpu: Embedded 20 pages/cpu s50828 r8192 d22900 u81920
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hd
mi=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=t
ty1 root=PARTUUID=c7f6f68d-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Kernel parameter elevator= does not have any effect anymore.
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Please use sysfs to set IO scheduler for individual devices.
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] Memory: 878804K/970752K available (10240K kernel code, 1312K rwdata, 2952K rodata, 1024K init, 862K bss, 26412K reserved, 65536K cma-reserved)
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] ftrace: allocating 32081 entries in 95 pages
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] ftrace: allocated 94 pages with 5 groups
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] rcu: Hierarchical RCU implementation.
Jan 11 01:17:05 A51SERVER kernel: [    0.000000]        Rude variant of Tasks RCU enabled.
Jan 11 01:17:05 A51SERVER kernel: [    0.000000]        Tracing variant of Tasks RCU enabled.
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] random: get_random_bytes called from start_kernel+0x3ac/0x580 with crng_init=1
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Jan 11 01:17:05 A51SERVER kernel: [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Jan 11 01:17:05 A51SERVER kernel: [    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Jan 11 01:17:05 A51SERVER kernel: [    0.000020] Switching to timer-based delay loop, resolution 52ns
Jan 11 01:17:05 A51SERVER kernel: [    0.000302] Console: colour dummy device 80x30
Jan 11 01:17:05 A51SERVER kernel: [    0.000375] printk: console [tty1] enabled
Jan 11 01:17:05 A51SERVER kernel: [    0.000427] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
Jan 11 01:17:05 A51SERVER kernel: [    0.000455] pid_max: default: 32768 minimum: 301
Jan 11 01:17:05 A51SERVER kernel: [    0.000665] LSM: Security Framework initializing
Jan 11 01:17:05 A51SERVER kernel: [    0.000909] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
Jan 11 01:17:05 A51SERVER kernel: [    0.000932] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
Jan 11 01:17:05 A51SERVER kernel: [    0.002372] cgroup: Disabling memory control group subsystem
Jan 11 01:17:05 A51SERVER kernel: [    0.002636] CPU: Testing write buffer coherency: ok
Jan 11 01:17:05 A51SERVER kernel: [    0.003133] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Jan 11 01:17:05 A51SERVER kernel: [    0.004368] Setting up static identity map for 0x100000 - 0x10003c
Jan 11 01:17:05 A51SERVER kernel: [    0.004554] rcu: Hierarchical SRCU implementation.
Jan 11 01:17:05 A51SERVER kernel: [    0.005470] smp: Bringing up secondary CPUs ...
Jan 11 01:17:05 A51SERVER kernel: [    0.006622] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Jan 11 01:17:05 A51SERVER kernel: [    0.007892] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
Jan 11 01:17:05 A51SERVER kernel: [    0.009091] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Jan 11 01:17:05 A51SERVER kernel: [    0.009248] smp: Brought up 1 node, 4 CPUs
Jan 11 01:17:05 A51SERVER kernel: [    0.009271] SMP: Total of 4 processors activated (153.60 BogoMIPS).
Jan 11 01:17:05 A51SERVER kernel: [    0.009283] CPU: All CPU(s) started in HYP mode.
Jan 11 01:17:05 A51SERVER kernel: [    0.009293] CPU: Virtualization extensions available.
Jan 11 01:17:05 A51SERVER kernel: [    0.010394] devtmpfs: initialized
Jan 11 01:17:05 A51SERVER kernel: [    0.028304] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
Jan 11 01:17:05 A51SERVER kernel: [    0.028559] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Jan 11 01:17:05 A51SERVER kernel: [    0.028589] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Jan 11 01:17:05 A51SERVER kernel: [    0.031665] pinctrl core: initialized pinctrl subsystem
Jan 11 01:17:05 A51SERVER kernel: [    0.032832] NET: Registered protocol family 16
Jan 11 01:17:05 A51SERVER kernel: [    0.037200] DMA: preallocated 1024 KiB pool for atomic coherent allocations
Jan 11 01:17:05 A51SERVER kernel: [    0.042924] audit: initializing netlink subsys (disabled)
Jan 11 01:17:05 A51SERVER kernel: [    0.043248] audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1
Jan 11 01:17:05 A51SERVER kernel: [    0.043842] thermal_sys: Registered thermal governor 'step_wise'
Jan 11 01:17:05 A51SERVER kernel: [    0.044982] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
Jan 11 01:17:05 A51SERVER kernel: [    0.044998] hw-breakpoint: maximum watchpoint size is 8 bytes.
Jan 11 01:17:05 A51SERVER kernel: [    0.045294] Serial: AMBA PL011 UART driver
Jan 11 01:17:05 A51SERVER kernel: [    0.063546] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Jan 11 01:17:05 A51SERVER kernel: [    0.080115] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-12-01T15:07:06, variant start
Jan 11 01:17:05 A51SERVER kernel: [    0.090127] raspberrypi-firmware soc:firmware: Firmware hash is 71bd3109023a0c8575585ba87cbb374d2eeb038f
Jan 11 01:17:05 A51SERVER kernel: [    0.134479] Kprobes globally optimized
Jan 11 01:17:05 A51SERVER kernel: [    0.139473] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
Jan 11 01:17:05 A51SERVER kernel: [    0.141725] SCSI subsystem initialized
Jan 11 01:17:05 A51SERVER kernel: [    0.141988] usbcore: registered new interface driver usbfs
Jan 11 01:17:05 A51SERVER kernel: [    0.142052] usbcore: registered new interface driver hub
Jan 11 01:17:05 A51SERVER kernel: [    0.142125] usbcore: registered new device driver usb
Jan 11 01:17:05 A51SERVER kernel: [    0.144301] clocksource: Switched to clocksource arch_sys_counter
Jan 11 01:17:05 A51SERVER kernel: [    1.861058] VFS: Disk quotas dquot_6.6.0
Jan 11 01:17:05 A51SERVER kernel: [    1.861173] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jan 11 01:17:05 A51SERVER kernel: [    1.861375] FS-Cache: Loaded
Jan 11 01:17:05 A51SERVER kernel: [    1.861662] CacheFiles: Loaded
Jan 11 01:17:05 A51SERVER kernel: [    1.872846] NET: Registered protocol family 2
Jan 11 01:17:05 A51SERVER kernel: [    1.873122] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
Jan 11 01:17:05 A51SERVER kernel: [    1.875579] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
Jan 11 01:17:05 A51SERVER kernel: [    1.875646] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
Jan 11 01:17:05 A51SERVER kernel: [    1.875764] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
Jan 11 01:17:05 A51SERVER kernel: [    1.875956] TCP: Hash tables configured (established 8192 bind 8192)
Jan 11 01:17:05 A51SERVER kernel: [    1.876143] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
Jan 11 01:17:05 A51SERVER kernel: [    1.876200] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
Jan 11 01:17:05 A51SERVER kernel: [    1.876485] NET: Registered protocol family 1
Jan 11 01:17:05 A51SERVER kernel: [    1.877288] RPC: Registered named UNIX socket transport module.
Jan 11 01:17:05 A51SERVER kernel: [    1.877301] RPC: Registered udp transport module.
Jan 11 01:17:05 A51SERVER kernel: [    1.877313] RPC: Registered tcp transport module.
Jan 11 01:17:05 A51SERVER kernel: [    1.877325] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 11 01:17:05 A51SERVER kernel: [    1.879184] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
Jan 11 01:17:05 A51SERVER kernel: [    1.882912] Initialise system trusted keyrings
Jan 11 01:17:05 A51SERVER kernel: [    1.883194] workingset: timestamp_bits=14 max_order=18 bucket_order=4
Jan 11 01:17:05 A51SERVER kernel: [    1.892716] zbud: loaded
Jan 11 01:17:05 A51SERVER kernel: [    1.894832] FS-Cache: Netfs 'nfs' registered for caching
Jan 11 01:17:05 A51SERVER kernel: [    1.895710] NFS: Registering the id_resolver key type
Jan 11 01:17:05 A51SERVER kernel: [    1.895770] Key type id_resolver registered
Jan 11 01:17:05 A51SERVER kernel: [    1.895783] Key type id_legacy registered
Jan 11 01:17:05 A51SERVER kernel: [    1.895944] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Jan 11 01:17:05 A51SERVER kernel: [    1.895959] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
Jan 11 01:17:05 A51SERVER kernel: [    1.897164] Key type asymmetric registered
Jan 11 01:17:05 A51SERVER kernel: [    1.897179] Asymmetric key parser 'x509' registered
Jan 11 01:17:05 A51SERVER kernel: [    1.897233] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
Jan 11 01:17:05 A51SERVER rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.1901.0]
Jan 11 01:17:05 A51SERVER kernel: [    1.897248] io scheduler mq-deadline registered
Jan 11 01:17:05 A51SERVER kernel: [    1.897261] io scheduler kyber registered
Jan 11 01:17:05 A51SERVER kernel: [    1.900786] bcm2708_fb soc:fb: FB found 1 display(s)
Jan 11 01:17:05 A51SERVER kernel: [    1.908429] Console: switching to colour frame buffer device 82x26
Jan 11 01:17:05 A51SERVER kernel: [    1.913326] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 656x416
Jan 11 01:17:05 A51SERVER kernel: [    1.919011] bcm2835-rng 3f104000.rng: hwrng registered
Jan 11 01:17:05 A51SERVER rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="405" x-info="https://www.rsyslog.com"] start
Jan 11 01:17:05 A51SERVER kernel: [    1.919443] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Jan 11 01:17:05 A51SERVER kernel: [    1.920295] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Jan 11 01:17:05 A51SERVER kernel: [    1.932512] brd: module loaded
Jan 11 01:17:05 A51SERVER kernel: [    1.944800] loop: module loaded
Jan 11 01:17:05 A51SERVER kernel: [    1.946556] Loading iSCSI transport class v2.0-870.
Jan 11 01:17:05 A51SERVER kernel: [    1.948412] usbcore: registered new interface driver lan78xx
Jan 11 01:17:05 A51SERVER kernel: [    1.948481] usbcore: registered new interface driver smsc95xx
Jan 11 01:17:05 A51SERVER kernel: [    1.948506] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Jan 11 01:17:05 A51SERVER kernel: [    2.676771] Core Release: 2.80a
Jan 11 01:17:05 A51SERVER kernel: [    2.676788] Setting default values for core params
Jan 11 01:17:05 A51SERVER kernel: [    2.676819] Finished setting default values for core params
Jan 11 01:17:05 A51SERVER kernel: [    2.877209] Using Buffer DMA mode
Jan 11 01:17:05 A51SERVER kernel: [    2.877222] Periodic Transfer Interrupt Enhancement - disabled
Jan 11 01:17:05 A51SERVER kernel: [    2.877235] Multiprocessor Interrupt Enhancement - disabled
Jan 11 01:17:05 A51SERVER kernel: [    2.877248] OTG VER PARAM: 0, OTG VER FLAG: 0
Jan 11 01:17:05 A51SERVER kernel: [    2.877276] Dedicated Tx FIFOs mode
Jan 11 01:17:05 A51SERVER kernel: [    2.877851]
Jan 11 01:17:05 A51SERVER kernel: [    2.877872] WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = b7514000 dma = 0xf7514000 len=9024
Jan 11 01:17:05 A51SERVER kernel: [    2.877904] FIQ FSM acceleration enabled for :
Jan 11 01:17:05 A51SERVER kernel: [    2.877904] Non-periodic Split Transactions
Jan 11 01:17:05 A51SERVER kernel: [    2.877904] Periodic Split Transactions
Jan 11 01:17:05 A51SERVER kernel: [    2.877904] High-Speed Isochronous Endpoints
Jan 11 01:17:05 A51SERVER kernel: [    2.877904] Interrupt/Control Split Transaction hack enabled
Jan 11 01:17:05 A51SERVER kernel: [    2.877980]
Jan 11 01:17:05 A51SERVER kernel: [    2.877990] WARN::hcd_init_fiq:457: FIQ on core 1
Jan 11 01:17:05 A51SERVER kernel: [    2.877996]
Jan 11 01:17:05 A51SERVER kernel: [    2.878006] WARN::hcd_init_fiq:458: FIQ ASM at 807cb8b8 length 36
Jan 11 01:17:05 A51SERVER kernel: [    2.878014]
Jan 11 01:17:05 A51SERVER kernel: [    2.878022] WARN::hcd_init_fiq:497: MPHI regs_base at bb810000
Jan 11 01:17:05 A51SERVER kernel: [    2.878046] dwc_otg 3f980000.usb: DWC OTG Controller
Jan 11 01:17:05 A51SERVER kernel: [    2.878086] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Jan 11 01:17:05 A51SERVER kernel: [    2.878135] dwc_otg 3f980000.usb: irq 89, io mem 0x00000000
Jan 11 01:17:05 A51SERVER kernel: [    2.878190] Init: Port Power? op_state=1
Jan 11 01:17:05 A51SERVER kernel: [    2.878202] Init: Power Port (0)
Jan 11 01:17:05 A51SERVER kernel: [    2.878579] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
Jan 11 01:17:05 A51SERVER kernel: [    2.878596] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan 11 01:17:05 A51SERVER kernel: [    2.878611] usb usb1: Product: DWC OTG Controller
Jan 11 01:17:05 A51SERVER kernel: [    2.878626] usb usb1: Manufacturer: Linux 5.10.103-v7+ dwc_otg_hcd
Jan 11 01:17:05 A51SERVER kernel: [    2.878641] usb usb1: SerialNumber: 3f980000.usb
Jan 11 01:17:05 A51SERVER kernel: [    2.879392] hub 1-0:1.0: USB hub found
Jan 11 01:17:05 A51SERVER kernel: [    2.879473] hub 1-0:1.0: 1 port detected
Jan 11 01:17:05 A51SERVER kernel: [    2.881052] usbcore: registered new interface driver usb-storage
Jan 11 01:17:05 A51SERVER kernel: [    2.881407] mousedev: PS/2 mouse device common for all mice
Jan 11 01:17:05 A51SERVER kernel: [    2.882583] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Jan 11 01:17:05 A51SERVER kernel: [    2.885406] sdhci: Secure Digital Host Controller Interface driver
Jan 11 01:17:05 A51SERVER kernel: [    2.885421] sdhci: Copyright(c) Pierre Ossman
Jan 11 01:17:05 A51SERVER kernel: [    2.886034] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
Jan 11 01:17:05 A51SERVER kernel: [    2.886714] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
Jan 11 01:17:05 A51SERVER kernel: [    2.886952] sdhci-pltfm: SDHCI platform and OF driver helper
Jan 11 01:17:05 A51SERVER kernel: [    2.888829] ledtrig-cpu: registered to indicate activity on CPUs
Jan 11 01:17:05 A51SERVER kernel: [    2.889255] hid: raw HID events driver (C) Jiri Kosina
Jan 11 01:17:05 A51SERVER kernel: [    2.889425] usbcore: registered new interface driver usbhid
Jan 11 01:17:05 A51SERVER kernel: [    2.889437] usbhid: USB HID core driver
Jan 11 01:17:05 A51SERVER kernel: [    2.894779] Initializing XFRM netlink socket
Jan 11 01:17:05 A51SERVER kernel: [    2.894828] NET: Registered protocol family 17
Jan 11 01:17:05 A51SERVER kernel: [    2.894993] Key type dns_resolver registered
Jan 11 01:17:05 A51SERVER kernel: [    2.895793] Registering SWP/SWPB emulation handler
Jan 11 01:17:05 A51SERVER kernel: [    2.895948] registered taskstats version 1
Jan 11 01:17:05 A51SERVER kernel: [    2.895982] Loading compiled-in X.509 certificates
Jan 11 01:17:05 A51SERVER kernel: [    2.896880] Key type ._fscrypt registered
Jan 11 01:17:05 A51SERVER kernel: [    2.896895] Key type .fscrypt registered
Jan 11 01:17:05 A51SERVER kernel: [    2.896908] Key type fscrypt-provisioning registered
Jan 11 01:17:05 A51SERVER kernel: [    2.908626] uart-pl011 3f201000.serial: cts_event_workaround enabled
Jan 11 01:17:05 A51SERVER kernel: [    2.908738] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 114, base_baud = 0) is a PL011 rev2
Jan 11 01:17:05 A51SERVER kernel: [    2.911101] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Jan 11 01:17:05 A51SERVER kernel: [    2.912785] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
Jan 11 01:17:05 A51SERVER kernel: [    2.912803] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
Jan 11 01:17:05 A51SERVER kernel: [    2.938528] sdhost: log_buf @ (ptrval) (f7513000)
Jan 11 01:17:05 A51SERVER kernel: [    2.976910] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Jan 11 01:17:05 A51SERVER kernel: [    2.978590] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Jan 11 01:17:05 A51SERVER kernel: [    2.980288] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Jan 11 01:17:05 A51SERVER kernel: [    2.983290] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Jan 11 01:17:05 A51SERVER kernel: [    2.988329] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Jan 11 01:17:05 A51SERVER kernel: [    2.991309] of_cfs_init
Jan 11 01:17:05 A51SERVER kernel: [    2.991557] of_cfs_init: OK
Jan 11 01:17:05 A51SERVER kernel: [    2.992738] Waiting for root device PARTUUID=c7f6f68d-02...
Jan 11 01:17:05 A51SERVER kernel: [    3.009266] Indeed it is in host mode hprt0 = 00021501
Jan 11 01:17:05 A51SERVER kernel: [    3.104725] mmc0: host does not support reading read-only switch, assuming write-enable
Jan 11 01:17:05 A51SERVER kernel: [    3.108100] mmc0: new high speed SDHC card at address 0001
Jan 11 01:17:05 A51SERVER kernel: [    3.109111] mmcblk0: mmc0:0001 EB1QT 29.8 GiB
Jan 11 01:17:05 A51SERVER kernel: [    3.111873]  mmcblk0: p1 p2
Jan 11 01:17:05 A51SERVER kernel: [    3.134084] mmc1: new high speed SDIO card at address 0001
Jan 11 01:17:05 A51SERVER kernel: [    3.174234] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
Jan 11 01:17:05 A51SERVER kernel: [    3.174251] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
Jan 11 01:17:05 A51SERVER kernel: [    3.214380] usb 1-1: new high-speed USB device number 2 using dwc_otg
Jan 11 01:17:05 A51SERVER kernel: [    3.214547] Indeed it is in host mode hprt0 = 00001101
Jan 11 01:17:05 A51SERVER kernel: [    3.454705] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Jan 11 01:17:05 A51SERVER kernel: [    3.454728] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 11 01:17:05 A51SERVER kernel: [    3.455543] hub 1-1:1.0: USB hub found
Jan 11 01:17:05 A51SERVER kernel: [    3.455664] hub 1-1:1.0: 4 ports detected
Jan 11 01:17:05 A51SERVER kernel: [    3.774348] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Jan 11 01:17:05 A51SERVER kernel: [    3.904681] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Jan 11 01:17:05 A51SERVER kernel: [    3.904704] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 11 01:17:05 A51SERVER kernel: [    3.905549] hub 1-1.1:1.0: USB hub found
Jan 11 01:17:05 A51SERVER kernel: [    3.905672] hub 1-1.1:1.0: 3 ports detected
Jan 11 01:17:05 A51SERVER kernel: [    4.004378] usb 1-1.3: new full-speed USB device number 4 using dwc_otg
Jan 11 01:17:05 A51SERVER kernel: [    4.139165] usb 1-1.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
Jan 11 01:17:05 A51SERVER kernel: [    4.139192] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 11 01:17:05 A51SERVER kernel: [    4.139209] usb 1-1.3: Product: CP2102N USB to UART Bridge Controller
Jan 11 01:17:05 A51SERVER kernel: [    4.139224] usb 1-1.3: Manufacturer: Silicon Labs
Jan 11 01:17:05 A51SERVER kernel: [    4.139239] usb 1-1.3: SerialNumber: 0001
Jan 11 01:17:05 A51SERVER kernel: [    4.235134] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
Jan 11 01:17:05 A51SERVER kernel: [    4.259074] EXT4-fs (mmcblk0p2): 6 orphan inodes deleted
Jan 11 01:17:05 A51SERVER kernel: [    4.259092] EXT4-fs (mmcblk0p2): recovery complete
Jan 11 01:17:05 A51SERVER kernel: [    4.288204] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Jan 11 01:17:05 A51SERVER kernel: [    4.288317] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Jan 11 01:17:05 A51SERVER kernel: [    4.289331] devtmpfs: mounted
Jan 11 01:17:05 A51SERVER kernel: [    4.296907] Freeing unused kernel memory: 1024K
Jan 11 01:17:05 A51SERVER kernel: [    4.297409] Run /sbin/init as init process
Jan 11 01:17:05 A51SERVER kernel: [    4.714377] usb 1-1.1.1: new high-speed USB device number 5 using dwc_otg
Jan 11 01:17:05 A51SERVER kernel: [    4.844857] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
Jan 11 01:17:05 A51SERVER kernel: [    4.844878] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 11 01:17:05 A51SERVER kernel: [    5.052028] NET: Registered protocol family 10
Jan 11 01:17:05 A51SERVER kernel: [    5.053473] Segment Routing with IPv6
Jan 11 01:17:05 A51SERVER kernel: [    5.119666] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
Jan 11 01:17:05 A51SERVER kernel: [    5.145147] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
Jan 11 01:17:05 A51SERVER kernel: [    6.234067] random: systemd: uninitialized urandom read (16 bytes read)
Jan 11 01:17:05 A51SERVER kernel: [    6.250264] random: systemd: uninitialized urandom read (16 bytes read)
Jan 11 01:17:05 A51SERVER kernel: [    6.251333] random: systemd: uninitialized urandom read (16 bytes read)
Jan 11 01:17:05 A51SERVER kernel: [    6.467914] i2c /dev entries driver
Jan 11 01:17:05 A51SERVER kernel: [    6.943148] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Jan 11 01:17:05 A51SERVER kernel: [    7.735521] mc: Linux media interface: v0.10
Jan 11 01:17:05 A51SERVER kernel: [    7.764783] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
Jan 11 01:17:05 A51SERVER kernel: [    7.767782] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
Jan 11 01:17:05 A51SERVER kernel: [    7.767812] [vc_sm_connected_init]: start
Jan 11 01:17:05 A51SERVER kernel: [    7.770217] [vc_sm_connected_init]: installed successfully
Jan 11 01:17:05 A51SERVER kernel: [    7.830302] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
Jan 11 01:17:05 A51SERVER kernel: [    7.836860] bcm2835_audio bcm2835_audio: card created with 8 channels
Jan 11 01:17:05 A51SERVER kernel: [    7.851561] videodev: Linux video capture interface: v2.00
Jan 11 01:17:05 A51SERVER kernel: [    7.877577] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Jan 11 01:17:05 A51SERVER kernel: [    7.877584] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Jan 11 01:17:05 A51SERVER kernel: [    7.902381] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
Jan 11 01:17:05 A51SERVER kernel: [    7.925067] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
Jan 11 01:17:05 A51SERVER kernel: [    7.943470] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
Jan 11 01:17:05 A51SERVER kernel: [    7.944146] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
Jan 11 01:17:05 A51SERVER kernel: [    7.944666] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
Jan 11 01:17:05 A51SERVER kernel: [    7.945031] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
Jan 11 01:17:05 A51SERVER kernel: [    7.945067] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
Jan 11 01:17:05 A51SERVER kernel: [    7.945096] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
Jan 11 01:17:05 A51SERVER kernel: [    7.945136] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
Jan 11 01:17:05 A51SERVER kernel: [    7.945157] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
Jan 11 01:17:05 A51SERVER kernel: [    7.945410] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
Jan 11 01:17:05 A51SERVER kernel: [    7.949801] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
Jan 11 01:17:05 A51SERVER kernel: [    7.957719] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
Jan 11 01:17:05 A51SERVER kernel: [    7.957781] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
Jan 11 01:17:05 A51SERVER kernel: [    7.965011] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
Jan 11 01:17:05 A51SERVER kernel: [    7.965066] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
Jan 11 01:17:05 A51SERVER kernel: [    8.004870] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
Jan 11 01:17:05 A51SERVER kernel: [    8.005051] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
Jan 11 01:17:05 A51SERVER kernel: [    8.016679] bcm2835-codec bcm2835-codec: Device registered as /dev/video18
Jan 11 01:17:05 A51SERVER kernel: [    8.016793] bcm2835-codec bcm2835-codec: Loaded V4L2 image_fx
Jan 11 01:17:05 A51SERVER kernel: [    8.181862] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Jan 11 01:17:05 A51SERVER kernel: [    8.373995] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Jan 11 01:17:05 A51SERVER kernel: [    8.452607] usbcore: registered new interface driver usbserial_generic
Jan 11 01:17:05 A51SERVER kernel: [    8.452693] usbserial: USB Serial support registered for generic
Jan 11 01:17:05 A51SERVER kernel: [    8.455424] usbcore: registered new interface driver brcmfmac
Jan 11 01:17:05 A51SERVER kernel: [    8.484627] usbcore: registered new interface driver cp210x
Jan 11 01:17:05 A51SERVER kernel: [    8.484731] usbserial: USB Serial support registered for cp210x
Jan 11 01:17:05 A51SERVER kernel: [    8.484956] cp210x 1-1.3:1.0: cp210x converter detected
Jan 11 01:17:05 A51SERVER kernel: [    8.505938] usb 1-1.3: cp210x converter now attached to ttyUSB0
Jan 11 01:17:05 A51SERVER kernel: [    8.820394] random: crng init done
Jan 11 01:17:05 A51SERVER kernel: [    8.820415] random: 7 urandom warning(s) missed due to ratelimiting
Jan 11 01:17:05 A51SERVER kernel: [   11.019459] uart-pl011 3f201000.serial: no DMA platform data
Jan 11 01:17:05 A51SERVER kernel: [   11.424419] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
Jan 11 01:17:05 A51SERVER udisksd[412]: udisks daemon version 2.8.1 starting
Jan 11 01:17:05 A51SERVER kernel: [   11.438448] 8021q: 802.1Q VLAN Support v1.8
Jan 11 01:17:06 A51SERVER udisksd[412]: failed to load module crypto: libbd_crypto.so.2: cannot open shared object file: No such file or directory
Jan 11 01:17:06 A51SERVER udisksd[412]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Jan 11 01:17:06 A51SERVER udisksd[412]: Failed to load the 'mdraid' libblockdev plugin
Jan 11 01:17:06 A51SERVER udisksd[412]: Failed to load the 'crypto' libblockdev plugin
Jan 11 01:17:07 A51SERVER kernel: [   12.696607] 8021q: adding VLAN 0 to HW filter on device eth0
Jan 11 01:17:07 A51SERVER lightdm[501]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Jan 11 01:17:07 A51SERVER udisksd[412]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Jan 11 01:17:08 A51SERVER vncserver-x11[514,root]: LogDestMem: Start replaying stored messages
Jan 11 01:17:08 A51SERVER vncserver-x11[514,root]: LogDestMem: Finished replaying stored messages
Jan 11 01:17:08 A51SERVER vncserver-x11[514,root]: ServerManager: Server started
Jan 11 01:17:08 A51SERVER vncserver-x11[514,root]: ConsoleDisplay: Cannot find a running X server on vt1
Jan 11 01:17:08 A51SERVER vncserver-x11[514,root]: ConsoleDisplay: Found running X server (pid=543, binary=/usr/lib/xorg/Xorg)
Jan 11 01:17:11 A51SERVER lightdm[834]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Jan 11 01:17:12 A51SERVER kernel: [   17.915950] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 11 01:17:12 A51SERVER kernel: [   17.946794] Bluetooth: Core ver 2.22
Jan 11 01:17:12 A51SERVER kernel: [   17.946883] NET: Registered protocol family 31
Jan 11 01:17:12 A51SERVER kernel: [   17.946889] Bluetooth: HCI device and connection manager initialized
Jan 11 01:17:12 A51SERVER kernel: [   17.946909] Bluetooth: HCI socket layer initialized
Jan 11 01:17:12 A51SERVER kernel: [   17.946919] Bluetooth: L2CAP socket layer initialized
Jan 11 01:17:12 A51SERVER kernel: [   17.946937] Bluetooth: SCO socket layer initialized
Jan 11 01:17:12 A51SERVER kernel: [   17.996906] Bluetooth: HCI UART driver ver 2.3
Jan 11 01:17:12 A51SERVER kernel: [   17.996927] Bluetooth: HCI UART protocol H4 registered
Jan 11 01:17:12 A51SERVER kernel: [   17.997034] Bluetooth: HCI UART protocol Three-wire (H5) registered
Jan 11 01:17:12 A51SERVER kernel: [   17.997237] Bluetooth: HCI UART protocol Broadcom registered
Jan 11 01:17:12 A51SERVER kernel: [   18.395309] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 11 01:17:12 A51SERVER kernel: [   18.395324] Bluetooth: BNEP filters: protocol multicast
Jan 11 01:17:12 A51SERVER kernel: [   18.395342] Bluetooth: BNEP socket layer initialized
Jan 11 01:17:16 A51SERVER kernel: [   21.678208] fuse: init (API version 7.32)
Jan 11 01:17:18 A51SERVER kernel: [   23.527019] Bluetooth: RFCOMM TTY layer initialized
Jan 11 01:17:18 A51SERVER kernel: [   23.527052] Bluetooth: RFCOMM socket layer initialized
Jan 11 01:17:18 A51SERVER kernel: [   23.527085] Bluetooth: RFCOMM ver 1.11
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Booting Linux on physical CPU 0x0
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Linux version 5.10.103-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1529 SMP Tue Mar 8 12:21:37 GMT 2022
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] CPU: div instructions available: patching division code
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] random: fast init done
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Memory policy: Data cache writealloc
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Reserved memory: created CMA memory pool at 0x37400000, size 64 MiB
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Zone ranges:
Jan 11 06:17:05 A51SERVER kernel: [    0.000000]   DMA      [mem 0x0000000000000000-0x000000003b3fffff]
Jan 11 06:17:05 A51SERVER kernel: [    0.000000]   Normal   empty
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Movable zone start for each node
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Early memory node ranges
Jan 11 06:17:05 A51SERVER kernel: [    0.000000]   node   0: [mem 0x0000000000000000-0x000000003b3fffff]
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003b3fffff]
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] percpu: Embedded 20 pages/cpu s50828 r8192 d22900 u81920
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=c7f6f68d-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Kernel parameter elevator= does not have any effect anymore.
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Please use sysfs to set IO scheduler for individual devices.
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] Memory: 878804K/970752K available (10240K kernel code, 1312K rwdata, 2952K rodata, 1024K init, 862K bss, 26412K reserved, 65536K cma-reserved)
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] ftrace: allocating 32081 entries in 95 pages
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] ftrace: allocated 94 pages with 5 groups
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] rcu: Hierarchical RCU implementation.
Jan 11 06:17:05 A51SERVER kernel: [    0.000000]        Rude variant of Tasks RCU enabled.
Jan 11 06:17:05 A51SERVER kernel: [    0.000000]        Tracing variant of Tasks RCU enabled.
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] random: get_random_bytes called from start_kernel+0x3ac/0x580 with crng_init=1
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Jan 11 06:17:05 A51SERVER kernel: [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Jan 11 06:17:05 A51SERVER kernel: [    0.000020] Switching to timer-based delay loop, resolution 52ns
Jan 11 06:17:05 A51SERVER kernel: [    0.000301] Console: colour dummy device 80x30
Jan 11 06:17:05 A51SERVER kernel: [    0.000374] printk: console [tty1] enabled
Jan 11 06:17:05 A51SERVER kernel: [    0.000426] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
Jan 11 06:17:05 A51SERVER kernel: [    0.000454] pid_max: default: 32768 minimum: 301
Jan 11 06:17:05 A51SERVER kernel: [    0.000661] LSM: Security Framework initializing
Jan 11 06:17:05 A51SERVER kernel: [    0.000904] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
Jan 11 06:17:05 A51SERVER kernel: [    0.000928] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
Jan 11 06:17:05 A51SERVER kernel: [    0.002373] cgroup: Disabling memory control group subsystem
Jan 11 06:17:05 A51SERVER kernel: [    0.002637] CPU: Testing write buffer coherency: ok
Jan 11 06:17:05 A51SERVER kernel: [    0.003132] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Jan 11 06:17:05 A51SERVER kernel: [    0.004366] Setting up static identity map for 0x100000 - 0x10003c
Jan 11 06:17:05 A51SERVER kernel: [    0.004551] rcu: Hierarchical SRCU implementation.
Jan 11 06:17:05 A51SERVER kernel: [    0.005467] smp: Bringing up secondary CPUs ...
Jan 11 06:17:05 A51SERVER kernel: [    0.006616] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Jan 11 06:17:05 A51SERVER kernel: [    0.007883] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
Jan 11 06:17:05 A51SERVER kernel: [    0.009080] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Jan 11 06:17:05 A51SERVER kernel: [    0.009238] smp: Brought up 1 node, 4 CPUs
Jan 11 06:17:05 A51SERVER kernel: [    0.009261] SMP: Total of 4 processors activated (153.60 BogoMIPS).
Jan 11 06:17:05 A51SERVER kernel: [    0.009272] CPU: All CPU(s) started in HYP mode.
Jan 11 06:17:05 A51SERVER kernel: [    0.009283] CPU: Virtualization extensions available.
Jan 11 06:17:05 A51SERVER mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
Jan 11 06:17:05 A51SERVER kernel: [    0.010380] devtmpfs: initialized
Jan 11 06:17:05 A51SERVER kernel: [    0.028287] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
Jan 11 06:17:05 A51SERVER kernel: [    0.028542] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Jan 11 06:17:05 A51SERVER kernel: [    0.028573] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Jan 11 06:17:05 A51SERVER mtp-probe: bus: 1, device: 4 was not an MTP device
Jan 11 06:17:05 A51SERVER kernel: [    0.031649] pinctrl core: initialized pinctrl subsystem
Jan 11 06:17:05 A51SERVER kernel: [    0.032820] NET: Registered protocol family 16
Jan 11 06:17:05 A51SERVER kernel: [    0.037192] DMA: preallocated 1024 KiB pool for atomic coherent allocations
Jan 11 06:17:05 A51SERVER kernel: [    0.042920] audit: initializing netlink subsys (disabled)
Jan 11 06:17:05 A51SERVER kernel: [    0.043242] audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1
Jan 11 06:17:05 A51SERVER mtp-probe: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.1"
Jan 11 06:17:05 A51SERVER kernel: [    0.043835] thermal_sys: Registered thermal governor 'step_wise'
Jan 11 06:17:05 A51SERVER kernel: [    0.044976] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
Jan 11 06:17:05 A51SERVER kernel: [    0.044992] hw-breakpoint: maximum watchpoint size is 8 bytes.
Jan 11 06:17:05 A51SERVER kernel: [    0.045290] Serial: AMBA PL011 UART driver
Jan 11 06:17:05 A51SERVER kernel: [    0.063531] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Jan 11 06:17:05 A51SERVER kernel: [    0.080119] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-12-01T15:07:06, variant start
Jan 11 06:17:05 A51SERVER kernel: [    0.090129] raspberrypi-firmware soc:firmware: Firmware hash is 71bd3109023a0c8575585ba87cbb374d2eeb038f
Jan 11 06:17:05 A51SERVER kernel: [    0.134480] Kprobes globally optimized
Jan 11 06:17:05 A51SERVER kernel: [    0.139460] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
Jan 11 06:17:05 A51SERVER kernel: [    0.141717] SCSI subsystem initialized
Jan 11 06:17:05 A51SERVER kernel: [    0.141981] usbcore: registered new interface driver usbfs
Jan 11 06:17:05 A51SERVER mtp-probe: bus: 1, device: 5 was not an MTP device
Jan 11 06:17:05 A51SERVER kernel: [    0.142045] usbcore: registered new interface driver hub
Jan 11 06:17:05 A51SERVER kernel: [    0.142119] usbcore: registered new device driver usb
Jan 11 06:17:05 A51SERVER kernel: [    0.144289] clocksource: Switched to clocksource arch_sys_counter
Jan 11 06:17:05 A51SERVER kernel: [    1.861346] VFS: Disk quotas dquot_6.6.0
Jan 11 06:17:05 A51SERVER kernel: [    1.861461] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jan 11 06:17:05 A51SERVER kernel: [    1.861664] FS-Cache: Loaded
Jan 11 06:17:05 A51SERVER kernel: [    1.861950] CacheFiles: Loaded
Jan 11 06:17:05 A51SERVER kernel: [    1.873128] NET: Registered protocol family 2
Jan 11 06:17:05 A51SERVER kernel: [    1.873404] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
Jan 11 06:17:05 A51SERVER kernel: [    1.875821] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
Jan 11 06:17:05 A51SERVER kernel: [    1.875886] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
Jan 11 06:17:05 A51SERVER kernel: [    1.876005] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
Jan 11 06:17:05 A51SERVER kernel: [    1.876197] TCP: Hash tables configured (established 8192 bind 8192)
Jan 11 06:17:05 A51SERVER kernel: [    1.876382] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
Jan 11 06:17:05 A51SERVER kernel: [    1.876438] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
Jan 11 06:17:05 A51SERVER kernel: [    1.876723] NET: Registered protocol family 1
Jan 11 06:17:05 A51SERVER kernel: [    1.877516] RPC: Registered named UNIX socket transport module.
Jan 11 06:17:05 A51SERVER kernel: [    1.877529] RPC: Registered udp transport module.
Jan 11 06:17:05 A51SERVER kernel: [    1.877541] RPC: Registered tcp transport module.
Jan 11 06:17:05 A51SERVER kernel: [    1.877553] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 11 06:17:05 A51SERVER kernel: [    1.879406] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
Jan 11 06:17:05 A51SERVER kernel: [    1.883137] Initialise system trusted keyrings
Jan 11 06:17:05 A51SERVER kernel: [    1.883421] workingset: timestamp_bits=14 max_order=18 bucket_order=4
Jan 11 06:17:05 A51SERVER kernel: [    1.892950] zbud: loaded
Jan 11 06:17:05 A51SERVER kernel: [    1.895060] FS-Cache: Netfs 'nfs' registered for caching
Jan 11 06:17:05 A51SERVER kernel: [    1.895939] NFS: Registering the id_resolver key type
Jan 11 06:17:05 A51SERVER kernel: [    1.895999] Key type id_resolver registered
Jan 11 06:17:05 A51SERVER kernel: [    1.896012] Key type id_legacy registered
Jan 11 06:17:05 A51SERVER kernel: [    1.896171] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
.........
En este último se ven un par de reinicios pero no veo ningún mensaje previo.... :avergonzado

Re: RPi3B+ se reinicia

Publicado: 11 Ene 2025, 18:51
por egrueda
La salida del comando "journalctl --list-boots" es... rara
Si la ejecutas otra vez ¿te sale lo mismo?
Por oro lado, ¿qué distribución y versión tienes instalada?

Re: RPi3B+ se reinicia

Publicado: 15 Ene 2025, 07:56
por walkandtalkblues
Buenas, si la salida de journal es bastante rara, me sale eso y luego un montón de renglones con el símbolo ~ y al final un recuadro con "END" (estoy hablando de memoria) del que no sé salir, suelo tener que reiniciar el Putty :guiño2

Ahora que le estoy dedicando algo de atención, voy acotando el tema y tengo novedades. Al menos desde que he solucionado el tema del voltage, los reinicios se dan todos los días a las mismas horas (con algún minuto de diferencia) 21:30, 2:00 y 6:30. Así que ya se pueden descartar inestabilidades o problemas de ese tipo, parece más bien algo programado. ¿Pueden ser actualizaciones o algo así?

La realidad es que todavía tampoco sé si se reinicia la raspberry o sólo el NodeRed.....ahora que ya tengo un horario, estaré atento a ver que veo.

Y la guinda a todo esto es la siguiente: Como la raspberry se reiniciaba y el reinicio me perturbaba el funcionamiento de unos relés, puse un arduino de intermediario, que se encarga de esos relés y se comunica con las RPI por mqtt. Pues resulta que el arduino también se reinicia a esas horas. Tengo que revisar el código para ver si la falta de comunicación con la raspberry puede provocarle el reinicio, pero me extraña...

Hoy comprobaré si los reinicios de la raspberry provocan reinicios del arduino y si no es así, ya solo me queda la opción de que se den cortes en la alimentación de ambos, ya que se alimentan del mismo sitio.

Saludos y gracias

Re: RPi3B+ se reinicia

Publicado: 28 Ene 2025, 12:41
por walkandtalkblues
Buenas, pues al final parece que eran reinicios provocados por microcortes en la alimentación... :avergonzado lo que nunca hubiese imaginado, ya que la energía viene de la batería solar pero pasando por el gestor de carga de ésta. Ahora la estoy alimentando directamente de la batería, en bruto, y ya no se reinicia...así que misterio resuelto, gracias por la ayuda e ideas prestadas.
Saludos

Re: RPi3B+ se reinicia

Publicado: 28 Ene 2025, 12:43
por egrueda
Uf, cuando la causa es externa es difícil de determinar:-/
Todos los horarios son UTC+02:00
Página 1 de 1

Desarrollado por phpBB® Forum Software © phpBB Limited

Traducción al español por phpBB España