Neue Installation von piVCCU3 klappt nicht!

Virtualisierte CCU für Raspberry Pi und Clones

Moderator: Co-Administratoren

Slice
Beiträge: 1201
Registriert: 03.02.2016, 14:44
System: Alternative CCU (auf Basis OCCU)
Wohnort: irgendwo aus Süd BaWü
Hat sich bedankt: 141 Mal
Danksagung erhalten: 85 Mal

Neue Installation von piVCCU3 klappt nicht!

Beitrag von Slice » 16.01.2021, 16:23

Hallo zusammen,

nachdem meine Produktivzentrale Probleme beim Reboot macht, wollte ich heute auf einem neuen Raspi3B+ mit zweiter HB-RF-ETH und dem alten kleinen Funkmodul eine ganz neue Installation aufsetzen.
Neue SD rein und das letzte Image RaspberryPiOS_lite_piVCCU3_2020-12-07 auf die Karte gepackt.
Den Pi mit der Karte gebootet und erstmal per sudo apt update && sudo apt upgrade geupdatet.
Jetzt kommts, egal was ich mache, nach jedem Reboot startet er piVCCU3 nicht mehr.
Ich bekomme immer:

Code: Alles auswählen

pi@raspberrypi:~ $ sudo systemctl status pivccu.service
● pivccu.service - piVCCU
   Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-01-16 16:11:16 CET; 8s ago
  Process: 933 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS)
 Main PID: 1163 (code=exited, status=1/FAILURE)

Jan 16 16:11:15 raspberrypi piVCCU3[1012]: HMIP hardware was not detected
Jan 16 16:11:15 raspberrypi start_container.sh[933]: <12>Jan 16 16:11:15 piVCCU3: HMIP hardware was not detected
Jan 16 16:11:15 raspberrypi start_container.sh[933]: kernel.sched_rt_runtime_us = -1
Jan 16 16:11:16 raspberrypi start_container.sh[933]: lxc-start: lxc: lxccontainer.c: wait_on_daemonized_start: 842 Received container state "ABORTING" instead of "RUNNING"
Jan 16 16:11:16 raspberrypi start_container.sh[933]: lxc-start: lxc: tools/lxc_start.c: main: 330 The container failed to start
Jan 16 16:11:16 raspberrypi start_container.sh[933]: lxc-start: lxc: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Jan 16 16:11:16 raspberrypi start_container.sh[933]: lxc-start: lxc: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
Jan 16 16:11:16 raspberrypi systemd[1]: Started piVCCU.
Jan 16 16:11:16 raspberrypi systemd[1]: pivccu.service: Main process exited, code=exited, status=1/FAILURE
Jan 16 16:11:16 raspberrypi systemd[1]: pivccu.service: Failed with result 'exit-code'.
Folglich geht auch ein:

Code: Alles auswählen

pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 3.53.34-51
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi UART:   Assigned to GPIO pins
HMRF Hardware:  HM-MOD-RPI-PCB
 Connected via: HB-RF-ETH@10.1.1.31 (/dev/raw-uart1)
 Board serial:  NEQ1330587
 Radio MAC:     0x4F6E2C
HMIP Hardware:  HM-MOD-RPI-PCB
 SGTIN:         3014F711A061A7D5699DB59B
 Radio MAC:     0xB62441
State:          STOPPED
nicht erfolgreich, State: STOPPED.

sudo dpkg-reconfigure pivccu-modules-dkms hab ich auch schon versucht. Ändert aber nichts, ich bekomme jedesmal pivccu.service: Failed with result 'exit-code'.

Gibt es Probleme wenn auf dem pi3 kein Funkmodul steckt bei der Ersteinrichtung?? Oder was mache ich den falsch?

Grüße,
Slice
----------------------------------------------------------------------------------------
Raspi3B+ Bullseye mit HB-RF-ETH und RPI-RF-MOD auf piVCCU-FW 3.75.7 / Addons: CuxD v2.11 - E-Mail v1.7.6 - Patcher v1.0.0 - Philips Hue v3.2.5 - Programme drucken v2.6 - Scriptparser v1.11 - XML-API v2.3
Geräte: 141 / Kanäle: 791 / Datenpunkte: 6080 / SysVars: 275 / Programme: 161 / Regadom IDs: 14010 / 48 CUxD-Kanäle in 3 CUxD-Geräten
Intel NUC i3-5010U @ 2,1 GHz mit 16 GB RAM & 512 GB SSD für Proxmox mit ioBroker VM und CCU-Historian/InfluxDB/Grafana VM
----------------------------------------------------------------------------------------
Projekte im Forum: HomeHub v4.1 / Fritzbox-Anruferliste für HomeHub
----------------------------------------------------------------------------------------

Slice
Beiträge: 1201
Registriert: 03.02.2016, 14:44
System: Alternative CCU (auf Basis OCCU)
Wohnort: irgendwo aus Süd BaWü
Hat sich bedankt: 141 Mal
Danksagung erhalten: 85 Mal

Re: Neue Installation von piVCCU3 klappt nicht!

Beitrag von Slice » 16.01.2021, 16:58

So, jetzt hab ich es einmal geschafft piVCCU3 zu starten!

Nachdem ich mit sudo systemctl restart monitor-hb-rf-eth neugestartet hatte, war die Platine nun verbunden:

Code: Alles auswählen

pi@raspberrypi:~ $ journalctl -xe
--
-- The process' exit code is 'exited' and its exit status is 1.
Jan 16 16:50:23 raspberrypi systemd[1]: pivccu.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pivccu.service has entered the 'failed' state with result 'exit-code'.
Jan 16 16:50:23 raspberrypi kernel: br0: port 2(vethpivccu) entered disabled state
Jan 16 16:50:23 raspberrypi kernel: device vethpivccu left promiscuous mode
Jan 16 16:50:23 raspberrypi kernel: br0: port 2(vethpivccu) entered disabled state
Jan 16 16:50:28 raspberrypi sudo[1277]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/systemctl status pivccu.service
Jan 16 16:50:28 raspberrypi sudo[1277]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
Jan 16 16:50:32 raspberrypi kernel: hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
Jan 16 16:50:32 raspberrypi kernel: hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
Jan 16 16:50:32 raspberrypi kernel: hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
Jan 16 16:50:41 raspberrypi kernel: hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
Jan 16 16:50:41 raspberrypi kernel: hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
Jan 16 16:50:41 raspberrypi kernel: hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
Jan 16 16:50:51 raspberrypi kernel: hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
Jan 16 16:50:51 raspberrypi kernel: hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
Jan 16 16:50:51 raspberrypi kernel: hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
Jan 16 16:50:52 raspberrypi sudo[1304]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/systemctl status monitor-hb-rf-eth
Jan 16 16:50:52 raspberrypi sudo[1304]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
Jan 16 16:50:52 raspberrypi sudo[1304]: pam_unix(sudo:session): session closed for user root
Jan 16 16:51:00 raspberrypi kernel: hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
Jan 16 16:51:00 raspberrypi kernel: hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
Jan 16 16:51:00 raspberrypi kernel: hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
Dann mit sudo systemctl restart pivccu

Code: Alles auswählen

pi@raspberrypi:~ $ sudo systemctl status pivccu.service
● pivccu.service - piVCCU
   Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2021-01-16 16:53:01 CET; 13s ago
  Process: 1424 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS)
 Main PID: 1638 (lxc-start)
    Tasks: 1 (limit: 2063)
   CGroup: /system.slice/pivccu.service
           └─1638 /usr/bin/lxc-start --lxcpath /var/lib/piVCCU3 --name lxc --pidfile /var/run/pivccu3.pid --daemon

Jan 16 16:52:34 raspberrypi systemd[1]: Starting piVCCU...
Jan 16 16:53:01 raspberrypi start_container.sh[1424]: kernel.sched_rt_runtime_us = -1
Jan 16 16:53:01 raspberrypi systemd[1]: Started piVCCU.
und sudo pivccu-info

Code: Alles auswählen

pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 3.53.34-51
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi UART:   Assigned to GPIO pins
HMRF Hardware:  HM-MOD-RPI-PCB
 Connected via: HB-RF-ETH@10.1.1.31 (/dev/raw-uart1)
 Board serial:  NEQ1330587
 Radio MAC:     0x4F6E2C
HMIP Hardware:  HM-MOD-RPI-PCB
 SGTIN:         3014F711A061A7D5699DB59B
 Radio MAC:     0xB62441
State:          RUNNING
PID:            1654
IP:             10.1.1.35
CPU use:        20.68 seconds
Link:           vethpivccu
 TX bytes:      11.50 KiB
 RX bytes:      49.13 KiB
 Total bytes:   60.63 KiB
komme ich nun auf die Webui.

Jetzt bin ich mal gespannt ob das auch einen reboot überlebt!!

Grüße,
Slice
----------------------------------------------------------------------------------------
Raspi3B+ Bullseye mit HB-RF-ETH und RPI-RF-MOD auf piVCCU-FW 3.75.7 / Addons: CuxD v2.11 - E-Mail v1.7.6 - Patcher v1.0.0 - Philips Hue v3.2.5 - Programme drucken v2.6 - Scriptparser v1.11 - XML-API v2.3
Geräte: 141 / Kanäle: 791 / Datenpunkte: 6080 / SysVars: 275 / Programme: 161 / Regadom IDs: 14010 / 48 CUxD-Kanäle in 3 CUxD-Geräten
Intel NUC i3-5010U @ 2,1 GHz mit 16 GB RAM & 512 GB SSD für Proxmox mit ioBroker VM und CCU-Historian/InfluxDB/Grafana VM
----------------------------------------------------------------------------------------
Projekte im Forum: HomeHub v4.1 / Fritzbox-Anruferliste für HomeHub
----------------------------------------------------------------------------------------

Slice
Beiträge: 1201
Registriert: 03.02.2016, 14:44
System: Alternative CCU (auf Basis OCCU)
Wohnort: irgendwo aus Süd BaWü
Hat sich bedankt: 141 Mal
Danksagung erhalten: 85 Mal

Re: Neue Installation von piVCCU3 klappt nicht!

Beitrag von Slice » 16.01.2021, 17:04

Slice hat geschrieben:
16.01.2021, 16:58
Jetzt bin ich mal gespannt ob das auch einen reboot überlebt!!
Leider nein, nach einem Reboot wieder das gleiche:

Code: Alles auswählen

pi@raspberrypi:~ $ sudo systemctl status pivccu.service
● pivccu.service - piVCCU
   Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-01-16 17:00:32 CET; 1min 40s ago
  Process: 531 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS)
 Main PID: 781 (code=exited, status=1/FAILURE)

Jan 16 17:00:31 raspberrypi piVCCU3[628]: HMIP hardware was not detected
Jan 16 17:00:31 raspberrypi start_container.sh[531]: <12>Jan 16 17:00:31 piVCCU3: HMIP hardware was not detected
Jan 16 17:00:31 raspberrypi start_container.sh[531]: kernel.sched_rt_runtime_us = -1
Jan 16 17:00:32 raspberrypi start_container.sh[531]: lxc-start: lxc: lxccontainer.c: wait_on_daemonized_start: 842 Received container state "ABORTING" instead of "RUNNING"
Jan 16 17:00:32 raspberrypi start_container.sh[531]: lxc-start: lxc: tools/lxc_start.c: main: 330 The container failed to start
Jan 16 17:00:32 raspberrypi start_container.sh[531]: lxc-start: lxc: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Jan 16 17:00:32 raspberrypi start_container.sh[531]: lxc-start: lxc: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
Jan 16 17:00:32 raspberrypi systemd[1]: Started piVCCU.
Jan 16 17:00:32 raspberrypi systemd[1]: pivccu.service: Main process exited, code=exited, status=1/FAILURE
Jan 16 17:00:32 raspberrypi systemd[1]: pivccu.service: Failed with result 'exit-code'.
Ich verstehe nicht warum piVCCU nicht startet... :?:
----------------------------------------------------------------------------------------
Raspi3B+ Bullseye mit HB-RF-ETH und RPI-RF-MOD auf piVCCU-FW 3.75.7 / Addons: CuxD v2.11 - E-Mail v1.7.6 - Patcher v1.0.0 - Philips Hue v3.2.5 - Programme drucken v2.6 - Scriptparser v1.11 - XML-API v2.3
Geräte: 141 / Kanäle: 791 / Datenpunkte: 6080 / SysVars: 275 / Programme: 161 / Regadom IDs: 14010 / 48 CUxD-Kanäle in 3 CUxD-Geräten
Intel NUC i3-5010U @ 2,1 GHz mit 16 GB RAM & 512 GB SSD für Proxmox mit ioBroker VM und CCU-Historian/InfluxDB/Grafana VM
----------------------------------------------------------------------------------------
Projekte im Forum: HomeHub v4.1 / Fritzbox-Anruferliste für HomeHub
----------------------------------------------------------------------------------------

Slice
Beiträge: 1201
Registriert: 03.02.2016, 14:44
System: Alternative CCU (auf Basis OCCU)
Wohnort: irgendwo aus Süd BaWü
Hat sich bedankt: 141 Mal
Danksagung erhalten: 85 Mal

Re: Neue Installation von piVCCU3 klappt nicht!

Beitrag von Slice » 17.01.2021, 11:24

Guten Morgen,

ich bin jetzt über das testing Repo auf der v3.55.5 und habe hier immer noch das gleiche Verhalten. piVCCU startet einfach nicht!
Aus lauter Verzweiflung bin ich bei der HB-RF-ETH auch mal auf die FW 1.23 zurück. Meine Vermutung das die Platine irgendwie beim booten nicht erkannt wird.
Egal wie, ich boote den Pi3 neu und piVCCU startet nicht. Erst nachdem ich die Shell Befehle eingebe bekomme ich piVCCU zum laufen.

@Alex: Irgendeine Idee was hier schief läuft?? Das gleiche Verhalten habe ich auf meinen produktiv System auch.. was etwas ärgerlich ist wenn die Zentrale mal abschmiert!

Schönen verschneiten Sonntag noch..
Slice
----------------------------------------------------------------------------------------
Raspi3B+ Bullseye mit HB-RF-ETH und RPI-RF-MOD auf piVCCU-FW 3.75.7 / Addons: CuxD v2.11 - E-Mail v1.7.6 - Patcher v1.0.0 - Philips Hue v3.2.5 - Programme drucken v2.6 - Scriptparser v1.11 - XML-API v2.3
Geräte: 141 / Kanäle: 791 / Datenpunkte: 6080 / SysVars: 275 / Programme: 161 / Regadom IDs: 14010 / 48 CUxD-Kanäle in 3 CUxD-Geräten
Intel NUC i3-5010U @ 2,1 GHz mit 16 GB RAM & 512 GB SSD für Proxmox mit ioBroker VM und CCU-Historian/InfluxDB/Grafana VM
----------------------------------------------------------------------------------------
Projekte im Forum: HomeHub v4.1 / Fritzbox-Anruferliste für HomeHub
----------------------------------------------------------------------------------------

wok1415
Beiträge: 118
Registriert: 16.07.2020, 15:52
System: Alternative CCU (auf Basis OCCU)
Hat sich bedankt: 1 Mal
Danksagung erhalten: 3 Mal

Re: Neue Installation von piVCCU3 klappt nicht!

Beitrag von wok1415 » 17.01.2021, 11:45

Vielleicht versuchst Du es mal damit:

Code: Alles auswählen

# systemctl enable pivccu
Für die pivccu3 (v.3.55.5) und die HB-RF-ETH Platine (v.1.2.8 mit RPI-RF-MOD) habe ich eine statische IP vergeben - ist aber nicht nötig. Auf einem Pi4 und einem Server mit Armbian funktioniert das stabil (bis auf die bekannten Bugs).
Zuletzt geändert von wok1415 am 17.01.2021, 12:54, insgesamt 1-mal geändert.

Slice
Beiträge: 1201
Registriert: 03.02.2016, 14:44
System: Alternative CCU (auf Basis OCCU)
Wohnort: irgendwo aus Süd BaWü
Hat sich bedankt: 141 Mal
Danksagung erhalten: 85 Mal

Re: Neue Installation von piVCCU3 klappt nicht!

Beitrag von Slice » 17.01.2021, 12:26

Hi wok1415,

hab ich mal ausprobiert und danach einen Reboot durchgeführt.
Immer noch diese Meldung:

Code: Alles auswählen

pi@raspberrypi:~ $ sudo systemctl status pivccu.service
● pivccu.service - piVCCU
   Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2021-01-17 12:23:23 CET; 2min 3s ago
  Process: 1042 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS)
 Main PID: 1249 (code=exited, status=1/FAILURE)

Jan 17 12:23:21 raspberrypi piVCCU3[1083]: HMIP hardware was not detected
Jan 17 12:23:21 raspberrypi start_container.sh[1042]: <12>Jan 17 12:23:21 piVCCU3: HMIP hardware was not detected
Jan 17 12:23:22 raspberrypi start_container.sh[1042]: kernel.sched_rt_runtime_us = -1
Jan 17 12:23:22 raspberrypi start_container.sh[1042]: lxc-start: lxc: lxccontainer.c: wait_on_daemonized_start: 842 Received container state "ABORTING" instead of "RUNNING"
Jan 17 12:23:22 raspberrypi start_container.sh[1042]: lxc-start: lxc: tools/lxc_start.c: main: 330 The container failed to start
Jan 17 12:23:22 raspberrypi start_container.sh[1042]: lxc-start: lxc: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Jan 17 12:23:22 raspberrypi start_container.sh[1042]: lxc-start: lxc: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
Jan 17 12:23:22 raspberrypi systemd[1]: Started piVCCU.
Jan 17 12:23:23 raspberrypi systemd[1]: pivccu.service: Main process exited, code=exited, status=1/FAILURE
Jan 17 12:23:23 raspberrypi systemd[1]: pivccu.service: Failed with result 'exit-code'.
Kannst Du Deine piVCCU neustarten ohne Probleme?

DHCP macht bei mir ein Windows Server, das läuft auch zuverlässig. Daran sollte es nicht liegen..

EDIT:
Nach dem 2ten oder 3ten mal sudo systemctl restart pivccu gehts:

Code: Alles auswählen

pi@raspberrypi:~ $ sudo systemctl status pivccu.service
● pivccu.service - piVCCU
   Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2021-01-17 12:27:51 CET; 5s ago
  Process: 1549 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS)
 Main PID: 1779 (lxc-start)
    Tasks: 1 (limit: 2063)
   CGroup: /system.slice/pivccu.service
           └─1779 /usr/bin/lxc-start --lxcpath /var/lib/piVCCU3 --name lxc --pidfile /var/run/pivccu3.pid --daemon

Jan 17 12:27:24 raspberrypi systemd[1]: Starting piVCCU...
Jan 17 12:27:51 raspberrypi start_container.sh[1549]: kernel.sched_rt_runtime_us = -1
Jan 17 12:27:51 raspberrypi systemd[1]: Started piVCCU.

Code: Alles auswählen

pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 3.55.5-53
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi UART:   Assigned to GPIO pins
HMRF Hardware:  HM-MOD-RPI-PCB
 Connected via: HB-RF-ETH@10.1.1.31 (/dev/raw-uart1)
 Board serial:  NEQ1330587
 Radio MAC:     0x4F6E2C
HMIP Hardware:  HM-MOD-RPI-PCB
 SGTIN:         3014F711A061A7D5699DB59B
 Radio MAC:     0xB62441
State:          RUNNING
PID:            1793
IP:             10.1.1.35
CPU use:        21.20 seconds
Link:           vethpivccu
 TX bytes:      794.73 KiB
 RX bytes:      76.35 KiB
 Total bytes:   871.08 KiB

Ich hoffe das Alex noch eine Idee hat was hier schief läuft!

Grüße,
Slice
----------------------------------------------------------------------------------------
Raspi3B+ Bullseye mit HB-RF-ETH und RPI-RF-MOD auf piVCCU-FW 3.75.7 / Addons: CuxD v2.11 - E-Mail v1.7.6 - Patcher v1.0.0 - Philips Hue v3.2.5 - Programme drucken v2.6 - Scriptparser v1.11 - XML-API v2.3
Geräte: 141 / Kanäle: 791 / Datenpunkte: 6080 / SysVars: 275 / Programme: 161 / Regadom IDs: 14010 / 48 CUxD-Kanäle in 3 CUxD-Geräten
Intel NUC i3-5010U @ 2,1 GHz mit 16 GB RAM & 512 GB SSD für Proxmox mit ioBroker VM und CCU-Historian/InfluxDB/Grafana VM
----------------------------------------------------------------------------------------
Projekte im Forum: HomeHub v4.1 / Fritzbox-Anruferliste für HomeHub
----------------------------------------------------------------------------------------


Slice
Beiträge: 1201
Registriert: 03.02.2016, 14:44
System: Alternative CCU (auf Basis OCCU)
Wohnort: irgendwo aus Süd BaWü
Hat sich bedankt: 141 Mal
Danksagung erhalten: 85 Mal

Re: Neue Installation von piVCCU3 klappt nicht!

Beitrag von Slice » 17.01.2021, 12:45

Code: Alles auswählen

pi@raspberrypi:~ $ dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.4.83-v7+ (dom@buildbot) (gcc version 8.4.0 (Ubuntu/Linaro 8.4.0-3ubuntu1)) #1379 SMP Mon Dec 14 13:08:57 GMT 2020
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Reserved memory: created CMA memory pool at 0x37400000, size 64 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] On node 0 totalpages: 242688
[    0.000000]   Normal zone: 2133 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 242688 pages, LIFO batch:63
[    0.000000] percpu: Embedded 20 pages/cpu s49740 r8192 d23988 u81920
[    0.000000] pcpu-alloc: s49740 r8192 d23988 u81920 alloc=20*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1360 bcm2708_fb.fbheight=768 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=tty1 root=PARTUUID=cc91ff97-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 880476K/970752K available (9216K kernel code, 698K rwdata, 2608K rodata, 1024K init, 827K bss, 24740K reserved, 65536K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 29205 entries in 58 pages
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] random: get_random_bytes called from start_kernel+0x324/0x4f8 with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000003] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000009] Switching to timer-based delay loop, resolution 52ns
[    0.000140] Console: colour dummy device 80x30
[    0.000398] printk: console [tty1] enabled
[    0.000435] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.000456] pid_max: default: 32768 minimum: 301
[    0.000551] LSM: Security Framework initializing
[    0.000663] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.000684] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.001413] Disabling memory control group subsystem
[    0.001480] CPU: Testing write buffer coherency: ok
[    0.001798] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.002249] Setting up static identity map for 0x100000 - 0x10003c
[    0.002347] rcu: Hierarchical SRCU implementation.
[    0.002680] smp: Bringing up secondary CPUs ...
[    0.003259] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.003877] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.004426] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.004492] smp: Brought up 1 node, 4 CPUs
[    0.004534] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.004547] CPU: All CPU(s) started in HYP mode.
[    0.004558] CPU: Virtualization extensions available.
[    0.005077] devtmpfs: initialized
[    0.012325] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.012474] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.012501] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.013984] pinctrl core: initialized pinctrl subsystem
[    0.014573] NET: Registered protocol family 16
[    0.016642] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.018748] audit: initializing netlink subsys (disabled)
[    0.018897] audit: type=2000 audit(0.010:1): state=initialized audit_enabled=0 res=1
[    0.019508] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.019525] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.019651] Serial: AMBA PL011 UART driver
[    0.020594] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.040054] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-01-08 14:33, variant start
[    0.050043] raspberrypi-firmware soc:firmware: Firmware hash is 194a85abd768c7334bbadc3f1911c10a7d18ed14
[    0.077900] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
[    0.078896] SCSI subsystem initialized
[    0.079017] usbcore: registered new interface driver usbfs
[    0.079053] usbcore: registered new interface driver hub
[    0.079123] usbcore: registered new device driver usb
[    0.079999] clocksource: Switched to clocksource arch_sys_counter
[    0.620404] VFS: Disk quotas dquot_6.6.0
[    0.620469] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.620586] FS-Cache: Loaded
[    0.620749] CacheFiles: Loaded
[    0.625691] thermal_sys: Registered thermal governor 'step_wise'
[    0.625875] NET: Registered protocol family 2
[    0.626309] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[    0.626343] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    0.626405] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.626495] TCP: Hash tables configured (established 8192 bind 8192)
[    0.626589] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[    0.626622] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[    0.626768] NET: Registered protocol family 1
[    0.627173] RPC: Registered named UNIX socket transport module.
[    0.627186] RPC: Registered udp transport module.
[    0.627198] RPC: Registered tcp transport module.
[    0.627209] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.628003] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.629565] Initialise system trusted keyrings
[    0.629705] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.634793] FS-Cache: Netfs 'nfs' registered for caching
[    0.635206] NFS: Registering the id_resolver key type
[    0.635243] Key type id_resolver registered
[    0.635254] Key type id_legacy registered
[    0.635271] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.635859] Key type asymmetric registered
[    0.635872] Asymmetric key parser 'x509' registered
[    0.635905] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    0.635922] io scheduler mq-deadline registered
[    0.635934] io scheduler kyber registered
[    0.637562] bcm2708_fb soc:fb: FB found 1 display(s)
[    0.659429] Console: switching to colour frame buffer device 170x48
[    0.666627] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 1360x768
[    0.668425] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[    0.669702] bcm2835-rng 3f104000.rng: hwrng registered
[    0.670015] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.670429] vc-sm: Videocore shared memory driver
[    0.670694] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    0.676395] brd: module loaded
[    0.682495] loop: module loaded
[    0.683258] Loading iSCSI transport class v2.0-870.
[    0.683777] libphy: Fixed MDIO Bus: probed
[    0.683885] usbcore: registered new interface driver lan78xx
[    0.683984] usbcore: registered new interface driver smsc95xx
[    0.684067] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    1.414449] Core Release: 2.80a
[    1.416855] Setting default values for core params
[    1.419264] Finished setting default values for core params
[    1.621852] Using Buffer DMA mode
[    1.624188] Periodic Transfer Interrupt Enhancement - disabled
[    1.626536] Multiprocessor Interrupt Enhancement - disabled
[    1.628875] OTG VER PARAM: 0, OTG VER FLAG: 0
[    1.631206] Dedicated Tx FIFOs mode
[    1.633790] WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = b7514000 dma = 0xf7514000 len=9024
[    1.636202] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    1.648117] dwc_otg: Microframe scheduler enabled
[    1.648150] WARN::hcd_init_fiq:457: FIQ on core 1
[    1.650492] WARN::hcd_init_fiq:458: FIQ ASM at 8070bf24 length 36
[    1.652841] WARN::hcd_init_fiq:497: MPHI regs_base at bb810000
[    1.655172] dwc_otg 3f980000.usb: DWC OTG Controller
[    1.657508] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    1.659877] dwc_otg 3f980000.usb: irq 56, io mem 0x00000000
[    1.662273] Init: Port Power? op_state=1
[    1.664600] Init: Power Port (0)
[    1.667034] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    1.669415] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.671790] usb usb1: Product: DWC OTG Controller
[    1.674112] usb usb1: Manufacturer: Linux 5.4.83-v7+ dwc_otg_hcd
[    1.676443] usb usb1: SerialNumber: 3f980000.usb
[    1.679125] hub 1-0:1.0: USB hub found
[    1.681490] hub 1-0:1.0: 1 port detected
[    1.684109] dwc_otg: FIQ enabled
[    1.684114] dwc_otg: NAK holdoff enabled
[    1.684118] dwc_otg: FIQ split-transaction FSM enabled
[    1.684125] Module dwc_common_port init
[    1.684298] usbcore: registered new interface driver usb-storage
[    1.686702] mousedev: PS/2 mouse device common for all mice
[    1.689555] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    1.692780] sdhci: Secure Digital Host Controller Interface driver
[    1.695050] sdhci: Copyright(c) Pierre Ossman
[    1.697568] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
[    1.700100] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[    1.702430] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.705929] ledtrig-cpu: registered to indicate activity on CPUs
[    1.708359] hidraw: raw HID events driver (C) Jiri Kosina
[    1.710760] usbcore: registered new interface driver usbhid
[    1.713041] usbhid: USB HID core driver
[    1.715822] vchiq: vchiq_init_state: slot_zero = (ptrval)
[    1.719260] [vc_sm_connected_init]: start
[    1.726669] [vc_sm_connected_init]: end - returning 0
[    1.729889] Initializing XFRM netlink socket
[    1.732175] NET: Registered protocol family 17
[    1.734511] Key type dns_resolver registered
[    1.737011] Registering SWP/SWPB emulation handler
[    1.739398] registered taskstats version 1
[    1.741632] Loading compiled-in X.509 certificates
[    1.744111] Key type ._fscrypt registered
[    1.746291] Key type .fscrypt registered
[    1.754345] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 53, base_baud = 50000000) is a 16550
[    1.756957] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[    1.759907] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    1.762180] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
[    1.790358] sdhost: log_buf @ (ptrval) (f7513000)
[    1.827357] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.831146] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.834877] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.839798] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.841972] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    1.845321] of_cfs_init
[    1.847572] of_cfs_init: OK
[    1.850224] Waiting for root device PARTUUID=cc91ff97-02...
[    1.900100] Indeed it is in host mode hprt0 = 00021501
[    1.964473] random: fast init done
[    1.984727] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.990674] mmc1: new high speed SDIO card at address 0001
[    1.993113] mmc0: new high speed SDHC card at address aaaa
[    1.995712] mmcblk0: mmc0:aaaa SA32G 29.7 GiB
[    2.000455]  mmcblk0: p1 p2
[    2.031681] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.033942] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    2.036682] devtmpfs: mounted
[    2.041935] Freeing unused kernel memory: 1024K
[    2.060193] Run /sbin/init as init process
[    2.110040] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    2.112325] Indeed it is in host mode hprt0 = 00001101
[    2.350228] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[    2.352470] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.355076] hub 1-1:1.0: USB hub found
[    2.357300] hub 1-1:1.0: 4 ports detected
[    2.609704] systemd[1]: System time before build time, advancing clock.
[    2.670029] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    2.726750] NET: Registered protocol family 10
[    2.729693] Segment Routing with IPv6
[    2.757761] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    2.763292] systemd[1]: Detected architecture arm.
[    2.800187] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[    2.802713] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.805564] hub 1-1.1:1.0: USB hub found
[    2.808111] hub 1-1.1:1.0: 3 ports detected
[    2.840729] systemd[1]: Set hostname to <raspberrypi>.
[    3.163420] dwc_otg_handle_wakeup_detected_intr lxstate = 2
[    3.285490] systemd[1]: /lib/systemd/system/pivccu.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/pivccu3.pid → /run/pivccu3.pid; please update the unit file accordingly.
[    3.364258] random: systemd: uninitialized urandom read (16 bytes read)
[    3.374797] random: systemd: uninitialized urandom read (16 bytes read)
[    3.378149] systemd[1]: Listening on udev Kernel Socket.
[    3.384480] random: systemd: uninitialized urandom read (16 bytes read)
[    3.387699] systemd[1]: Listening on udev Control Socket.
[    3.394607] systemd[1]: Listening on Journal Audit Socket.
[    3.401010] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    3.407655] systemd[1]: Listening on Journal Socket.
[    3.416265] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    3.590077] usb 1-1.1.1: new high-speed USB device number 4 using dwc_otg
[    3.727089] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
[    3.727100] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.967664] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    3.990313] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
[    3.991192] libphy: lan78xx-mdiobus: probed
[    4.014904] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
[    4.055890] systemd-journald[111]: Received request to flush runtime journal from PID 1
[    4.439261] generic_raw_uart: loading out-of-tree module taints kernel.
[    4.447638] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[    4.448893] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[    4.448903] [vc_sm_connected_init]: start
[    4.450951] [vc_sm_connected_init]: installed successfully
[    4.478514] mc: Linux media interface: v0.10
[    4.531737] videodev: Linux video capture interface: v2.00
[    4.578730] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    4.593275] bcm2835_audio bcm2835_audio: card created with 4 channels
[    4.594961] bcm2835_audio bcm2835_audio: card created with 4 channels
[    4.606915] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    4.608247] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    4.608769] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    4.624917] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[    4.625944] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[    4.633585] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[    4.639825] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[    4.640285] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[    4.642095] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[    4.642102] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[    4.642121] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[    4.642339] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[    4.642354] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[    4.642365] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[    4.642373] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[    4.642381] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[    4.642485] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[    4.650274] pl011_raw_uart 3f201000.serial: Initialized pl011 device; mapbase=0x3f201000; irq=81; clockrate=47999625
[    4.673776] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[    4.673804] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[    4.677826] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[    4.677903] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[    4.828728] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    4.922721] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    4.986165] brcmfmac: F1 signature read @0x18000000=0x15264345
[    5.000216] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    5.001349] usbcore: registered new interface driver brcmfmac
[    5.040995] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt failed with error -2
[    5.244756] random: crng init done
[    5.244767] random: 7 urandom warning(s) missed due to ratelimiting
[    5.251931] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    5.268520] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 23 2020 02:19:54 version 7.45.206 (r725000 CY) FWID 01-88ee44ea
[    5.281730] rtc-rx8130 1-0032: Unable to read registers #28..#30
[    5.281744] i2c i2c-1: probing for rx8130 failed
[    5.281768] rtc-rx8130: probe of 1-0032 failed with error -121
[    6.763406] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    6.770608] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[    6.776656] br0: port 1(eth0) entered blocking state
[    6.776666] br0: port 1(eth0) entered disabled state
[    6.777048] device eth0 entered promiscuous mode
[    7.812303] br0: port 1(eth0) entered blocking state
[    7.812310] br0: port 1(eth0) entered forwarding state
[    7.812424] IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready
[   12.734362] hb-rf-eth hb-rf-eth: Trying to connect to 10.1.1.31
[   12.850106] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[   12.917256] raw-uart raw-uart: Reset radio module
[   13.334063] Bluetooth: Core ver 2.22
[   13.334126] NET: Registered protocol family 31
[   13.334133] Bluetooth: HCI device and connection manager initialized
[   13.334150] Bluetooth: HCI socket layer initialized
[   13.334159] Bluetooth: L2CAP socket layer initialized
[   13.334177] Bluetooth: SCO socket layer initialized
[   13.346615] Bluetooth: HCI UART driver ver 2.3
[   13.346628] Bluetooth: HCI UART protocol H4 registered
[   13.346668] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   13.346818] Bluetooth: HCI UART protocol Broadcom registered
[   13.600136] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   13.600148] Bluetooth: BNEP filters: protocol multicast
[   13.600167] Bluetooth: BNEP socket layer initialized
[   22.190024] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[   22.190062] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[   22.190748] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[   31.164663] raw-uart raw-uart1: Reset radio module
[   31.550028] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[   31.550065] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[   31.550639] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[   49.768661] br0: port 2(vethpivccu) entered blocking state
[   49.768670] br0: port 2(vethpivccu) entered disabled state
[   49.768856] device vethpivccu entered promiscuous mode
[   49.843744] cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation
[   49.932384] eth0: renamed from veth03TYQ5
[   49.972006] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   49.972134] IPv6: ADDRCONF(NETDEV_CHANGE): vethpivccu: link becomes ready
[   49.972217] br0: port 2(vethpivccu) entered blocking state
[   49.972223] br0: port 2(vethpivccu) entered forwarding state
[   50.300894] br0: port 2(vethpivccu) entered disabled state
[   50.302931] device vethpivccu left promiscuous mode
[   50.302943] br0: port 2(vethpivccu) entered disabled state
[   58.330039] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[   58.330080] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[   58.330797] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[   67.780023] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[   67.780061] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[   67.780640] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[   73.160509] hb-rf-eth hb-rf-eth: Trying to connect to 10.1.1.31
[   73.280297] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[   73.318191] raw-uart raw-uart: Reset radio module
[   82.710778] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[   82.710816] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[   82.711459] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[   91.526769] raw-uart raw-uart1: Reset radio module
[   92.061036] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[   92.061074] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[   92.061675] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  119.771293] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  119.771332] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  119.771947] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  129.221318] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  129.221356] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  129.221949] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  138.670899] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  138.670938] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  138.671680] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  148.020244] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  148.020282] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  148.020888] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  157.369741] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  157.369781] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  157.370428] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  166.719363] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  166.719407] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  166.720040] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  172.449358] hb-rf-eth hb-rf-eth: Trying to connect to 10.1.1.31
[  172.569159] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  172.607125] raw-uart raw-uart: Reset radio module
[  181.898849] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  181.898886] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  181.899476] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  190.814342] raw-uart raw-uart1: Reset radio module
[  191.348620] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  191.348657] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  191.349211] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  210.141548] br0: port 2(vethpivccu) entered blocking state
[  210.141560] br0: port 2(vethpivccu) entered disabled state
[  210.141828] device vethpivccu entered promiscuous mode
[  210.300771] eth0: renamed from veth2QSVXF
[  210.382201] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  210.382363] IPv6: ADDRCONF(NETDEV_CHANGE): vethpivccu: link becomes ready
[  210.382443] br0: port 2(vethpivccu) entered blocking state
[  210.382449] br0: port 2(vethpivccu) entered forwarding state
[  210.549093] br0: port 2(vethpivccu) entered disabled state
[  210.550386] device vethpivccu left promiscuous mode
[  210.550393] br0: port 2(vethpivccu) entered disabled state
[  218.018128] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  218.018166] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  218.018798] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  227.467990] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  227.468025] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  227.468603] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  236.917866] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  236.917904] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  236.918493] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  246.267746] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  246.267783] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  246.268385] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  255.727643] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  255.727683] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  255.728273] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  265.087651] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  265.087688] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  265.088345] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  274.437840] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  274.437881] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  274.438455] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  283.888007] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  283.888046] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  283.888711] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  293.338136] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  293.338173] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  293.338768] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  302.788254] hb-rf-eth hb-rf-eth: Did not receive any packet in the last 5 seconds, terminating connection.
[  302.788295] hb-rf-eth hb-rf-eth: Trying to reconnect to 10.1.1.31
[  302.788938] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  452.028552] hb-rf-eth hb-rf-eth: Trying to connect to 10.1.1.31
[  452.158267] hb-rf-eth hb-rf-eth: Successfully connected to 10.1.1.31
[  452.195562] raw-uart raw-uart: Reset radio module
[  470.403869] raw-uart raw-uart1: Reset radio module
[  478.678668] br0: port 2(vethpivccu) entered blocking state
[  478.678680] br0: port 2(vethpivccu) entered disabled state
[  478.678894] device vethpivccu entered promiscuous mode
[  478.791673] eth0: renamed from vethXVO3TU
[  478.842079] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  478.842240] IPv6: ADDRCONF(NETDEV_CHANGE): vethpivccu: link becomes ready
[  478.842326] br0: port 2(vethpivccu) entered blocking state
[  478.842333] br0: port 2(vethpivccu) entered forwarding state
[  492.198695] eq3loop: created slave mmd_hmip
[  492.199306] eq3loop: created slave mmd_bidcos
[  494.257113] eq3loop: eq3loop_open_slave() mmd_bidcos
[  508.260440] eq3loop: eq3loop_open_slave() mmd_hmip
[  508.260643] eq3loop: eq3loop_close_slave() mmd_hmip
[  508.263565] eq3loop: eq3loop_open_slave() mmd_hmip
[  508.263736] eq3loop: eq3loop_close_slave() mmd_hmip
[  508.273910] eq3loop: eq3loop_open_slave() mmd_hmip
----------------------------------------------------------------------------------------
Raspi3B+ Bullseye mit HB-RF-ETH und RPI-RF-MOD auf piVCCU-FW 3.75.7 / Addons: CuxD v2.11 - E-Mail v1.7.6 - Patcher v1.0.0 - Philips Hue v3.2.5 - Programme drucken v2.6 - Scriptparser v1.11 - XML-API v2.3
Geräte: 141 / Kanäle: 791 / Datenpunkte: 6080 / SysVars: 275 / Programme: 161 / Regadom IDs: 14010 / 48 CUxD-Kanäle in 3 CUxD-Geräten
Intel NUC i3-5010U @ 2,1 GHz mit 16 GB RAM & 512 GB SSD für Proxmox mit ioBroker VM und CCU-Historian/InfluxDB/Grafana VM
----------------------------------------------------------------------------------------
Projekte im Forum: HomeHub v4.1 / Fritzbox-Anruferliste für HomeHub
----------------------------------------------------------------------------------------

Benutzeravatar
deimos
Beiträge: 5396
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 957 Mal
Kontaktdaten:

Re: Neue Installation von piVCCU3 klappt nicht!

Beitrag von deimos » 17.01.2021, 12:55

Hi,

bestätigt leider meinen Verdacht:

Die Kommunikation mit der Platine läuft in Timeouts. Das kann entweder an Netzwerkproblemen liegen oder daran, dass der Pi grade am Anfang die CPUs so gnadenlos blockiert, dass der Netzwerkstack keine eingehenden Pakete verarbeitet. Ich habe da schon versucht, das mit höheren Prioritäten zu verbessern, aber scheinbar reicht selbst das nicht (außer du hast nicht die aktuellen Kernel Module drauf, dann bitte Update).

Kurzfristig fällt mir da nur ein, piVCCU erst mit Verzögerung zu starten.

Viele Grüße
Alex

Slice
Beiträge: 1201
Registriert: 03.02.2016, 14:44
System: Alternative CCU (auf Basis OCCU)
Wohnort: irgendwo aus Süd BaWü
Hat sich bedankt: 141 Mal
Danksagung erhalten: 85 Mal

Re: Neue Installation von piVCCU3 klappt nicht!

Beitrag von Slice » 17.01.2021, 13:04

Hi Alex,

wie kann ich mir den die Kernelmodule anzeigen lassen. Update hatte ich am Anfang durchgeführt!

EDIT:

Code: Alles auswählen

pi@raspberrypi:~ $ uname -r
5.4.83-v7+
Passen die Module?

Gibt es eine Möglichkeit piVCCU automatisch verzögert starten zu lassen??
Mein Netzwerk sollte ohne Probleme laufen, zumindest konnte ich bisher keine Probleme feststellen.

Danke und Grüße,
Slice
----------------------------------------------------------------------------------------
Raspi3B+ Bullseye mit HB-RF-ETH und RPI-RF-MOD auf piVCCU-FW 3.75.7 / Addons: CuxD v2.11 - E-Mail v1.7.6 - Patcher v1.0.0 - Philips Hue v3.2.5 - Programme drucken v2.6 - Scriptparser v1.11 - XML-API v2.3
Geräte: 141 / Kanäle: 791 / Datenpunkte: 6080 / SysVars: 275 / Programme: 161 / Regadom IDs: 14010 / 48 CUxD-Kanäle in 3 CUxD-Geräten
Intel NUC i3-5010U @ 2,1 GHz mit 16 GB RAM & 512 GB SSD für Proxmox mit ioBroker VM und CCU-Historian/InfluxDB/Grafana VM
----------------------------------------------------------------------------------------
Projekte im Forum: HomeHub v4.1 / Fritzbox-Anruferliste für HomeHub
----------------------------------------------------------------------------------------

Antworten

Zurück zu „piVCCU“