HM-MOD-RPI-PCB not detected after "sudo apt upgrade" with piVCCU Debian image on Raspberry Pi 4

Dear Alex,
thank you first of all for this nice piece of work.
I have been using piVCCU3 with the provided Debian image on a Raspberry Pi 4 with the HM-MOD-RPI-PCB module for several months now and it worked great! I interfaced heating control for our flat and several switchable power plugs successfully. Additionally, I installed OpenHAB 2, created a sitemap and implemented various nice trigger functions that simplify our daily live. :-)
However, now after several months I updated the Debian image using sudo apt update, sudo apt upgrade and sudo apt autoremove and first everything seemed fine.
It was only two days later, that I recognized, that piVCCU (even though the Homematic Web Interface was running properly without service messages) lost connection to the HMIP components. Power plugs are not switchable anymore through the Web Interface.
I did a complete sudo shutdown -h now, waited for the process, disconnected the USB power and restarted the Raspberry Pi 4. Still the same issue. Then I went into some diagnosing, however, now I'm kind off stuck, because, after some Googleing I cannot find the exact the problem I'm having with other users on the net.
Now I hope to find some help here, as I would really like to avoid a complete reinstallation of the setup (which up to now worked really nice).
Here are some output, which I hope will be useful:
uname -a
Linux raspberrypi 5.4.51-v7l+ #1327 SMP Thu Jul 23 11:04:39 BST 2020 armv7l GNU/Linux

sudo pivccu-info
piVCCU version: 3.51.6-40
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi UART:   Assigned to GPIO pins
HMRF Hardware:  unknown
HMIP Hardware:  unknown
Board serial:   unknown
Radio MAC:      unknown
SGTIN:          unknown
State:          RUNNING
PID:            1034
IP:             <IP_ADDRESS>
CPU use:        18.07 seconds
BlkIO use:      53.25 MiB
Link:           vethpivccu
 TX bytes:      146.12 KiB
 RX bytes:      89.29 KiB
 Total bytes:   235.41 KiB

It seems to me that the HMIP hardware (HM-MOD-RPI-PCB) cannot be detected anymore, even though it worked fine before the upgrade.
Last part of /var/log/messages:
cat /var/log/messages
Aug  2 15:26:21 raspberrypi kernel: [   10.924188] Bluetooth: HCI device and connection manager initialized
Aug  2 15:26:21 raspberrypi kernel: [   10.924201] Bluetooth: HCI socket layer initialized
Aug  2 15:26:21 raspberrypi kernel: [   10.924210] Bluetooth: L2CAP socket layer initialized
Aug  2 15:26:21 raspberrypi kernel: [   10.924223] Bluetooth: SCO socket layer initialized
Aug  2 15:26:21 raspberrypi kernel: [   10.929662] Bluetooth: HCI UART driver ver 2.3
Aug  2 15:26:21 raspberrypi kernel: [   10.929671] Bluetooth: HCI UART protocol H4 registered
Aug  2 15:26:21 raspberrypi kernel: [   10.929709] Bluetooth: HCI UART protocol Three-wire (H5) registered
Aug  2 15:26:21 raspberrypi kernel: [   10.929848] Bluetooth: HCI UART protocol Broadcom registered
Aug  2 15:26:22 raspberrypi kernel: [   11.088414] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Aug  2 15:26:22 raspberrypi kernel: [   11.088421] Bluetooth: BNEP filters: protocol multicast
Aug  2 15:26:22 raspberrypi kernel: [   11.088434] Bluetooth: BNEP socket layer initialized
Aug  2 15:26:25 raspberrypi kernel: [   14.566141] raw-uart raw-uart: Reset radio module
Aug  2 15:26:36 raspberrypi piVCCU3: HMRF hardware was not detected
Aug  2 15:26:36 raspberrypi piVCCU3: HMIP hardware was not detected
Aug  2 15:26:37 raspberrypi kernel: [   26.095997] br0: port 2(vethpivccu) entered blocking state
Aug  2 15:26:37 raspberrypi kernel: [   26.096006] br0: port 2(vethpivccu) entered disabled state
Aug  2 15:26:37 raspberrypi kernel: [   26.096178] device vethpivccu entered promiscuous mode
Aug  2 15:26:37 raspberrypi kernel: [   26.238242] eth0: renamed from veth0K5MVC
Aug  2 15:26:37 raspberrypi kernel: [   26.304025] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug  2 15:26:37 raspberrypi kernel: [   26.304146] IPv6: ADDRCONF(NETDEV_CHANGE): vethpivccu: link becomes ready
Aug  2 15:26:37 raspberrypi kernel: [   26.304214] br0: port 2(vethpivccu) entered blocking state
Aug  2 15:26:37 raspberrypi kernel: [   26.304221] br0: port 2(vethpivccu) entered forwarding state
Aug  2 15:26:37 raspberrypi kernel: [   26.461061] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Aug  2 15:31:18 raspberrypi kernel: [   37.840742] eq3loop: created slave mmd_hmip
Aug  2 15:31:18 raspberrypi kernel: [   37.841617] eq3loop: created slave mmd_bidcos
Aug  2 15:31:30 raspberrypi kernel: [   49.849021] eq3loop: eq3loop_open_slave() mmd_hmip
Aug  2 15:31:30 raspberrypi kernel: [   49.849165] eq3loop: eq3loop_close_slave() mmd_hmip
Aug  2 15:31:30 raspberrypi kernel: [   49.851259] eq3loop: eq3loop_open_slave() mmd_hmip
Aug  2 15:31:30 raspberrypi kernel: [   49.851419] eq3loop: eq3loop_close_slave() mmd_hmip
Aug  2 15:31:30 raspberrypi kernel: [   49.856778] eq3loop: eq3loop_open_slave() mmd_hmip

Also points to the fact that the HM-MOD-RPI-PCB is not detected. However, I cannot figure out what might be the cause.
sudo systemctl status pivccu.service
● pivccu.service - piVCCU
   Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2020-08-02 15:26:37 CEST; 35min ago
  Process: 611 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS)
 Main PID: 1021 (lxc-start)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/pivccu.service
           └─1021 /usr/bin/lxc-start --lxcpath /var/lib/piVCCU3 --name lxc --pidfile /var/run/pivccu3.pid --daemon

Aug 02 15:26:25 raspberrypi systemd[1]: Starting piVCCU...
Aug 02 15:26:36 raspberrypi piVCCU3[827]: HMRF hardware was not detected
Aug 02 15:26:36 raspberrypi start_container.sh[611]: <12>Aug  2 15:26:36 piVCCU3: HMRF hardware was not detected
Aug 02 15:26:36 raspberrypi piVCCU3[828]: HMIP hardware was not detected
Aug 02 15:26:36 raspberrypi start_container.sh[611]: <12>Aug  2 15:26:36 piVCCU3: HMIP hardware was not detected
Aug 02 15:26:37 raspberrypi start_container.sh[611]: kernel.sched_rt_runtime_us = -1
Aug 02 15:26:37 raspberrypi systemd[1]: Started piVCCU.

Any help on this issue is very much appreciated!
Thanks
Benjamin

Same Problem here!
***********@raspbx:~# uname -a
Linux raspbx 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux

***********@raspbx:~# pivccu-info
piVCCU version: 3.51.6-41
Kernel modules: Not available
Raw UART dev:   Not available
Rasp.Pi UART:   Assigned to GPIO pins
HMRF Hardware:  unknown
HMIP Hardware:  unknown
Board serial:   unknown
Radio MAC:      unknown
SGTIN:          unknown
State:          STOPPED

***********@raspbx:~# sudo systemctl status pivccu.service
● pivccu.service - piVCCU
   Loaded: loaded (/lib/systemd/system/pivccu.service; enabled; vendor preset: enabled)
   Active: failed (Result: resources) since Tue 2020-08-04 01:28:10 UTC; 2min 59s ago
  Process: 23381 ExecStart=/var/lib/piVCCU3/start_container.sh (code=exited, status=0/SUCCESS)
      CPU: 408ms

Aug 04 01:27:35 raspbx start_container.sh[23381]: modprobe: FATAL: Module rpi_rf_mod_led not found in directory /lib/modules/4.19.66-v7+
Aug 04 01:27:35 raspbx start_container.sh[23381]: kernel.sched_rt_runtime_us = -1
Aug 04 01:27:40 raspbx start_container.sh[23381]: lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
Aug 04 01:27:40 raspbx start_container.sh[23381]: lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
Aug 04 01:27:40 raspbx start_container.sh[23381]: lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.
Aug 04 01:27:40 raspbx systemd[1]: pivccu.service: PID file /var/run/pivccu3.pid not readable (yet?) after start: No such file or directory
Aug 04 01:28:10 raspbx systemd[1]: pivccu.service: Daemon never wrote its PID file. Failing.
Aug 04 01:28:10 raspbx systemd[1]: Failed to start piVCCU.
Aug 04 01:28:10 raspbx systemd[1]: pivccu.service: Unit entered failed state.
Aug 04 01:28:10 raspbx systemd[1]: pivccu.service: Failed with result 'resources'.

***********@raspbx:~# sudo apt install --reinstall pivccu-modules-dkms pivccu3
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  aufs-dkms aufs-tools libarchive13 liblua5.1-0 libsrtp0 linux-kbuild-4.9
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/108 MB of archives.
After this operation, 0 B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 120734 files and directories currently installed.)
Preparing to unpack .../pivccu-modules-dkms_1.0.39_all.deb ...
Removed /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service.
Removed /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service.
Removed /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service.

------------------------------
Deleting module version: 1.0.39
completely from the DKMS tree.
------------------------------
Done.
Unpacking pivccu-modules-dkms (1.0.39) over (1.0.39) ...
Preparing to unpack .../pivccu3_3.51.6-41_armhf.deb ...
Removed /etc/systemd/system/multi-user.target.wants/pivccu.service.
Unpacking pivccu3 (3.51.6-41) over (3.51.6-41) ...
Setting up pivccu-modules-dkms (1.0.39) ...

Creating symlink /var/lib/dkms/pivccu/1.0.39/source ->
                 /usr/src/pivccu-1.0.39

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make -j4 KERNELRELEASE=4.19.66-v7+ ARCH=arm all....(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.19.66-v7+ (armv7l)
Consult /var/lib/dkms/pivccu/1.0.39/build/make.log for more information.
Created symlink /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Created symlink /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Created symlink /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Setting up pivccu3 (3.51.6-41) ...
Created symlink /etc/systemd/system/multi-user.target.wants/pivccu.service → /lib/systemd/system/pivccu.service.
Job for pivccu.service failed because of unavailable resources or another system error.
See "systemctl status pivccu.service" and "journalctl -xe" for details.

***********@raspbx:~# sudo dpkg-reconfigure pivccu-modules-dkms
Removed /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service.
Removed /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service.
Removed /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service.

------------------------------
Deleting module version: 1.0.39
completely from the DKMS tree.
------------------------------
Done.

Creating symlink /var/lib/dkms/pivccu/1.0.39/source ->
                 /usr/src/pivccu-1.0.39

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j4 KERNELRELEASE=4.19.66-v7+ ARCH=arm all....(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.19.66-v7+ (armv7l)
Consult /var/lib/dkms/pivccu/1.0.39/build/make.log for more information.
Created symlink /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Created symlink /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Created symlink /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.

***********@raspbx:/var/lib/dkms/pivccu# ls
1.0.39

***********@raspbx:~# cat /var/log/messages
Aug  4 01:23:30 raspbx kernel: [    0.000000] Booting Linux on physical CPU 0x0
Aug  4 01:23:30 raspbx kernel: [    0.000000] Linux version 4.19.66-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1253 SMP Thu Aug 15 11:49:46 BST 2019
Aug  4 01:23:30 raspbx kernel: [    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
Aug  4 01:23:30 raspbx kernel: [    0.000000] CPU: div instructions available: patching division code
Aug  4 01:23:30 raspbx kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Aug  4 01:23:30 raspbx kernel: [    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Aug  4 01:23:30 raspbx kernel: [    0.000000] Memory policy: Data cache writealloc
Aug  4 01:23:30 raspbx kernel: [    0.000000] cma: Reserved 8 MiB at 0x3ac00000
Aug  4 01:23:30 raspbx kernel: [    0.000000] random: get_random_bytes called from start_kernel+0xac/0x4b4 with crng_init=0
Aug  4 01:23:30 raspbx kernel: [    0.000000] percpu: Embedded 17 pages/cpu s39488 r8192 d21952 u69632
Aug  4 01:23:30 raspbx kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
Aug  4 01:23:30 raspbx kernel: [    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
Aug  4 01:23:30 raspbx kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.000000] Memory: 939088K/970752K available (8192K kernel code, 629K rwdata, 2176K rodata, 1024K init, 821K bss, 23472K reserved, 8192K cma-reserved)
Aug  4 01:23:30 raspbx kernel: [    0.000000] Virtual kernel memory layout:
Aug  4 01:23:30 raspbx kernel: [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Aug  4 01:23:30 raspbx kernel: [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
Aug  4 01:23:30 raspbx kernel: [    0.000000]     vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
Aug  4 01:23:30 raspbx kernel: [    0.000000]     lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
Aug  4 01:23:30 raspbx kernel: [    0.000000]     modules : 0x7f000000 - 0x80000000   (  16 MB)
Aug  4 01:23:30 raspbx kernel: [    0.000000]       .text : 0x(ptrval) - 0x(ptrval)   (9184 kB)
Aug  4 01:23:30 raspbx kernel: [    0.000000]       .init : 0x(ptrval) - 0x(ptrval)   (1024 kB)
Aug  4 01:23:30 raspbx kernel: [    0.000000]       .data : 0x(ptrval) - 0x(ptrval)   ( 630 kB)
Aug  4 01:23:30 raspbx kernel: [    0.000000]        .bss : 0x(ptrval) - 0x(ptrval)   ( 822 kB)
Aug  4 01:23:30 raspbx kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Aug  4 01:23:30 raspbx kernel: [    0.000000] ftrace: allocating 26394 entries in 78 pages
Aug  4 01:23:30 raspbx kernel: [    0.000000] rcu: Hierarchical RCU implementation.
Aug  4 01:23:30 raspbx kernel: [    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
Aug  4 01:23:30 raspbx kernel: [    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Aug  4 01:23:30 raspbx kernel: [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns:<PHONE_NUMBER>67 ns
Aug  4 01:23:30 raspbx kernel: [    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every<PHONE_NUMBER>078ns
Aug  4 01:23:30 raspbx kernel: [    0.000023] Switching to timer-based delay loop, resolution 52ns
Aug  4 01:23:30 raspbx kernel: [    0.000293] Console: colour dummy device 80x30
Aug  4 01:23:30 raspbx kernel: [    0.000910] console [tty1] enabled
Aug  4 01:23:30 raspbx kernel: [    0.000971] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
Aug  4 01:23:30 raspbx kernel: [    0.001017] pid_max: default: 32768 minimum: 301
Aug  4 01:23:30 raspbx kernel: [    0.001372] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.001407] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.002339] CPU: Testing write buffer coherency: ok
Aug  4 01:23:30 raspbx kernel: [    0.002821] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Aug  4 01:23:30 raspbx kernel: [    0.003489] Setting up static identity map for 0x100000 - 0x10003c
Aug  4 01:23:30 raspbx kernel: [    0.003658] rcu: Hierarchical SRCU implementation.
Aug  4 01:23:30 raspbx kernel: [    0.004473] smp: Bringing up secondary CPUs ...
Aug  4 01:23:30 raspbx kernel: [    0.005334] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Aug  4 01:23:30 raspbx kernel: [    0.006265] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
Aug  4 01:23:30 raspbx kernel: [    0.007128] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Aug  4 01:23:30 raspbx kernel: [    0.007249] smp: Brought up 1 node, 4 CPUs
Aug  4 01:23:30 raspbx kernel: [    0.007330] SMP: Total of 4 processors activated (153.60 BogoMIPS).
Aug  4 01:23:30 raspbx kernel: [    0.007354] CPU: All CPU(s) started in HYP mode.
Aug  4 01:23:30 raspbx kernel: [    0.007375] CPU: Virtualization extensions available.
Aug  4 01:23:30 raspbx kernel: [    0.008366] devtmpfs: initialized
Aug  4 01:23:30 raspbx kernel: [    0.021380] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
Aug  4 01:23:30 raspbx kernel: [    0.021652] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>2750000 ns
Aug  4 01:23:30 raspbx kernel: [    0.021699] futex hash table entries: 1024 (order: 4, 65536 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.022306] pinctrl core: initialized pinctrl subsystem
Aug  4 01:23:30 raspbx kernel: [    0.023195] NET: Registered protocol family 16
Aug  4 01:23:30 raspbx kernel: [    0.026104] DMA: preallocated 1024 KiB pool for atomic coherent allocations
Aug  4 01:23:30 raspbx kernel: [    0.031764] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
Aug  4 01:23:30 raspbx kernel: [    0.031800] hw-breakpoint: maximum watchpoint size is 8 bytes.
Aug  4 01:23:30 raspbx kernel: [    0.032027] Serial: AMBA PL011 UART driver
Aug  4 01:23:30 raspbx kernel: [    0.034334] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Aug  4 01:23:30 raspbx kernel: [    0.069335] bcm2835-dma 3f007000.dma: DMA legacy API manager at (ptrval), dmachans=0x1
Aug  4 01:23:30 raspbx kernel: [    0.071081] SCSI subsystem initialized
Aug  4 01:23:30 raspbx kernel: [    0.071324] usbcore: registered new interface driver usbfs
Aug  4 01:23:30 raspbx kernel: [    0.071400] usbcore: registered new interface driver hub
Aug  4 01:23:30 raspbx kernel: [    0.071513] usbcore: registered new device driver usb
Aug  4 01:23:30 raspbx kernel: [    0.090120] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-08-15 12:06, variant start
Aug  4 01:23:30 raspbx kernel: [    0.100405] raspberrypi-firmware soc:firmware: Firmware hash is 0e6daa5106dd4164474616408e0dc24f997ffcf3
Aug  4 01:23:30 raspbx kernel: [    0.111630] clocksource: Switched to clocksource arch_sys_counter
Aug  4 01:23:30 raspbx kernel: [    0.200750] VFS: Disk quotas dquot_6.6.0
Aug  4 01:23:30 raspbx kernel: [    0.200861] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.201046] FS-Cache: Loaded
Aug  4 01:23:30 raspbx kernel: [    0.201277] CacheFiles: Loaded
Aug  4 01:23:30 raspbx kernel: [    0.211277] NET: Registered protocol family 2
Aug  4 01:23:30 raspbx kernel: [    0.212098] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.212163] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.212294] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.212499] TCP: Hash tables configured (established 8192 bind 8192)
Aug  4 01:23:30 raspbx kernel: [    0.212652] UDP hash table entries: 512 (order: 2, 16384 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.212718] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.213048] NET: Registered protocol family 1
Aug  4 01:23:30 raspbx mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.1"
Aug  4 01:23:30 raspbx mtp-probe: bus: 1, device: 4 was not an MTP device
Aug  4 01:23:30 raspbx mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.1"
Aug  4 01:23:30 raspbx mtp-probe: bus: 1, device: 4 was not an MTP device
Aug  4 01:23:30 raspbx kernel: [    0.213623] RPC: Registered named UNIX socket transport module.
Aug  4 01:23:30 raspbx kernel: [    0.213650] RPC: Registered udp transport module.
Aug  4 01:23:30 raspbx kernel: [    0.213672] RPC: Registered tcp transport module.
Aug  4 01:23:30 raspbx kernel: [    0.213694] RPC: Registered tcp NFSv4.1 backchannel transport module.
Aug  4 01:23:30 raspbx kernel: [    0.215394] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
Aug  4 01:23:30 raspbx kernel: [    0.218424] Initialise system trusted keyrings
Aug  4 01:23:30 raspbx kernel: [    0.218631] workingset: timestamp_bits=14 max_order=18 bucket_order=4
Aug  4 01:23:30 raspbx kernel: [    0.228617] FS-Cache: Netfs 'nfs' registered for caching
Aug  4 01:23:30 raspbx kernel: [    0.229209] NFS: Registering the id_resolver key type
Aug  4 01:23:30 raspbx kernel: [    0.229255] Key type id_resolver registered
Aug  4 01:23:30 raspbx kernel: [    0.229277] Key type id_legacy registered
Aug  4 01:23:30 raspbx kernel: [    0.229309] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Aug  4 01:23:30 raspbx kernel: [    0.231591] Key type asymmetric registered
Aug  4 01:23:30 raspbx kernel: [    0.231699] Asymmetric key parser 'x509' registered
Aug  4 01:23:30 raspbx kernel: [    0.231769] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
Aug  4 01:23:30 raspbx kernel: [    0.231953] io scheduler noop registered
Aug  4 01:23:30 raspbx kernel: [    0.231977] io scheduler deadline registered (default)
Aug  4 01:23:30 raspbx kernel: [    0.232182] io scheduler cfq registered
Aug  4 01:23:30 raspbx kernel: [    0.232207] io scheduler mq-deadline registered (default)
Aug  4 01:23:30 raspbx kernel: [    0.232231] io scheduler kyber registered
Aug  4 01:23:30 raspbx kernel: [    0.234436] bcm2708_fb soc:fb: FB found 1 display(s)
Aug  4 01:23:30 raspbx kernel: [    0.243936] Console: switching to colour frame buffer device 82x26
Aug  4 01:23:30 raspbx kernel: [    0.250750] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 656x416
Aug  4 01:23:30 raspbx kernel: [    0.256498] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
Aug  4 01:23:30 raspbx liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="450" x-info="http://www.rsyslog.com"] start
Aug  4 01:23:30 raspbx kernel: [    0.260361] bcm2835-rng 3f104000.rng: hwrng registered
Aug  4 01:23:30 raspbx kernel: [    0.263115] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Aug  4 01:23:30 raspbx kernel: [    0.268474] vc-sm: Videocore shared memory driver
Aug  4 01:23:30 raspbx kernel: [    0.271291] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Aug  4 01:23:30 raspbx kernel: [    0.287296] brd: module loaded
Aug  4 01:23:30 raspbx kernel: [    0.300018] loop: module loaded
Aug  4 01:23:30 raspbx kernel: [    0.303180] Loading iSCSI transport class v2.0-870.
Aug  4 01:23:30 raspbx kernel: [    0.306329] libphy: Fixed MDIO Bus: probed
Aug  4 01:23:30 raspbx kernel: [    0.308830] usbcore: registered new interface driver lan78xx
Aug  4 01:23:30 raspbx kernel: [    0.311348] usbcore: registered new interface driver smsc95xx
Aug  4 01:23:30 raspbx kernel: [    0.313835] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Aug  4 01:23:30 raspbx kernel: [    0.344161] dwc_otg 3f980000.usb: base=(ptrval)
Aug  4 01:23:30 raspbx kernel: [    0.546851] Core Release: 2.80a
Aug  4 01:23:30 raspbx kernel: [    0.549308] Setting default values for core params
Aug  4 01:23:30 raspbx kernel: [    0.551837] Finished setting default values for core params
Aug  4 01:23:30 raspbx kernel: [    0.754631] Using Buffer DMA mode
Aug  4 01:23:30 raspbx kernel: [    0.757034] Periodic Transfer Interrupt Enhancement - disabled
Aug  4 01:23:30 raspbx kernel: [    0.759446] Multiprocessor Interrupt Enhancement - disabled
Aug  4 01:23:30 raspbx kernel: [    0.761850] OTG VER PARAM: 0, OTG VER FLAG: 0
Aug  4 01:23:30 raspbx kernel: [    0.764199] Dedicated Tx FIFOs mode
Aug  4 01:23:30 raspbx kernel: [    0.766925] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = bad14000 dma = 0xfad14000 len=9024
Aug  4 01:23:30 raspbx kernel: [    0.771506] FIQ FSM acceleration enabled for :
Aug  4 01:23:30 raspbx kernel: [    0.771506] Non-periodic Split Transactions
Aug  4 01:23:30 raspbx kernel: [    0.771506] Periodic Split Transactions
Aug  4 01:23:30 raspbx kernel: [    0.771506] High-Speed Isochronous Endpoints
Aug  4 01:23:30 raspbx kernel: [    0.771506] Interrupt/Control Split Transaction hack enabled
Aug  4 01:23:30 raspbx kernel: [    0.782478] WARN::hcd_init_fiq:457: FIQ on core 1
Aug  4 01:23:30 raspbx kernel: [    0.784710] WARN::hcd_init_fiq:458: FIQ ASM at 80654f4c length 36
Aug  4 01:23:30 raspbx kernel: [    0.786924] WARN::hcd_init_fiq:497: MPHI regs_base at bb810000
Aug  4 01:23:30 raspbx kernel: [    0.789179] dwc_otg 3f980000.usb: DWC OTG Controller
Aug  4 01:23:30 raspbx kernel: [    0.791441] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Aug  4 01:23:30 raspbx kernel: [    0.793784] dwc_otg 3f980000.usb: irq 56, io mem 0x00000000
Aug  4 01:23:30 raspbx kernel: [    0.796090] Init: Port Power? op_state=1
Aug  4 01:23:30 raspbx kernel: [    0.798331] Init: Power Port (0)
Aug  4 01:23:30 raspbx kernel: [    0.800744] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
Aug  4 01:23:30 raspbx kernel: [    0.805288] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug  4 01:23:30 raspbx kernel: [    0.807708] usb usb1: Product: DWC OTG Controller
Aug  4 01:23:30 raspbx kernel: [    0.810076] usb usb1: Manufacturer: Linux 4.19.66-v7+ dwc_otg_hcd
Aug  4 01:23:30 raspbx kernel: [    0.812522] usb usb1: SerialNumber: 3f980000.usb
Aug  4 01:23:30 raspbx kernel: [    0.815476] hub 1-0:1.0: USB hub found
Aug  4 01:23:30 raspbx kernel: [    0.817751] hub 1-0:1.0: 1 port detected
Aug  4 01:23:30 raspbx kernel: [    0.820810] usbcore: registered new interface driver usb-storage
Aug  4 01:23:30 raspbx kernel: [    0.823295] mousedev: PS/2 mouse device common for all mice
Aug  4 01:23:30 raspbx kernel: [    0.826483] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Aug  4 01:23:30 raspbx kernel: [    0.829112] bcm2835-cpufreq: min=600000 max=1400000
Aug  4 01:23:30 raspbx kernel: [    0.831943] sdhci: Secure Digital Host Controller Interface driver
Aug  4 01:23:30 raspbx kernel: [    0.834360] sdhci: Copyright(c) Pierre Ossman
Aug  4 01:23:30 raspbx kernel: [    0.837139] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
Aug  4 01:23:30 raspbx kernel: [    0.840050] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
Aug  4 01:23:30 raspbx kernel: [    0.842759] sdhci-pltfm: SDHCI platform and OF driver helper
Aug  4 01:23:30 raspbx kernel: [    0.846878] ledtrig-cpu: registered to indicate activity on CPUs
Aug  4 01:23:30 raspbx kernel: [    0.849612] hidraw: raw HID events driver (C) Jiri Kosina
Aug  4 01:23:30 raspbx kernel: [    0.852417] usbcore: registered new interface driver usbhid
Aug  4 01:23:30 raspbx kernel: [    0.855057] usbhid: USB HID core driver
Aug  4 01:23:30 raspbx kernel: [    0.858373] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0
Aug  4 01:23:30 raspbx kernel: [    0.862522] [vc_sm_connected_init]: start
Aug  4 01:23:30 raspbx kernel: [    0.871280] [vc_sm_connected_init]: end - returning 0
Aug  4 01:23:30 raspbx kernel: [    0.874839] Initializing XFRM netlink socket
Aug  4 01:23:30 raspbx kernel: [    0.877267] NET: Registered protocol family 17
Aug  4 01:23:30 raspbx kernel: [    0.879773] Key type dns_resolver registered
Aug  4 01:23:30 raspbx kernel: [    0.882612] Registering SWP/SWPB emulation handler
Aug  4 01:23:30 raspbx kernel: [    0.885710] registered taskstats version 1
Aug  4 01:23:30 raspbx kernel: [    0.888117] Loading compiled-in X.509 certificates
Aug  4 01:23:30 raspbx kernel: [    0.899017] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
Aug  4 01:23:30 raspbx kernel: [    0.901461] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
Aug  4 01:23:30 raspbx kernel: [    0.930155] sdhost: log_buf @ (ptrval) (fad13000)
Aug  4 01:23:30 raspbx kernel: [    0.968834] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.972759] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.976551] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Aug  4 01:23:30 raspbx kernel: [    0.980937] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Aug  4 01:23:30 raspbx kernel: [    0.984304] of_cfs_init
Aug  4 01:23:30 raspbx kernel: [    0.986427] of_cfs_init: OK
Aug  4 01:23:30 raspbx kernel: [    0.988978] Waiting for root device /dev/mmcblk0p2...
Aug  4 01:23:30 raspbx kernel: [    1.003229] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Aug  4 01:23:30 raspbx kernel: [    1.031756] Indeed it is in host mode hprt0 = 00021501
Aug  4 01:23:30 raspbx kernel: [    1.101100] random: fast init done
Aug  4 01:23:30 raspbx kernel: [    1.130076] mmc0: host does not support reading read-only switch, assuming write-enable
Aug  4 01:23:30 raspbx kernel: [    1.137700] mmc0: new high speed SDXC card at address aaaa
Aug  4 01:23:30 raspbx kernel: [    1.140086] mmc1: new high speed SDIO card at address 0001
Aug  4 01:23:30 raspbx kernel: [    1.143433] mmcblk0: mmc0:aaaa AFGCE 59.5 GiB
Aug  4 01:23:30 raspbx kernel: [    1.149356]  mmcblk0: p1 p2
Aug  4 01:23:30 raspbx kernel: [    1.177533] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Aug  4 01:23:30 raspbx kernel: [    1.181838] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Aug  4 01:23:30 raspbx kernel: [    1.193580] devtmpfs: mounted
Aug  4 01:23:30 raspbx kernel: [    1.201082] Freeing unused kernel memory: 1024K
Aug  4 01:23:30 raspbx kernel: [    1.203731] Run /sbin/init as init process
Aug  4 01:23:30 raspbx kernel: [    1.241677] usb 1-1: new high-speed USB device number 2 using dwc_otg
Aug  4 01:23:30 raspbx kernel: [    1.244293] Indeed it is in host mode hprt0 = 00001101
Aug  4 01:23:30 raspbx kernel: [    1.481970] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Aug  4 01:23:30 raspbx kernel: [    1.487092] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug  4 01:23:30 raspbx kernel: [    1.490521] hub 1-1:1.0: USB hub found
Aug  4 01:23:30 raspbx kernel: [    1.493377] hub 1-1:1.0: 4 ports detected
Aug  4 01:23:30 raspbx kernel: [    1.811683] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Aug  4 01:23:30 raspbx kernel: [    1.837605] NET: Registered protocol family 10
Aug  4 01:23:30 raspbx kernel: [    1.841575] Segment Routing with IPv6
Aug  4 01:23:30 raspbx kernel: [    1.873056] random: systemd: uninitialized urandom read (16 bytes read)
Aug  4 01:23:30 raspbx kernel: [    1.878180] random: systemd: uninitialized urandom read (16 bytes read)
Aug  4 01:23:30 raspbx kernel: [    1.952126] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Aug  4 01:23:30 raspbx kernel: [    1.957706] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug  4 01:23:30 raspbx kernel: [    1.962408] hub 1-1.1:1.0: USB hub found
Aug  4 01:23:30 raspbx kernel: [    1.962970] random: systemd-cryptse: uninitialized urandom read (16 bytes read)
Aug  4 01:23:30 raspbx kernel: [    1.965579] hub 1-1.1:1.0: 3 ports detected
Aug  4 01:23:30 raspbx kernel: [    2.326063] dwc_otg_handle_wakeup_detected_intr lxstate = 2
Aug  4 01:23:30 raspbx kernel: [    2.821746] usb 1-1.1.1: new high-speed USB device number 4 using dwc_otg
Aug  4 01:23:30 raspbx kernel: [    2.843164] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
Aug  4 01:23:30 raspbx kernel: [    2.856364] bcm2835_audio soc:audio: card created with 8 channels
Aug  4 01:23:30 raspbx kernel: [    2.921068] i2c /dev entries driver
Aug  4 01:23:30 raspbx kernel: [    2.962325] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
Aug  4 01:23:30 raspbx kernel: [    2.962339] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug  4 01:23:30 raspbx kernel: [    3.246361] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
Aug  4 01:23:30 raspbx kernel: [    3.247356] libphy: lan78xx-mdiobus: probed
Aug  4 01:23:30 raspbx kernel: [    3.261706] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
Aug  4 01:23:30 raspbx kernel: [    3.497635] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Aug  4 01:23:30 raspbx kernel: [    4.673849] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
Aug  4 01:23:30 raspbx kernel: [    4.676474] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
Aug  4 01:23:30 raspbx kernel: [    4.676489] [vc_sm_connected_init]: start
Aug  4 01:23:30 raspbx kernel: [    4.678902] [vc_sm_connected_init]: installed successfully
Aug  4 01:23:30 raspbx kernel: [    4.697270] media: Linux media interface: v0.10
Aug  4 01:23:30 raspbx kernel: [    4.732447] videodev: Linux video capture interface: v2.00
Aug  4 01:23:30 raspbx kernel: [    4.769918] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Aug  4 01:23:30 raspbx kernel: [    4.769941] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Aug  4 01:23:30 raspbx kernel: [    4.779631] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
Aug  4 01:23:30 raspbx kernel: [    4.787298] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
Aug  4 01:23:30 raspbx kernel: [    4.804639] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
Aug  4 01:23:30 raspbx kernel: [    4.804662] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
Aug  4 01:23:30 raspbx kernel: [    4.818134] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
Aug  4 01:23:30 raspbx kernel: [    4.818150] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
Aug  4 01:23:30 raspbx kernel: [    4.825092] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
Aug  4 01:23:30 raspbx kernel: [    4.825108] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
Aug  4 01:23:30 raspbx kernel: [    4.927438] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Aug  4 01:23:30 raspbx kernel: [    4.965915] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Aug  4 01:23:30 raspbx kernel: [    5.030243] usbcore: registered new interface driver brcmfmac
Aug  4 01:23:30 raspbx kernel: [    5.113574] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
Aug  4 01:23:30 raspbx kernel: [    5.160211] br0: port 1(eth0) entered blocking state
Aug  4 01:23:30 raspbx kernel: [    5.160226] br0: port 1(eth0) entered disabled state
Aug  4 01:23:30 raspbx kernel: [    5.161223] device eth0 entered promiscuous mode
Aug  4 01:23:30 raspbx kernel: [    5.211393] IPv6: ADDRCONF(NETDEV_UP): br0: link is not ready
Aug  4 01:23:30 raspbx kernel: [    5.237865] random: crng init done
Aug  4 01:23:30 raspbx kernel: [    5.237880] random: 7 urandom warning(s) missed due to ratelimiting
Aug  4 01:23:30 raspbx kernel: [    6.443986] zram: Added device: zram0
Aug  4 01:23:30 raspbx kernel: [    6.444866] zram: Added device: zram1
Aug  4 01:23:30 raspbx kernel: [    6.457839] zram: Added device: zram2
Aug  4 01:23:30 raspbx kernel: [    6.461733] zram: Added device: zram3
Aug  4 01:23:30 raspbx kernel: [    6.521210] new mount options do not match the existing superblock, will be ignored
Aug  4 01:23:30 raspbx kernel: [    6.574420] zram0: detected capacity change from 0 to 53477376
Aug  4 01:23:30 raspbx kernel: [    6.702502] Adding 52220k swap on /dev/zram0.  Priority:100 extents:1 across:52220k SSFS
Aug  4 01:23:30 raspbx kernel: [    6.705933] fuse init (API version 7.27)
Aug  4 01:23:30 raspbx kernel: [    6.733212] zram1: detected capacity change from 0 to 53477376
Aug  4 01:23:30 raspbx kernel: [    6.757616] Adding 52220k swap on /dev/zram1.  Priority:100 extents:1 across:52220k SSFS
Aug  4 01:23:30 raspbx kernel: [    6.765166] zram2: detected capacity change from 0 to 53477376
Aug  4 01:23:30 raspbx kernel: [    6.778036] Adding 52220k swap on /dev/zram2.  Priority:100 extents:1 across:52220k SSFS
Aug  4 01:23:30 raspbx kernel: [    6.785394] zram3: detected capacity change from 0 to 53477376
Aug  4 01:23:30 raspbx kernel: [    6.797927] Adding 52220k swap on /dev/zram3.  Priority:100 extents:1 across:52220k SSFS
Aug  4 01:23:31 raspbx kernel: [    7.250282] br0: port 1(eth0) entered blocking state
Aug  4 01:23:31 raspbx kernel: [    7.250291] br0: port 1(eth0) entered forwarding state
Aug  4 01:23:31 raspbx kernel: [    7.250384] IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready
Aug  4 01:23:42 raspbx kernel: [    8.766934] rtc-ds1307 1-0068: registered as rtc0
Aug  4 01:23:42 raspbx kernel: [    8.767619] i2c i2c-1: new_device: Instantiated device ds1307 at 0x68
Aug  4 01:23:51 raspbx kernel: [   18.198490] Bridge firewalling registered
Aug  4 01:23:52 raspbx kernel: [   19.162178] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
Aug  4 01:24:03 raspbx kernel: [   29.773888] Bluetooth: Core ver 2.22
Aug  4 01:24:03 raspbx kernel: [   29.773972] NET: Registered protocol family 31
Aug  4 01:24:03 raspbx kernel: [   29.773979] Bluetooth: HCI device and connection manager initialized
Aug  4 01:24:03 raspbx kernel: [   29.773996] Bluetooth: HCI socket layer initialized
Aug  4 01:24:03 raspbx kernel: [   29.774009] Bluetooth: L2CAP socket layer initialized
Aug  4 01:24:03 raspbx kernel: [   29.774042] Bluetooth: SCO socket layer initialized
Aug  4 01:27:35 raspbx piVCCU3: HMRF hardware was not detected
Aug  4 01:27:35 raspbx piVCCU3: HMIP hardware was not detected
Aug  4 01:27:35 raspbx kernel: [  241.643237] br0: port 2(vethpivccu) entered blocking state
Aug  4 01:27:35 raspbx kernel: [  241.643246] br0: port 2(vethpivccu) entered disabled state
Aug  4 01:27:35 raspbx kernel: [  241.643481] device vethpivccu entered promiscuous mode
Aug  4 01:27:35 raspbx kernel: [  241.643794] IPv6: ADDRCONF(NETDEV_UP): vethpivccu: link is not ready
Aug  4 01:27:35 raspbx kernel: [  241.715134] eth0: renamed from vethTNEUCP
Aug  4 01:27:35 raspbx kernel: [  241.778996] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug  4 01:27:35 raspbx kernel: [  241.782721] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug  4 01:27:35 raspbx kernel: [  241.782866] IPv6: ADDRCONF(NETDEV_CHANGE): vethpivccu: link becomes ready
Aug  4 01:27:35 raspbx kernel: [  241.782945] br0: port 2(vethpivccu) entered blocking state
Aug  4 01:27:35 raspbx kernel: [  241.782951] br0: port 2(vethpivccu) entered forwarding state
Aug  4 01:27:35 raspbx kernel: [  241.843035] br0: port 2(vethpivccu) entered disabled state
Aug  4 01:27:35 raspbx kernel: [  241.849424] device vethpivccu left promiscuous mode
Aug  4 01:27:35 raspbx kernel: [  241.849435] br0: port 2(vethpivccu) entered disabled state

***********@raspbx:/var/lib/dkms/pivccu/1.0.39/build# cat make.log
DKMS make.log for pivccu-1.0.39 for kernel 4.19.66-v7+ (armv7l)
Tue  4 Aug 01:18:37 UTC 2020
make -C /lib/modules/4.19.66-v7+/build M=/var/lib/dkms/pivccu/1.0.39/build modules
make[1]: Entering directory '/usr/src/linux-headers-4.19.66-v7+'
  CC [M]  /var/lib/dkms/pivccu/1.0.39/build/eq3_char_loop.o
/bin/sh: 1: gcc-8: not found
scripts/Makefile.build:309: recipe for target '/var/lib/dkms/pivccu/1.0.39/build/eq3_char_loop.o' failed
make[2]: *** [/var/lib/dkms/pivccu/1.0.39/build/eq3_char_loop.o] Error 127
make[2]: *** Waiting for unfinished jobs....
  CC [M]  /var/lib/dkms/pivccu/1.0.39/build/plat_eq3ccu2.o
/bin/sh: 1: gcc-8: not found
scripts/Makefile.build:309: recipe for target '/var/lib/dkms/pivccu/1.0.39/build/plat_eq3ccu2.o' failed
make[2]: *** [/var/lib/dkms/pivccu/1.0.39/build/plat_eq3ccu2.o] Error 127
Makefile:1519: recipe for target '_module_/var/lib/dkms/pivccu/1.0.39/build' failed
make[1]: *** [_module_/var/lib/dkms/pivccu/1.0.39/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.19.66-v7+'
Makefile:27: recipe for target 'all' failed
make: *** [all] Error 2

I  read in the log:
Volume was not properly unmounted. Some data may be corrupt. Please run fsck

Most likely, you did not shutdown your system, but just unplugged the power.
So run fsck and you could also try to reinstall piVCCU using apt to ensure, that all binaries are valid.

Dear Alex,
thank you for your fast reply.
The kernel reports FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. on sda1 which is my USB stick on the RaspberryPi. This is not the root partition. Anyway, I ran fsck on sda1 and the root partition (to be sure) and the issue disappeared. The filesystem should be fine.
I uninstalled pivccu3 and pivccu-modules-dkms which also removed pivccu-modules-raspberrypi. I then reinstalled pivccu3, pivccu-modules-dkms and pivccu-modules-raspberrypi.
The status is still the same:
pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 3.51.6-40
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi UART:   Assigned to GPIO pins
HMRF Hardware:  unknown
HMIP Hardware:  unknown
Board serial:   unknown
Radio MAC:      unknown
SGTIN:          unknown
State:          RUNNING
PID:            1038
IP:             <IP_ADDRESS>
IP:             2a01:c23:7018:8d00:a808:79ff:fe1e:7811
CPU use:        1.27 seconds
BlkIO use:      4.64 MiB
Link:           vethpivccu
 TX bytes:      6.01 KiB
 RX bytes:      11.39 KiB
 Total bytes:   17.40 KiB

The HMIP hardware is missing.
Any further hints to get this debugged?
Thank you again.
Benjamin

I now repeated the entire uninstallation / installation procedure to get the logs and be sure everything went fine.

Uninstallation

$ sudo apt remove pivccu3
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  arch-test cloud-image-utils debootstrap distro-info dns-root-data dnsmasq-base genisoimage libaio1 libfuse2 liblxc1 libpam-cgfs lxc lxc-templates lxcfs qemu-utils
  uidmap
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  pivccu3
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 119997 files and directories currently installed.)
Removing pivccu3 (3.51.6-40) ...
Removed /etc/systemd/system/multi-user.target.wants/pivccu.service.

Looks fine to me.
$ sudo apt remove pivccu-modules-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  arch-test bc cloud-image-utils debootstrap distro-info dkms dns-root-data dnsmasq-base genisoimage libaio1 libfuse2 liblxc1 libpam-cgfs lxc lxc-templates lxcfs
  qemu-utils raspberrypi-kernel-headers uidmap
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  pivccu-modules-dkms pivccu-modules-raspberrypi
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 99349 files and directories currently installed.)
Removing pivccu-modules-raspberrypi (2.0-12) ...
Removed /etc/systemd/system/multi-user.target.wants/pivccu-rpi-modules.service.
Removing pivccu-modules-dkms (1.0.38) ...
Removed /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service.
Removed /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service.
Removed /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service.

-------- Uninstall Beginning --------
Module:  pivccu
Version: 1.0.38
Kernel:  5.4.51-v7l+ (armv7l)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

dummy_rx8130.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

dw_apb_raw_uart.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

eq3_char_loop.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

fake_hmrf.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

generic_raw_uart.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

hb_rf_usb-2.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

hb_rf_usb.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

led_trigger_timer.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

meson_raw_uart.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

pl011_raw_uart.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

plat_eq3ccu2.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

rpi_rf_mod_led.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove 'kernel/drivers/pivccu': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

rtc-rx8130.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/
rmdir: failed to remove directory 'kernel/drivers': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod...

DKMS: uninstall completed.

------------------------------
Deleting module version: 1.0.38
completely from the DKMS tree.
------------------------------
Done.

This looks a bit weird: rmdir: failed to remove directory 'kernel/drivers': Directory not empty - Might this be an issue?
$ sudo apt autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  arch-test bc cloud-image-utils debootstrap distro-info dkms dns-root-data dnsmasq-base genisoimage libaio1 libfuse2 liblxc1 libpam-cgfs lxc lxc-templates lxcfs qemu-utils raspberrypi-kernel-headers uidmap
0 upgraded, 0 newly installed, 19 to remove and 0 not upgraded.
After this operation, 183 MB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 99321 files and directories currently installed.)
Removing arch-test (0.15-2) ...
Removing bc (1.07.1-2) ...
Removing cloud-image-utils (0.29-1) ...
Removing debootstrap (1.0.114) ...
Removing distro-info (0.21) ...
Removing dkms (2.6.1-4) ...
Removing dns-root-data<PHONE_NUMBER>) ...
Removing dnsmasq-base (2.80-1+rpt1) ...
Removing genisoimage (9:1.1.11-3) ...
Removing qemu-utils (1:3.1+dfsg-8+deb10u7) ...
Removing libaio1:armhf (0.3.112-3) ...
Removing lxcfs (3.0.3-2) ...
Removing libfuse2:armhf (2.9.9-1+deb10u1) ...
Removing lxc-templates (3.0.4-0+deb10u1) ...
Removing lxc (1:3.1.0+really3.0.3-8) ...
Removing liblxc1 (1:3.1.0+really3.0.3-8) ...
Removing libpam-cgfs (1:3.1.0+really3.0.3-8) ...
Removing raspberrypi-kernel-headers (1.20200723-1) ...
Removing uidmap (1:4.5-1.1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...

This looks fine to me-

Installation

$ sudo apt install pivccu3
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  arch-test cloud-image-utils debootstrap distro-info dkms dns-root-data dnsmasq-base genisoimage libaio1 libfuse2 liblxc1 libpam-cgfs lxc lxc-templates lxcfs pivccu-modules-dkms qemu-utils raspberrypi-kernel-headers uidmap
Suggested packages:
  cloud-utils-euca ubuntu-archive-keyring squid-deb-proxy-client shunit2 python3-apport menu wodim cdrkit-doc fuse btrfs-progs lvm2 python3-lxc qemu-block-extra
The following NEW packages will be installed:
  arch-test cloud-image-utils debootstrap distro-info dkms dns-root-data dnsmasq-base genisoimage libaio1 libfuse2 liblxc1 libpam-cgfs lxc lxc-templates lxcfs pivccu-modules-dkms pivccu3 qemu-utils raspberrypi-kernel-headers uidmap
0 upgraded, 20 newly installed, 0 to remove and 0 not upgraded.
Need to get 137 MB of archives.
After this operation, 183 MB of additional disk space will be used.
Do you want to continue?
Selecting previously unselected package dkms.
(Reading database ... 46345 files and directories currently installed.)
Preparing to unpack .../archives/dkms_2.6.1-4_all.deb ...
Unpacking dkms (2.6.1-4) ...
Setting up dkms (2.6.1-4) ...
Selecting previously unselected package pivccu-modules-dkms.
(Reading database ... 46373 files and directories currently installed.)
Preparing to unpack .../pivccu-modules-dkms_1.0.38_all.deb ...
Unpacking pivccu-modules-dkms (1.0.38) ...
Selecting previously unselected package liblxc1.
Preparing to unpack .../liblxc1_1%3a3.1.0+really3.0.3-8_armhf.deb ...
Unpacking liblxc1 (1:3.1.0+really3.0.3-8) ...
Selecting previously unselected package lxc.
Preparing to unpack .../lxc_1%3a3.1.0+really3.0.3-8_armhf.deb ...
Unpacking lxc (1:3.1.0+really3.0.3-8) ...
Setting up liblxc1 (1:3.1.0+really3.0.3-8) ...
Setting up lxc (1:3.1.0+really3.0.3-8) ...
Selecting previously unselected package pivccu3.
(Reading database ... 46596 files and directories currently installed.)
Preparing to unpack .../00-pivccu3_3.51.6-40_armhf.deb ...
Unpacking pivccu3 (3.51.6-40) ...
Selecting previously unselected package arch-test.
Preparing to unpack .../01-arch-test_0.15-2_all.deb ...
Unpacking arch-test (0.15-2) ...
Selecting previously unselected package debootstrap.
Preparing to unpack .../02-debootstrap_1.0.114_all.deb ...
Unpacking debootstrap (1.0.114) ...
Selecting previously unselected package distro-info.
Preparing to unpack .../03-distro-info_0.21_armhf.deb ...
Unpacking distro-info (0.21) ...
Selecting previously unselected package dns-root-data.
Preparing to unpack .../04-dns-root-data_2019031302_all.deb ...
Unpacking dns-root-data<PHONE_NUMBER>) ...
Selecting previously unselected package dnsmasq-base.
Preparing to unpack .../05-dnsmasq-base_2.80-1+rpt1_armhf.deb ...
Unpacking dnsmasq-base (2.80-1+rpt1) ...
Selecting previously unselected package genisoimage.
Preparing to unpack .../06-genisoimage_9%3a1.1.11-3_armhf.deb ...
Unpacking genisoimage (9:1.1.11-3) ...
Selecting previously unselected package libaio1:armhf.
Preparing to unpack .../07-libaio1_0.3.112-3_armhf.deb ...
Unpacking libaio1:armhf (0.3.112-3) ...
Selecting previously unselected package libfuse2:armhf.
Preparing to unpack .../08-libfuse2_2.9.9-1+deb10u1_armhf.deb ...
Unpacking libfuse2:armhf (2.9.9-1+deb10u1) ...
Selecting previously unselected package libpam-cgfs.
Preparing to unpack .../09-libpam-cgfs_1%3a3.1.0+really3.0.3-8_armhf.deb ...
Unpacking libpam-cgfs (1:3.1.0+really3.0.3-8) ...
Selecting previously unselected package lxc-templates.
Preparing to unpack .../10-lxc-templates_3.0.4-0+deb10u1_armhf.deb ...
Unpacking lxc-templates (3.0.4-0+deb10u1) ...
Selecting previously unselected package lxcfs.
Preparing to unpack .../11-lxcfs_3.0.3-2_armhf.deb ...
Unpacking lxcfs (3.0.3-2) ...
Selecting previously unselected package qemu-utils.
Preparing to unpack .../12-qemu-utils_1%3a3.1+dfsg-8+deb10u7_armhf.deb ...
Unpacking qemu-utils (1:3.1+dfsg-8+deb10u7) ...
Selecting previously unselected package raspberrypi-kernel-headers.
Preparing to unpack .../13-raspberrypi-kernel-headers_1.20200723-1_armhf.deb ...
Unpacking raspberrypi-kernel-headers (1.20200723-1) ...
Selecting previously unselected package uidmap.
Preparing to unpack .../14-uidmap_1%3a4.5-1.1_armhf.deb ...
Unpacking uidmap (1:4.5-1.1) ...
Selecting previously unselected package cloud-image-utils.
Preparing to unpack .../15-cloud-image-utils_0.29-1_all.deb ...
Unpacking cloud-image-utils (0.29-1) ...
Setting up genisoimage (9:1.1.11-3) ...
Setting up distro-info (0.21) ...
Setting up debootstrap (1.0.114) ...
Setting up libpam-cgfs (1:3.1.0+really3.0.3-8) ...
Setting up uidmap (1:4.5-1.1) ...
Setting up lxc-templates (3.0.4-0+deb10u1) ...
Setting up dnsmasq-base (2.80-1+rpt1) ...
Setting up libfuse2:armhf (2.9.9-1+deb10u1) ...
Setting up dns-root-data<PHONE_NUMBER>) ...
Setting up raspberrypi-kernel-headers (1.20200723-1) ...
run-parts: executing /etc/kernel/header_postinst.d/dkms 5.4.51+
run-parts: executing /etc/kernel/header_postinst.d/dkms 5.4.51-v7+
run-parts: executing /etc/kernel/header_postinst.d/dkms 5.4.51-v7l+
run-parts: executing /etc/kernel/header_postinst.d/dkms 5.4.51-v8+
Setting up arch-test (0.15-2) ...
Setting up libaio1:armhf (0.3.112-3) ...
Setting up pivccu-modules-dkms (1.0.38) ...

Creating symlink /var/lib/dkms/pivccu/1.0.38/source ->
                 /usr/src/pivccu-1.0.38

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.4.51-v7l+ ARCH=arm all.....
cleaning build area...

DKMS: build completed.

dummy_rx8130.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

dw_apb_raw_uart.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

eq3_char_loop.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

fake_hmrf.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

generic_raw_uart.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

hb_rf_usb-2.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

hb_rf_usb.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

led_trigger_timer.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

meson_raw_uart.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

pl011_raw_uart.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

plat_eq3ccu2.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

rpi_rf_mod_led.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

rtc-rx8130.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.51-v7l+/kernel/drivers/pivccu/

depmod...

DKMS: install completed.
Created symlink /etc/systemd/system/multi-user.target.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Created symlink /etc/systemd/system/debmatic.service.wants/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Created symlink /etc/systemd/system/pivccu.service.requires/pivccu-dkms.service → /lib/systemd/system/pivccu-dkms.service.
Setting up pivccu3 (3.51.6-40) ...
Created symlink /etc/systemd/system/multi-user.target.wants/pivccu.service → /lib/systemd/system/pivccu.service.
Setting up lxcfs (3.0.3-2) ...
Setting up qemu-utils (1:3.1+dfsg-8+deb10u7) ...
Setting up cloud-image-utils (0.29-1) ...
Processing triggers for dbus (1.12.20-0+deb10u1) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
Processing triggers for systemd (241-7~deb10u4+rpi1) ...
Processing triggers for man-db (2.8.5-2) ...

This seems to go through fine as well.
$ sudo apt install pivccu-modules-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
pivccu-modules-dkms is already the newest version (1.0.38).
pivccu-modules-dkms set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Looks good.
$ sudo apt install pivccu-modules-raspberrypi
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  bc
The following NEW packages will be installed:
  bc pivccu-modules-raspberrypi
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 101 kB/104 kB of archives.
After this operation, 220 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://mirror.netcologne.de/raspbian/raspbian buster/main armhf bc armhf 1.07.1-2 [101 kB]
Fetched 101 kB in 0s (292 kB/s)
Preconfiguring packages ...
Selecting previously unselected package bc.
(Reading database ... 119975 files and directories currently installed.)
Preparing to unpack .../archives/bc_1.07.1-2_armhf.deb ...
Unpacking bc (1.07.1-2) ...
Selecting previously unselected package pivccu-modules-raspberrypi.
Preparing to unpack .../pivccu-modules-raspberrypi_2.0-12_armhf.deb ...
dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
Adding 'diversion of /boot/overlays/pivccu-raspberrypi.dtbo to /usr/share/rpikernelhack/overlays/pivccu-raspberrypi.dtbo by rpikernelhack'
Unpacking pivccu-modules-raspberrypi (2.0-12) ...
Setting up bc (1.07.1-2) ...
Setting up pivccu-modules-raspberrypi (2.0-12) ...
Removing 'diversion of /boot/overlays/pivccu-raspberrypi.dtbo to /usr/share/rpikernelhack/overlays/pivccu-raspberrypi.dtbo by rpikernelhack'
Created symlink /etc/systemd/system/multi-user.target.wants/pivccu-rpi-modules.service → /lib/systemd/system/pivccu-rpi-modules.service.
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...

Went well I think.
Any hints would be great ...!
Thanks
Benjamin

Any ideas / news on this issue?
One more thing: After reinstalling pivccu3 from the command line I found that the Homematic configuration "survived" the reinstallation. The Homematic WebUI keeps my configuration even after a new installation. I guess it's saved somewhere in my home directory?
Would it be a wise idea to do a factory reset from the Homematic WebUI and restore from my backup? Maybe that might get things going?
I guess not, since the issue seems to be deeper. But is it worth a try?
Kind of desperate on how to proceed.
Any hints appreciated.
Thanks
Benjamin

Still interested in solving this issue. Any help with debugging? Can provide command outputs and all diagnostic information that's need.
Would be great to get this up and running again. Currently all the Homematic IP components in our flat are doing their job "on their own". However, I would like to get back in control and bring the piVCCU back up.
Greetings
Benjamin

I have a similar problem after each reboot. Did you tried to reconfigure pivccu3?
`sudo dpkg-reconfigure pivccu3``

I have a similar problem after each reboot. Did you tried to reconfigure pivccu3?
sudo dpkg-reconfigure pivccu3

Thank you very much. I will definitely try that and get back here with the results.
I did not have time to work on the issue, however, the problem persists. I have to get it solved once the heating period starts. 😄￼￼￼￼

Now, here is something weird.
I finally had some free minutes and performed another sudo apt update, sudo apt upgrade and sudo reboot. I then went to check the HmIP web interface: the wall units (Wandthermometer) seem to report the correct temperature and humidity to the Raspberry Pi!
Furthermore, I can set temperatures, however, with a huge delay. Takes several seconds to adjust. However, window contacts don't seem to work anymore. They always report a closed window position to the Raspberry Pi even though the wall units display the correct window state.
After all, this means that the wireless communication between the HmIP devices and the Raspberry Pi is not entirely dead! It was working properly before the update.
However, it still does not work properly. Communication is slow and some transmission seems to be interrupted.
The output of pivccu-info is still identical:
pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 3.51.6-41
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi UART:   Assigned to GPIO pins
HMRF Hardware:  unknown
HMIP Hardware:  unknown
Board serial:   unknown
Radio MAC:      unknown
SGTIN:          unknown
State:          RUNNING
PID:            2949
IP:             <IP_ADDRESS>
CPU use:        18.35 seconds
BlkIO use:      3.96 MiB
Link:           vethpivccu
 TX bytes:      15.38 KiB
 RX bytes:      539.38 KiB
 Total bytes:   554.76 KiB
pi@raspberrypi:~ $

Anyone was some hints to what might have happened here?

Dear everyone,
finally the issue is solved by another update (3.53.30-47 to 3.51.6-41).
Just before the real heating period starts. Thanks. :-)
Find the output of pivccu-info below:
pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 3.53.30-47
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi UART:   Assigned to GPIO pins
HMRF Hardware:  HM-MOD-RPI-PCB
 Board serial:  QEQ0407065
 Radio MAC:     0x000000
HMIP Hardware:  HM-MOD-RPI-PCB
 SGTIN:         3014F711A061A7DA498F9E19
 Radio MAC:     0xBF2C1E
State:          RUNNING
PID:            4996
IP:             <IP_ADDRESS>
CPU use:        22.94 seconds
BlkIO use:      6.99 MiB
Link:           vethpivccu
 TX bytes:      3.98 MiB
 RX bytes:      258.12 KiB
 Total bytes:   4.23 MiB

This is how it should look like.
Thanks to everyone working in the background making this piece of software better! :-)
Best regards
Benjamin
P.S.: Alex, can I buy you a coffee or transfer something to your PayPal account?

Good to hear, that it works now, I will close the issue now.
P.S. See the sponsor button at the head of the Github page, there you will find some options.


Returning a Promise from validation

Why not return a Promise in ValidationController.validate(), instead of an array of errors? This would permit to do asynchronous validation (e.g. server-side).

This is a duplicate. There is a long conversation on this in another thread. Closing for now.

If you mean https://github.com/aurelia/validation/issues/252 I missed that since it's a bit more general. I'll follow there, thank you!


RSS reader to include ATOM feeds

First of all, let me start by saying that I love the look and feel of your minimalist design. I find it intuitive to use and has a lot of nice features.
What I would love to see added is an Atom reader. Most feeds I read (e.g. Github) are in ATOM format and since it will probably become even more prevalent it would be great if you could include it!
Kind regards,
Remko van der Pluijm

Thanks for the suggestion, we'll see about making this happen.

Please try to load an Atom feed into it right now. The RSS and ATOM specifications already overlap significantly, and I seem to remember adding a couple extra parsing options for some differences, but I don't recall if it was complete or not yet.
Parsing Rules:
https://github.com/trueos/lumina/blob/master/src-qt5/core/lumina-desktop/desktop-plugins/rssreader/RSSObjects.cpp
Sample Combination feed (RSS2 and ATOM):
http://lumina-desktop.org/feed/

The RSS reading should be working with ATOM feeds now.
https://github.com/trueos/lumina/commit/6679414ee4e385e3f88aa1401cb24f8afe73b4c3


Run prettier on output in build dirs

Summary
See #3497

Test plan

Codecov Report

Merging #5858 into master will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5858      +/-   ##
==========================================
- Coverage   63.88%   63.82%   -0.07%
==========================================
  Files         216      216
  Lines        7970     8149     +179
  Branches        4        3       -1
==========================================
+ Hits         5092     5201     +109
- Misses       2877     2947      +70
  Partials        1        1

Impacted Files
Coverage Δ

packages/jest-editor-support/src/index.js
63.15% <0%> (-36.85%)
:arrow_down:

packages/jest-cli/src/run_jest.js
50.79% <0%> (-19.21%)
:arrow_down:

packages/jest-haste-map/src/worker.js
78.68% <0%> (-18.82%)
:arrow_down:

packages/jest-resolve/src/is_builtin_module.js
83.33% <0%> (-16.67%)
:arrow_down:

packages/jest-cli/src/jest_hooks.js
66.66% <0%> (-16.67%)
:arrow_down:

packages/jest-config/src/deprecated.js
45.45% <0%> (-4.55%)
:arrow_down:

packages/jest-docblock/src/index.js
80% <0%> (-3.93%)
:arrow_down:

packages/jest-util/src/format_test_results.js
76% <0%> (-3.17%)
:arrow_down:

packages/jest-validate/src/validate_cli_options.js
65.11% <0%> (-2.39%)
:arrow_down:

.../jest-editor-support/src/parsers/babylon_parser.js
92.2% <0%> (-2.16%)
:arrow_down:

... and 62 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6a77ee3...2d717c4. Read the comment docs.

🎉


Fix XML child-value syntax in Setters

What does the pull request do?
    <Setter Property='Margin'>10, 4, 0, 4</Setter>

As far as I can tell, this syntax was never supported, but I don't see why it shouldn't.
Checklist

[x] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation

Fixed issues
Fixes #3799

It was always strange to me this wasn't supported. I just worked around it and moved on. It's nice it's added now for XAML compatibility!

@robloo honestly, I didn't know it's not supported/is broken, until I found this 4 years old issue.


[EPIC] Rework Traceloop

Traceloop is not like our other gadgets, it’s “old” (for eBPF purposes), it doesn’t integrate with Gadget Tracer Manager but rather runs as a separate binary. We would like to integrate it better and update it to current practices.
This epic includes:

[ ] #338
[ ] Migrate to CO-RE and newer practices.
[ ] Integrate with Gadget Tracer Manager
[ ] Expose traceloop as a golang package used by Inspektor Gadget, that other tools can also use.

All gadget/traceloop issues

One thing to consider when reworking traceloop: instead of it being a separate gadget, it could make sense for it to be a functionality available for any of our tracing gadgets. Something like kubectl-gadget trace exec --loop. We would need to add a tracer that traces ALL syscalls, like traceloop does, because we currently don't have that one.


python312Packages.requests-ratelimiter: 0.6.0 -> 0.7.0

Diff: https://github.com/JWCook/requests-ratelimiter/compare/refs/tags/v0.6.0...v0.7.0
Changelog: https://github.com/JWCook/requests-ratelimiter/blob/refs/tags/v0.7.0/HISTORY.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 333913 run on x86_64-linux 1

12 packages built:

conkeyscan
conkeyscan.dist
python311Packages.clize
python311Packages.clize.dist
python311Packages.requests-ratelimiter
python311Packages.requests-ratelimiter.dist
python312Packages.clize
python312Packages.clize.dist
python312Packages.requests-ratelimiter
python312Packages.requests-ratelimiter.dist
sbomnix
sbomnix.dist


SCE-1171[1/2]: baseline flag replaced with explicit "None" aggressor

Fixes issue "cannot run experiment with only "baseline" phase" (env flag is not used when provided as an empty string"
Summary of changes:

removed "include baseline flag" for all experiments and replaced with "None" dummy aggressor that is constructed by prepareAggressor helpers
memcached-sensitivity-experiment replaced manual error checking with errorutil.CheckWithContext
memcached-cat validation that user provided ranges for HP & BE workloads

Testing done:

yes

run integration tests

run integration tests

run integration tests

run integration tests

run integration tests

run integration tests


Provide initial value to reduce in order to avoid runtime errors.

Lacking the initial value throws a runtime error when the array is empty. http://stackoverflow.com/questions/23359173/javascript-reduce-an-empty-array

Thanks!


fix: panic when a port is not specified in an Openshift Route

If port is nil, which port are we exposing?

If port is nil, which port are we exposing?

	// If specified, the port to be used by the router. Most routers will use all
	// endpoints exposed by the service by default - set this value to instruct routers
	// which port to use.
	Port *RoutePort `json:"port,omitempty" protobuf:"bytes,5,opt,name=port"`


Error: Permission denied - /opt/homebrew-cask/Caskroom/(application)

Unable to install applications.
Already ran:
brew update && brew upgrade brew-cask && brew cleanup && brew cask cleanup

First, make sure brew doctor has no errors.
Please post the output of brew cask doctor and sudo ls -arlt /opt/homebrew-cask

From brew doctor:
Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected header files:
/usr/local/include/ublio.h
Warning: Homebrew's sbin was not found in your PATH but you have installed
formulae that put executables in /usr/local/sbin.
Consider setting the PATH for example like so
echo 'export PATH="/usr/local/sbin:$PATH"' >> ~/.bash_profile
From brew cask doctor:
==> OS X Release:
10.11
==> OS X Release with Patchlevel:
10.11.1
==> Hardware Architecture:
intel-64
==> Ruby Version:
2.0.0-p645
==> Ruby Path:
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
==> Homebrew Version:
0.9.5 (git revision 12f4; last commit 2015-12-06)
==> Homebrew Executable Path:
/usr/local/bin/brew
==> Homebrew Cellar Path:
/usr/local/Cellar
==> Homebrew Repository Path:
/usr/local
==> Homebrew Origin:
https://github.com/Homebrew/homebrew
==> Homebrew-cask Version:
0.59.0
==> Homebrew-cask Install Location:
/usr/local/Cellar/brew-cask/0.59.0
==> Homebrew-cask Staging Location:
/opt/homebrew-cask/Caskroom (error: not writable by current user)
==> Homebrew-cask Cached Downloads:
/Library/Caches/Homebrew
/Library/Caches/Homebrew/Casks
4 files (warning: run "brew cask cleanup")
84.61 megs (warning: run "brew cask cleanup")
==> Homebrew-cask Default Tap Path:
/usr/local/Library/Taps/caskroom/homebrew-cask
==> Homebrew-cask Alternate Cask Taps:

==> Homebrew-cask Default Tap Cask Count:
2903
==> Contents of $LOAD_PATH:
/usr/local/Cellar/brew-cask/0.59.0/rubylib
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin15
/Library/Ruby/Site/2.0.0/universal-darwin15
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin15
==> Contents of $RUBYLIB Environment Variable:

==> Contents of $RUBYOPT Environment Variable:

==> Contents of $RUBYPATH Environment Variable:

==> Contents of $RBENV_VERSION Environment Variable:

==> Contents of $CHRUBY_VERSION Environment Variable:

==> Contents of $GEM_HOME Environment Variable:

==> Contents of $GEM_PATH Environment Variable:

==> Contents of $BUNDLE_PATH Environment Variable:

==> Contents of $PATH Environment Variable:
PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/Library/ENV/scm"
==> Contents of $SHELL Environment Variable:
SHELL="/bin/bash"
==> Contents of Locale Environment Variables:
LANG="en_US.UTF-8"
==> Running As Privileged User:
No
Thank you for your helping!

Ah, I see it's a permissions error: /opt/homebrew-cask/Caskroom (error: not writable by current user)
Can you please check if sudo ls -arlt /opt/homebrew-cask gives you an output like:
[~] > sudo ls -arlt /opt/homebrew-cask
Password:
total 24
drwxr-xr-x   4 aditya  staff   136 Oct  4 14:31 .
drwxrwxr-x@  4 root    wheel   136 Nov 19 09:40 ..
-rw-r--r--@  1 aditya  staff  8196 Nov 29 12:50 .DS_Store
drwxr-xr-x  24 aditya  staff   816 Dec  6 10:25 Caskroom

If they don't look like that, let's fix that, run:
sudo mkdir -p /opt/homebrew-cask/Caskroom
sudo chown -R ${USER}:staff /opt/homebrew-cask

Try running brew update && brew upgrade -all && brew cleanup && brew cask cleanup after that. If there are no errors, you're good to go.
And finally, if that still doesn't work, the "nuclear" option is:
# NOTE: this will wipe homebrew-cask
brew uninstall brew-cask
brew untap caskroom/cask
sudo rm -rf '/opt'
brew install caskroom/cask/brew-cask

Please let us know your results.

Closing due to lack of reply

Thanks @adityadalal924 . It worked for me without needing to use the Nuclear option.


autocomplete :Stdout maxBuffer exceeded

VSCode Version:1.7.1
OS Version:Ubuntu 16.04

Language :Golang 1.7
Now，I work with vscode meeting a problem.Our team has an errcode file and it has a log of constants.When I use vscode and autocomplete this package.It doesn't work! I debug it and find such error in console
[Extension Host] rejected promise not handled within 1 second
workbench.main.js:126 stdout maxBuffer exceeded: Error: stdout maxBuffer exceeded
at Socket. (child_process.js:271:14)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at readableAddChunk (_stream_readable.js:176:18)
at Socket.Readable.push (_stream_readable.js:134:10)
at Pipe.onread (net.js:543:20)e.onUnexpectedError @ workbench.main.js:126(anonymous function) @ workbench.main.js:126e.onUnexpectedError @ workbench.main.js:29r @ workbench.main.js:29t.onUnexpectedExtHostError @ workbench.main.js:101e.handle @ workbench.main.js:100s @ workbench.main.js:49f @ workbench.main.js:49_combinedTickCallback @ internal/process/next_tick.js:67_tickCallback @ internal/process/next_tick.js:98
so,how can it work nicely?
Thank you!
Steps to Reproduce:

I work with golang . So it can produce a large go package with a lot of constants
Import it and autocomplete from this package

This issue was moved to Microsoft/vscode-go#640


Add an event for XrManager in AR for when it finds the ground/floor and starts tracking camera position

The reason for want this event is so that the developer can disable entities when going through the AR tracking phase and only show them once they can be anchored to the floor.
As far as I can tell, WebXR AR starts tracking when a pose is returned at this point:
https://github.com/playcanvas/engine/blob/main/src/xr/xr-manager.js#L689
@Maksims, would you be able to help advise on this please?

Spoke to Maksims: In 1.57, the XrManager doesn't fire the 'update' event until there is a valid pose available so this could be used as a workaround until we've thought about this more

This that was merged few days ago is related too
https://github.com/playcanvas/engine/pull/4517

That recent fix https://github.com/playcanvas/engine/pull/4517 - while avoiding an issue with Oculus Link is actually skipping other XR subsystems from updates and not doing rendering - which is last thing we want to do.
Lack of pose from frame data - is a valid XR state, based on WebXR Specs: https://www.w3.org/TR/webxr/#dom-xrframe-getviewerpose
So we need a better fix for the issue, by providing a valid path with the pose === null case.

Yep I had the same feeling after reading this ticket.
Any suggestions on how to handle this?

I've created an issue to address it: https://github.com/playcanvas/engine/issues/4675

On the note of this issue, XR Spec does not provide any events or flags about underlying XR system tracking state, but lack of pose is basically a case of "no tracking", which we can use to have our own flag for it.
We already have a concept of tracking flag in XrHand: https://github.com/playcanvas/engine/blob/main/src/xr/xr-hand.js#L297-L304
With two additional events tracking and trackinglost: https://github.com/playcanvas/engine/blob/main/src/xr/xr-hand.js#L130-L140
Similar could be added for view state, except we don't have a dedicated class/object to refer to a view/pose, maybe something like:
if (camera.tracking) {

}

// or

camera.on('trackingloss', () => {

});

Further down the update method, we have this line: https://github.com/playcanvas/engine/blob/main/src/xr/xr-manager.js#L768
this.fire('update', frame);

You could also do something like this for getting the first tracked update:
this.app.xr.once('update', () => {
    // code here
});

Yeah, that is probably what I would switch once 1.57 is current in the Editor. In 1.56, update is being fired each frame, pose or not 😅


Spot Check: Build an Atom 1.6.0-rc.4

From #27, the remaining issue was phetsims/build-an-atom#170 involving an issue with the touch areas on arrow buttons for some challenges in the game.  @phet-steele can you please verify that it is fixed in
http://www.colorado.edu/physics/phet/dev/html/build-an-atom/1.6.0-rc.4/build-an-atom_en.html
Once verified, this sim can be redeployed and we can deploy as our first sim to Legends of Learning.

Verified on Win 10 Chrome 60.0.3112.78.


False Positive: nexusrules.officeapps.live.com

Request to whitelist nexusrules.officeapps.live.com.
The following endpoints are used to connect to the Microsoft 365 admin center's shared infrastructure, including Office in a browser. For more info, see Office 365 URLs and IP address ranges. You can turn this off by removing all Microsoft Office apps and the Mail and Calendar apps. If you turn off traffic for these endpoints, users won't be able to save documents to the cloud or see their recently used documents.

Thank you for this @anxiouslelimo.
I agree. This is removed in commit 6c9377b which will be included in the next release.


Full market title needed

in liquidity section in portfolio cards are missing market titles

re-closing this so github treats it as closed.


pin scipy to < 1.14, see https://github.com/openmm/openmm/issues/4601

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Not sure what is going on with the failures, they fail to import openmm,
ModuleNotFoundError: No module named 'openmm'
In the build log, this also shows up:
Traceback (most recent call last):
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/work/build/python/setup.py", line 276, in <module>
    main()
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/work/build/python/setup.py", line 273, in main
    setup(**setupKeywords)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/__init__.py", line 108, in setup
    return distutils.core.setup(**attrs)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/core.py", line 184, in setup
    return run_commands(dist)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/core.py", line 200, in run_commands
    dist.run_commands()
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/dist.py", line 964, in run_commands
    self.run_command(cmd)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/dist.py", line 945, in run_command
    super().run_command(command)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/dist.py", line 983, in run_command
    cmd_obj.run()
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/command/install.py", line 86, in run
    return super().run()
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/command/install.py", line 694, in run
    self.run_command('build')
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
    self.distribution.run_command(command)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/dist.py", line 945, in run_command
    super().run_command(command)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/dist.py", line 983, in run_command
    cmd_obj.run()
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
    self.distribution.run_command(command)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/dist.py", line 945, in run_command
    super().run_command(command)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/dist.py", line 983, in run_command
    cmd_obj.run()
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/command/build_ext.py", line 93, in run
    _build_ext.run(self)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 359, in run
    self.build_extensions()
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 476, in build_extensions
    self._build_extensions_serial()
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 502, in _build_extensions_serial
    self.build_extension(ext)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/command/build_ext.py", line 254, in build_extension
    _build_ext.build_extension(self, ext)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/Cython/Distutils/build_ext.py", line 135, in build_extension
    super(build_ext, self).build_extension(ext)
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 581, in build_extension
    self.compiler.link_shared_object(
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/ccompiler.py", line 757, in link_shared_object
    self.link(
  File "/home/conda/feedstock_root/build_artifacts/openmm_1724181143600/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/pypy3.9/site-packages/setuptools/_distutils/unixccompiler.py", line 268, in link
    linker = (
TypeError: 'NoneType' object is not subscriptable (key slice(None, None, None))

But does not show up in the passing builds

It's not a very helpful error message.  My best guess is that one of the entries in setupKeywords at line 273 of setup.py is None, or something else invalid.  Can you patch it to print out the value?

I just got the same error from CI at https://github.com/openmm/openmm/pull/4622, but only for the Pypy build.

The inputs to setup() look fine.  I think this is the line in unixcompiler.py that's throwing the exception.
linker = (self.linker_exe if building_exe else self.linker_so)[:]

This looks like something in the compiler stack has changed recently and broken.

Sweet looks like it worked! any objects to merging @peastman ? after it gets merged in I'll make a repometadata patch to update the older builds with this pin.

Looks good!


Finalize artifacts and test for improving response time

Problem statement
We identified potential priorities and exploring areas we need to learn more about. Speeding up the responses we get from users was one of those priorities
What you need to know

Onboarding Journey Improvement Synthesis
Initial pass at plan in mural
Ideas can be found in the "Improving Response Time" section of this document

Acceptance criteria

what are the ACs here? @audreykwr


Feature/Redis-Backed Chat Memory

issue
https://github.com/FlowiseAI/Flowise/issues/369
note
The Redis-Backed Chat Memory is closer to Buffer Memory than Zep Memory according to the Langchain Docs
I use the same icon with other memory to keep consistent. I'm happy to update it or other memory icons if you think it's not necessary.
Add Redis dependency to flowise-components workspace since it's required in RedisChatMessageHistory

think we can replace the icon the Redis icon, purely personal preference 😅 so its not so dull haha

also putting a note here: you can run redis instance with docker
docker run --name my-redis -p 6379:6379 -d redis


Remove duplicate headings in data table

The datatable headers are redundant with the names given to the tabs (for example, Publications below). Some of these can be deleted, but others we might replace with explanatory text

There's been some changes to include explanatory text for these tabs, making this not relevant anymore.


AddYumRepo is not used anymore, remove it

@andreer has a PR adding usage of AddYumRepo, which I have suggested substituting with the new yum repo template stuff.

I will hold off until https://git.ouroath.com/vespa/hosted/pull/6352 has been merged.

AddYumRepo is not used in #6352 anymore, merging


Ideas for custom icons

Valid descriptor - document with checkmark
Verified to run on platform x
Organisation verified to belong to user x
Tool and workflow and service icon
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Issue Number: DOCK-1107

Validated (ie. valid json, wdl, cwl)
e.g. nice version of https://en.wikipedia.org/wiki/W3C_Markup_Validation_Service#/media/File:Valid_XHTML_1.0.svg


Clean up particle systems

Currently only a single spawner is supported. Probably should instantiate them bound to an entity or something like that. Call it Emitter.
The particle's firing conditions should ideally be handled by the emitter, not the particle. Thus, move it to events.

It's fine enough for now


API Category

This category would include libraries that help make accessing web API's easier on iOS. Two libraries that I have created that would fit perfectly into this category are:
BigBoard - An Elegant Financial Markets Library Written in Swift
Spartan - An Elegant Spotify Web API Library Written in Swift for iOS and macOS
I'm sure there are many other libraries that could fit perfectly into this category as well.

How about SDK?

@dkhamsing You are correct. Based on other repos in that section, the two mentioned above would fit in there. Thanks!