search

alexreinert / piVCCU

piVCCU is a project to install the original Homematic CCU3 firmware inside a virtualized container (lxc) on ARM based single board computers.
Apache License 2.0
302 stars 64 forks source link

Failure after update #452

Closed T1mey closed 1 year ago

T1mey commented 2 years ago

Hi @alexreinert ,

I did an update like described in readme

sudo apt update && sudo apt upgrade

After that the ccu isn't starting anymore. Any recommendations ?

Sep 07 06:07:13 rpi3 systemd[1]: Starting piVCCU...
Sep 07 06:07:13 rpi3 start_container.sh[2752]: modprobe: FATAL: Module eq3_char_loop not found in directory /lib/modules/5.10.103-v7+
Sep 07 06:07:13 rpi3 piVCCU3[2756]: Could not load required kernel module eq3_char_loop.
Sep 07 06:07:13 rpi3 start_container.sh[2752]: <11>Sep  7 06:07:13 piVCCU3: Could not load required kernel module eq3_char_loop.
Sep 07 06:07:13 rpi3 systemd[1]: pivccu.service: Can't open PID file /run/pivccu3.pid (yet?) after start: No such file or directory
Sep 07 06:07:13 rpi3 systemd[1]: pivccu.service: Failed with result 'protocol'.
Sep 07 06:07:13 rpi3 systemd[1]: Failed to start piVCCU.

Seems to be similar to https://github.com/alexreinert/piVCCU/issues/445

alexreinert commented 2 years ago

Did you reboot the system after the update?

T1mey commented 2 years ago

Did you reboot the system after the update?

Yes, I did

T1mey commented 2 years ago

Did you reboot the system after the update?

Any Idea ?

dicer commented 2 years ago

Have you tried to reinstall the modules and reboot? sudo apt-get install --reinstall pivccu-modules-raspberrypi

alexreinert commented 2 years ago

Please provide the output of 

uname -a
cat /etc/os-release
sudo pivccu-info
sudo dpkg-reconfigure pivccu-modules-dkms
T1mey commented 2 years ago

Linux rpi3 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux

PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

piVCCU version: 3.65.8-74
Kernel modules: Not available
Raw UART dev:   Not available
Rasp.Pi UART:   Assigned to GPIO pins
HMRF Hardware:  unknown
HMIP Hardware:  unknown
State:          STOPPED

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.

------------------------------
Deleting module version: 1.0.78
completely from the DKMS tree.
------------------------------
Done.
Error! There are no instances of module: pivccu
1.0.78 located in the DKMS tree.

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

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.10.103-v7+ ARCH=arm all....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.10.103-v7+ (armv7l)
Consult /var/lib/dkms/pivccu/1.0.78/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.
alexreinert commented 2 years ago

Was steht in der Datei /var/lib/dkms/pivccu/1.0.78/build/make.log?

T1mey commented 2 years ago

/var/lib/dkms/pivccu/1.0.78/build/make.log

DKMS make.log for pivccu-1.0.78 for kernel 5.10.103-v7+ (armv7l)
Mon 12 Sep 09:14:47 BST 2022
make -C /lib/modules/5.10.103-v7+/build M=/var/lib/dkms/pivccu/1.0.78/build modules
make[1]: Entering directory '/usr/src/linux-headers-5.10.103-v7+'
  CC [M]  /var/lib/dkms/pivccu/1.0.78/build/eq3_char_loop.o
  CC [M]  /var/lib/dkms/pivccu/1.0.78/build/plat_eq3ccu2.o
  CC [M]  /var/lib/dkms/pivccu/1.0.78/build/generic_raw_uart.o
  CC [M]  /var/lib/dkms/pivccu/1.0.78/build/pl011_raw_uart.o
  CC [M]  /var/lib/dkms/pivccu/1.0.78/build/dw_apb_raw_uart.o
during RTL pass: dse1
In file included from /var/lib/dkms/pivccu/1.0.78/build/pl011_raw_uart.c:36:
/var/lib/dkms/pivccu/1.0.78/build/pl011_raw_uart.c: In function ‘__pl011_raw_uart_probe’:
/var/lib/dkms/pivccu/1.0.78/build/generic_raw_uart.h:97:12: internal compiler error: Segmentation fault
     struct device *dev = &pdev->dev;                                                      \
            ^~~~~~
/var/lib/dkms/pivccu/1.0.78/build/pl011_raw_uart.c:331:1: note: in expansion of macro ‘module_raw_uart_driver’
 module_raw_uart_driver(MODULE_NAME, pl011_raw_uart, pl011_raw_uart_of_match);
 ^~~~~~~~~~~~~~~~~~~~~~
during RTL pass: dse1
/var/lib/dkms/pivccu/1.0.78/build/eq3_char_loop.c: In function ‘eq3loop_read’:
/var/lib/dkms/pivccu/1.0.78/build/eq3_char_loop.c:262:1: internal compiler error: Segmentation fault
 }
 ^
0x76ace10f ???
        ../sysdeps/unix/sysv/linux/arm/sigrestorer.S:64
0x76ab8717 __libc_start_main
        /build/glibc-Ir6W4B/glibc-2.28/csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-8/README.Bugs> for instructions.
make[2]: *** [scripts/Makefile.build:280: /var/lib/dkms/pivccu/1.0.78/build/pl011_raw_uart.o] Error 1
make[2]: *** Waiting for unfinished jobs....
0x76aca10f ???
        ../sysdeps/unix/sysv/linux/arm/sigrestorer.S:64
0x76ab4717 __libc_start_main
        /build/glibc-Ir6W4B/glibc-2.28/csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-8/README.Bugs> for instructions.
during RTL pass: dse1
/var/lib/dkms/pivccu/1.0.78/build/dw_apb_raw_uart.c: In function ‘dw_apb_raw_uart_irq_handle’:
/var/lib/dkms/pivccu/1.0.78/build/dw_apb_raw_uart.c:282:1: internal compiler error: Segmentation fault
 }
 ^
make[2]: *** [scripts/Makefile.build:280: /var/lib/dkms/pivccu/1.0.78/build/eq3_char_loop.o] Error 1
during RTL pass: fwprop2
In file included from /var/lib/dkms/pivccu/1.0.78/build/generic_raw_uart.c:1319:
/var/lib/dkms/pivccu/1.0.78/build/devkey.inc: In function ‘bigint_mod_add’:
/var/lib/dkms/pivccu/1.0.78/build/devkey.inc:332:1: internal compiler error: Segmentation fault
 }
 ^
0x76b4210f ???
        ../sysdeps/unix/sysv/linux/arm/sigrestorer.S:64
0x76b2c717 __libc_start_main
        /build/glibc-Ir6W4B/glibc-2.28/csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-8/README.Bugs> for instructions.
make[2]: *** [scripts/Makefile.build:280: /var/lib/dkms/pivccu/1.0.78/build/dw_apb_raw_uart.o] Error 1
0x76b3910f ???
        ../sysdeps/unix/sysv/linux/arm/sigrestorer.S:64
0x76b23717 __libc_start_main
        /build/glibc-Ir6W4B/glibc-2.28/csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-8/README.Bugs> for instructions.
make[2]: *** [scripts/Makefile.build:280: /var/lib/dkms/pivccu/1.0.78/build/generic_raw_uart.o] Error 1
make[1]: *** [Makefile:1825: /var/lib/dkms/pivccu/1.0.78/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.10.103-v7+'
make: *** [Makefile:30: all] Error 2
alexreinert commented 2 years ago

Das "Segmentation fault" klingt nicht gut, das bedeutet, dass der auf deinem System installierte Compiler defekt ist. Ich würde stark von einer defekten SD Karte oder einem defekten Dateisystem ausgehen.

T1mey commented 2 years ago

Das "Segmentation fault" klingt nicht gut, das bedeutet, dass der auf deinem System installierte Compiler defekt ist. Ich würde stark von einer defekten SD Karte oder einem defekten Dateisystem ausgehen.

Also ich habe das System aus einem alten Backup wiederhergestellt und da lief eine ältere Version von pivccu problemlos. Dann habe ich wie in der Doku beschrieben ein Update ausgeführt. Danach startete das Teil nicht mehr.

Schließt das nicht ein defektes Dateisystem aus ?

T1mey commented 2 years ago

Das "Segmentation fault" klingt nicht gut, das bedeutet, dass der auf deinem System installierte Compiler defekt ist. Ich würde stark von einer defekten SD Karte oder einem defekten Dateisystem ausgehen.

Raspi nochmal neu installiert und pivccu manuell installiert auf der selben SD Karte... Funktioniert nun. Kann also ein Problem beim Updateprozess zu sein.

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.