Crash (arrêt) jeedom Raspberry PI4 plusieurs fois par jour

Bonjour
Depuis plusieurs semaines, j’ai des crash complet de mon jeedom :frowning:
Ca s’arrete plusieurs fois par jour, et au max ca tient 24h. (donc je reboote avec une prise Philips Hue)
Jeedom n’est plus accessible en local (la page ne répond pas). Le raspberry répond au ping mais c’est tout. (un SSH n’aboutit pas non plus par exemple).
Pas d’autre choix que le reboot éléctrique.
J’ai tenté une install + restauration du backup, mais ca n’a rien changé.
J’ai des tonnes de scénarios et capteurs, donc une fresh install sera le dernier dernier recours :frowning:
J’ai l’alim officielle du Raspberry, et je n’ai pas connu de problèmes au début (la plateforme a 2 ans d’age).

Avez vous des pistes de log à regarder ?
Est-ce que ca pourrait etre un problème hardware mais comment tester ?

Merci d’avance pour vos pistes.

Bonjour,

En 1er lieu essayer avec une carte SD neuve.

Donc l’OS est planté, et du coup tout le reste dont Jeedom

Ou un souci de carte SD ou un souci système mais il faudrait du coup regarder les logs systèmes.

Ou saturé… Faudrait vérifier la charge du serveur
Un PB de charge peut être du à un PB disque ou un PB de mauvais paramétrage de Jeedom

Si la machine pingue, c’est que l’os n’est pas planté

Je vois les remarques sur la carte SD :slight_smile:
J’avais oublié cette étape, mais ayant pensé à la meme chose, j’ai réinstallé mon jeedom il y a qqs mois sur un disque mSATA Transcend 64 Go SATA, donc hors cause a priori (meme symptômes)

Ah oui bien vu j’avais pas vu que le ping était OK.

Donc l’OS doit être totale a genoux.

Enfin sans log

Justement, quels logs pour avancer sur un debug ?

Coté charge j’ai ca :

top - 13:57:24 up  1:29,  3 users,  load average: 0.34, 0.78, 0.67
Tasks: 198 total,   1 running, 197 sleeping,   0 stopped,   0 zombie
%Cpu(s):  2.0 us,  1.2 sy,  0.0 ni, 96.7 id,  0.1 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   1848.2 total,    310.7 free,    708.6 used,    828.9 buff/cache
MiB Swap:    100.0 total,     89.2 free,     10.8 used.   1010.2 avail Mem

Santée Jeedom : tout est en vert

|Matériel|RPI 4 B|Système à jour|OK|
| --- | --- | --- | --- |
|Cron actif|OK|Scénario actif|OK|
|Démarré|OK 2024-09-12 11:18:04|Date système (dernière heure enregistrée)|OK 2024-09-12 13:56:36 (2024-09-12 13:16:01)|
|Droits sudo|OK|Version Jeedom|4.4.17|
|Version OS|debian 11.11|Version PHP|7.4.33|
|Nombre de processus Apache|11|Version OS|Linux raspberrySata 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux [11.11]|
|Version database|10.5.23-MariaDB-0+deb11u1|Espace disque libre|83 %|
|Connexion active/max/autorisée|12/28/151|Taille base de données|405.72 MB|
|Espace disque libre tmp|98 %|Mémoire disponible|54 % (Total 1848 Mo)|
|Mémoire suffisante|0|Erreur I/O|0|
|Swap disponible|89 % (Total 100 Mo)|Swapiness|10 %|
|Charge|0.47 - 0.89 - 0.7|Configuration réseau interne|OK|
|Configuration réseau externe|OK|Node|v20.17.0|
|Python|Python 3.9.2|Python 3|Python 3.9.2|
|Persistance du cache|OK (2024-09-12 13:30:06)|Apache private tmp|OK|
|Plugins|OK|

NB : sur cette dernière ré ré install, j’ai pas augmenté la taille swap (ca n’avait rien changé sur l’installé précédente)

Brancher un écran pourrait donner des pistes.

Bonjour,
C’est curieux, perso dans ce cas c’est plutôt la première chose que j’aurai faite.
Cela permet de repartir sur de bonnes bases, et d’être sûr du côté système support. Ensuite il sera toujours temps d’investiguer éventuellement du côté de Jeedom, ou du matériel lui-même.
D’autant plus que ce n’est pas tellement plus long, ni même risqué, que de refaire une installation complète, comme cela a déjà été fait visiblement…

Donc je préconiserai de repartir de zéro en claquant une image disque Debian 11 light (avec Raspberry Pi Imager par exemple) sur un disque fiable (SD, SSD, clé USB,…), puis une réinstallation de Jeedom suivi d’une restauration de la dernière sauvegarde.

1 « J'aime »

dmesg en shell our voir si il ne te détecte pas de secteurs defectueux au démarrage

Norbert

Je me suis surement mal exprimé mais c’est ce que j’ai fait : install neuve sur SSD mSATA (avec Raspberry Pi Imager), et réinstallation du backup.
Quand je dis que je veux éviter de tout ré-installer de zéro, c’est : sans remonter un backup. J’ai bcp de scripts, et objets !

Ah, ok… Oui, dans ce cas je comprend mieux en effet…

Voici le dmesg

Résumé
[    1.444033] Loading iSCSI transport class v2.0-870.
[    1.449468] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000
[    1.506888] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus
[    1.508091] usbcore: registered new interface driver r8152
[    1.508167] usbcore: registered new interface driver lan78xx
[    1.508236] usbcore: registered new interface driver smsc95xx
[    1.555700] pci 0000:00:00.0: enabling device (0000 -> 0002)
[    1.555896] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    1.555929] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[    1.556665] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0001e40000000890
[    1.557697] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    1.557719] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    1.557741] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[    1.558131] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[    1.558152] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.558167] usb usb1: Product: xHCI Host Controller
[    1.558181] usb usb1: Manufacturer: Linux 6.1.21-v8+ xhci-hcd
[    1.558193] usb usb1: SerialNumber: 0000:01:00.0
[    1.558984] hub 1-0:1.0: USB hub found
[    1.559053] hub 1-0:1.0: 1 port detected
[    1.559996] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01
[    1.560017] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.560032] usb usb2: Product: xHCI Host Controller
[    1.560045] usb usb2: Manufacturer: Linux 6.1.21-v8+ xhci-hcd
[    1.560057] usb usb2: SerialNumber: 0000:01:00.0
[    1.560716] hub 2-0:1.0: USB hub found
[    1.560811] hub 2-0:1.0: 4 ports detected
[    1.562575] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    1.562938] dwc_otg: FIQ enabled
[    1.562951] dwc_otg: NAK holdoff enabled
[    1.562961] dwc_otg: FIQ split-transaction FSM enabled
[    1.562977] Module dwc_common_port init
[    1.563573] usbcore: registered new interface driver uas
[    1.563687] usbcore: registered new interface driver usb-storage
[    1.563915] mousedev: PS/2 mouse device common for all mice
[    1.570435] sdhci: Secure Digital Host Controller Interface driver
[    1.570454] sdhci: Copyright(c) Pierre Ossman
[    1.571151] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.574792] ledtrig-cpu: registered to indicate activity on CPUs
[    1.575151] hid: raw HID events driver (C) Jiri Kosina
[    1.575356] usbcore: registered new interface driver usbhid
[    1.575370] usbhid: USB HID core driver
[    1.584341] NET: Registered PF_PACKET protocol family
[    1.584463] Key type dns_resolver registered
[    1.586047] registered taskstats version 1
[    1.586128] Loading compiled-in X.509 certificates
[    1.587108] Key type .fscrypt registered
[    1.587122] Key type fscrypt-provisioning registered
[    1.602842] uart-pl011 fe201000.serial: there is not valid maps for state default
[    1.603573] uart-pl011 fe201000.serial: cts_event_workaround enabled
[    1.603736] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2
[    1.612913] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    1.613378] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[    1.614698] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    1.614763] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated
[    1.644667] of_cfs_init
[    1.644815] of_cfs_init: OK
[    1.681694] mmc0: SDHCI controller on fe340000.mmc [fe340000.mmc] using ADMA
[    1.682016] Waiting for root device PARTUUID=54f887a8-02...
[    1.730245] mmc1: new high speed SDIO card at address 0001
[    1.814758] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    1.965419] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[    1.965442] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.965458] usb 1-1: Product: USB2.0 Hub
[    1.967075] hub 1-1:1.0: USB hub found
[    1.967385] hub 1-1:1.0: 4 ports detected
[    2.091179] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
[    2.112302] usb 2-2: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00
[    2.112322] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    2.112337] usb 2-2: Product: ASM1153E
[    2.112351] usb 2-2: Manufacturer: Inateck
[    2.112364] usb 2-2: SerialNumber: 123456789716
[    2.125422] scsi host0: uas
[    2.126758] scsi 0:0:0:0: Direct-Access     Inateck  ASM1153E         0    PQ: 0 ANSI: 6
[    2.129309] sd 0:0:0:0: [sda] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
[    2.129513] sd 0:0:0:0: [sda] Write Protect is off
[    2.129531] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[    2.129903] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.130398] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[    2.130416] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
[    2.134602]  sda: sda1 sda2
[    2.135177] sd 0:0:0:0: [sda] Attached SCSI disk
[    2.147377] EXT4-fs (sda2): INFO: recovery required on readonly filesystem
[    2.147401] EXT4-fs (sda2): write access will be enabled during recovery
[    2.262762] usb 1-1.3: new full-speed USB device number 3 using xhci_hcd
[    2.348578] EXT4-fs (sda2): orphan cleanup on readonly fs
[    2.354065] EXT4-fs (sda2): 42 orphan inodes deleted
[    2.354092] EXT4-fs (sda2): recovery complete
[    2.360960] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none.
[    2.361065] VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
[    2.363561] devtmpfs: mounted
[    2.372546] Freeing unused kernel memory: 4160K
[    2.372751] Run /sbin/init as init process
[    2.372762]   with arguments:
[    2.372771]     /sbin/init
[    2.372781]     splash
[    2.372791]   with environment:
[    2.372799]     HOME=/
[    2.372809]     TERM=linux
[    2.546042] systemd[1]: System time before build time, advancing clock.
[    2.699103] NET: Registered PF_INET6 protocol family
[    2.701024] Segment Routing with IPv6
[    2.701068] In-situ OAM (IOAM) with IPv6
[    2.751767] systemd[1]: systemd 247.3-7+deb11u6 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[    2.752767] systemd[1]: Detected architecture arm64.
[    2.753952] systemd[1]: Set hostname to <raspberrySata>.
[    3.014530] usb 1-1.3: New USB device found, idVendor=0463, idProduct=ffff, bcdDevice= 1.00
[    3.014570] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=4
[    3.014587] usb 1-1.3: Product: Eaton 3S
[    3.014601] usb 1-1.3: Manufacturer: EATON
[    3.014615] usb 1-1.3: SerialNumber: Blank
[    3.369963] systemd[1]: /lib/systemd/system/plymouth-start.service:16: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[    3.513371] systemd[1]: Queued start job for default target Graphical Interface.
[    3.536435] systemd[1]: Created slice system-getty.slice.
[    3.537769] systemd[1]: Created slice system-modprobe.slice.
[    3.538816] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    3.539629] systemd[1]: Created slice User and Session Slice.
[    3.540140] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    3.541303] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    3.541797] systemd[1]: Reached target Slices.
[    3.541938] systemd[1]: Reached target Swap.
[    3.544302] systemd[1]: Listening on Syslog Socket.
[    3.545112] systemd[1]: Listening on fsck to fsckd communication Socket.
[    3.545507] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    3.548248] systemd[1]: Listening on Journal Audit Socket.
[    3.549134] systemd[1]: Listening on Journal Socket (/dev/log).
[    3.550123] systemd[1]: Listening on Journal Socket.
[    3.551702] systemd[1]: Listening on udev Control Socket.
[    3.552498] systemd[1]: Listening on udev Kernel Socket.
[    3.553481] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[    3.575267] systemd[1]: Mounting POSIX Message Queue File System...
[    3.580014] systemd[1]: Mounting RPC Pipe File System...
[    3.585746] systemd[1]: Mounting Kernel Debug File System...
[    3.591382] systemd[1]: Mounting Kernel Trace File System...
[    3.592149] systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped.
[    3.598561] systemd[1]: Starting Restore / save the current clock...
[    3.604551] systemd[1]: Starting Set the console keyboard layout...
[    3.610248] systemd[1]: Starting Create list of static device nodes for the current kernel...
[    3.616187] systemd[1]: Starting Load Kernel Module configfs...
[    3.622203] systemd[1]: Starting Load Kernel Module drm...
[    3.635950] systemd[1]: Starting Load Kernel Module fuse...
[    3.638446] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[    3.644067] systemd[1]: Starting File System Check on Root Device...
[    3.654229] systemd[1]: Starting Journal Service...
[    3.662308] systemd[1]: Starting Load Kernel Modules...
[    3.679536] systemd[1]: Starting Coldplug All udev Devices...
[    3.703895] systemd[1]: Mounted POSIX Message Queue File System.
[    3.704827] systemd[1]: Mounted RPC Pipe File System.
[    3.705830] systemd[1]: Mounted Kernel Debug File System.
[    3.706677] systemd[1]: Mounted Kernel Trace File System.
[    3.718886] systemd[1]: Finished Restore / save the current clock.
[    3.720731] fuse: init (API version 7.37)
[    3.721937] systemd[1]: Finished Create list of static device nodes for the current kernel.
[    3.724258] systemd[1]: modprobe@configfs.service: Succeeded.
[    3.727095] systemd[1]: Finished Load Kernel Module configfs.
[    3.730860] systemd[1]: modprobe@fuse.service: Succeeded.
[    3.739592] systemd[1]: Finished Load Kernel Module fuse.
[    3.739993] i2c_dev: i2c /dev entries driver
[    3.763461] systemd[1]: Mounting FUSE Control File System...
[    3.779332] systemd[1]: Mounting Kernel Configuration File System...
[    3.784604] systemd[1]: Started File System Check Daemon to report status.
[    3.818909] systemd[1]: Finished Load Kernel Modules.
[    3.823979] systemd[1]: Mounted FUSE Control File System.
[    3.824823] systemd[1]: Mounted Kernel Configuration File System.
[    3.859808] systemd[1]: Starting Apply Kernel Variables...
[    3.862648] systemd[1]: modprobe@drm.service: Succeeded.
[    3.864609] systemd[1]: Finished Load Kernel Module drm.
[    3.917930] systemd[1]: Finished File System Check on Root Device.
[    3.923318] systemd[1]: Starting Remount Root and Kernel File Systems...
[    3.949327] systemd[1]: Finished Apply Kernel Variables.
[    4.047180] systemd[1]: Started Journal Service.
[    4.052090] EXT4-fs (sda2): re-mounted. Quota mode: none.
[    4.166288] systemd-journald[147]: Received client request to flush runtime journal.
[    4.359121] systemd-journald[147]: File /var/log/journal/e85e3900efe5447ea82290b4e8cca2ac/system.journal corrupted or uncleanly shut down, renaming and replacing.
[    5.218475] mc: Linux media interface: v0.10
[    5.312077] videodev: Linux video capture interface: v2.00
[    5.333923] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[    5.381223] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[    5.381267] [vc_sm_connected_init]: start
[    5.395271] [vc_sm_connected_init]: installed successfully
[    5.443159] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    5.454388] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[    5.457629] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    5.466974] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    5.480790] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[    5.495817] rpivid_hevc: module is from the staging directory, the quality is unknown, you have been warned.
[    5.504174] bcm2835_audio bcm2835_audio: card created with 8 channels
[    5.517382] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[    5.520359] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[    5.525573] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[    5.526586] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[    5.528248] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[    5.528302] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[    5.528339] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[    5.528357] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[    5.528374] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[    5.556172] brcmstb-i2c fef04500.i2c:  @97500hz registered in polling mode
[    5.560475] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video20
[    5.561593] rpivid feb10000.codec: Device registered as /dev/video19
[    5.563902] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video21
[    5.567716] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video22
[    5.571040] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video23
[    5.571091] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[    5.571114] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[    5.571132] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[    5.571149] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[    5.572692] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[    5.572990] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[    5.573050] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[    5.591881] brcmstb-i2c fef09500.i2c:  @97500hz registered in polling mode
[    5.603560] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[    5.603625] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[    5.623119] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[    5.623186] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[    5.640318] bcm2835-codec bcm2835-codec: Device registered as /dev/video18
[    5.640409] bcm2835-codec bcm2835-codec: Loaded V4L2 image_fx
[    5.663769] bcm2835-codec bcm2835-codec: Device registered as /dev/video31
[    5.663828] bcm2835-codec bcm2835-codec: Loaded V4L2 encode_image
[    5.792651] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0
[    5.849283] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    5.928070] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    5.990629] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    5.998679] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
[    6.080968] hid-generic 0003:0463:FFFF.0001: hiddev96,hidraw0: USB HID v1.10 Device [EATON Eaton 3S] on usb-0000:01:00.0-1.3/input0
[    6.178358] brcmfmac: F1 signature read @0x18000000=0x15264345
[    6.187726] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    6.198842] usb 1-1.4: new full-speed USB device number 4 using xhci_hcd
[    6.207419] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])
[    6.230373] Registered IR keymap rc-cec
[    6.230613] rc rc0: vc4-hdmi-0 as /devices/platform/soc/fef00700.hdmi/rc/rc0
[    6.230913] input: vc4-hdmi-0 as /devices/platform/soc/fef00700.hdmi/rc/rc0/input0
[    6.242350] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops [vc4])
[    6.245412] Registered IR keymap rc-cec
[    6.245639] rc rc1: vc4-hdmi-1 as /devices/platform/soc/fef05700.hdmi/rc/rc1
[    6.245900] input: vc4-hdmi-1 as /devices/platform/soc/fef05700.hdmi/rc/rc1/input1
[    6.250872] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops [vc4])
[    6.251481] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops [vc4])
[    6.251930] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4])
[    6.252357] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4])
[    6.252772] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4])
[    6.253069] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4])
[    6.253477] vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops [vc4])
[    6.257341] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1
[    6.258127] vc4-drm gpu: [drm] Cannot find any crtc or sizes
[    6.308213] usb 1-1.4: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[    6.308255] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.308273] usb 1-1.4: Product: ConBee II
[    6.308288] usb 1-1.4: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[    6.308302] usb 1-1.4: SerialNumber: DE2474501
[    6.431800] usbcore: registered new interface driver brcmfmac
[    6.447931] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Nov  1 2021 00:37:25 version 7.45.241 (1a2f2fa CY) FWID 01-703fd60
[    7.118833] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device
[    7.119127] usbcore: registered new interface driver cdc_acm
[    7.119146] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    7.391792] uart-pl011 fe201000.serial: no DMA platform data
[    7.598381] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k FS
[    8.137811] 8021q: 802.1Q VLAN Support v1.8
[    8.557156] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[    8.814253] bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay)
[    8.816892] bcmgenet fd580000.ethernet eth0: Link is Down
[   12.895019] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   12.895070] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   14.899949] Bluetooth: Core ver 2.22
[   14.900048] NET: Registered PF_BLUETOOTH protocol family
[   14.900054] Bluetooth: HCI device and connection manager initialized
[   14.900070] Bluetooth: HCI socket layer initialized
[   14.900077] Bluetooth: L2CAP socket layer initialized
[   14.900091] Bluetooth: SCO socket layer initialized
[   14.907756] Bluetooth: HCI UART driver ver 2.3
[   14.907777] Bluetooth: HCI UART protocol H4 registered
[   14.907843] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   14.908013] Bluetooth: HCI UART protocol Broadcom registered
[   15.051166] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   15.051195] Bluetooth: BNEP filters: protocol multicast
[   15.051214] Bluetooth: BNEP socket layer initialized
[   15.056087] Bluetooth: MGMT ver 1.22
[   15.064342] NET: Registered PF_ALG protocol family
[   15.135982] Bluetooth: RFCOMM TTY layer initialized
[   15.136011] Bluetooth: RFCOMM socket layer initialized
[   15.136030] Bluetooth: RFCOMM ver 1.11
[   71.338410] tun: Universal TUN/TAP device driver, 1.6

Essayer avec une autre alim alors. Un SSD même msata ça tête un peu.

Bonsoir à tous,
@jjlc je pense avoir un peu près le même problème que toi. Depuis le 31/10/24, mon jeedom était planté, plus de SSH et le raspberry ne répondait plus à rien. Seul solution l’éteindre brutalement et électriquement. Mais même en le rallumant, toujours même symptômes.
Par contre, si je débranche ma clé ConbeeII et en redémarrant le raspberry, là tout refonctionne (jeedom, ping, SSH, etc…).
Je ne pense que ça vienne de l’alim (c’est l’officiel raspberry qui fonctionne sans soucis depuis plus de 3 ans H24).
D’où cela peut-il venir ?
Je précise que je suis sur un raspberry Pi 4 sous Debian 10. Pas de carte microSD, l’OS est sur un DD et rien d’autre de branché dessus à part ma ConbeeII qui semble être à l’origine du problème.