Hallo, nach einen Upgrade (ohne Fehler) von
5.1-3138 auf 5.2-4062 startet die IPSymcon nicht mehr.
pi@raspberrypi:~ $ sudo /etc/init.d/symcon status
IP-Symcon is not running.
pi@raspberrypi:~ $ sudo /etc/init.d/symcon start
IP-Symcon started with PID
pi@raspberrypi:~ $ sudo /etc/init.d/symcon status
IP-Symcon is not running.
Der Service schaft es irgendwie nicht ein PID zu vergeben.
Was machen?
pi@raspberrypi:/var/log/symcon $ sudo gdb /usr/bin/symcon
GNU gdb (Raspbian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/symcon...done.
(gdb) run
Starting program: /usr/bin/symcon
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Program received signal SIGILL, Illegal instruction.
0x017e36e8 in _armv7_tick ()
(gdb)
auch wenn ich mit c + Enter weiter gehe steht keine gescheite Fehlermeldung
pi@raspberrypi:~ $ sudo gdb /usr/bin/symcon
GNU gdb (Raspbian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/symcon...done.
(gdb) run
Starting program: /usr/bin/symcon
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Program received signal SIGILL, Illegal instruction.
0x017e36e8 in _armv7_tick ()
(gdb) c
Continuing.
Program received signal SIGILL, Illegal instruction.
0x01793650 in OBJ_nid2sn ()
(gdb) c
Continuing.
Program terminated with signal SIGILL, Illegal instruction.
The program no longer exists.
(gdb)
mache ich übrigens ein downgrade auf 5.1-3138…funktieniert symcon sofort wieder
pi@raspberrypi:~ $ sudo apt install symcon=5.1-3138
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be DOWNGRADED:
symcon
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
Need to get 43.8 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://apt.symcon.de stable/rpi armhf symcon armhf 5.1-3138 [43.8 MB]
Fetched 43.8 MB in 23s (1,851 kB/s)
dpkg: warning: downgrading symcon from 5.2-4062 to 5.1-3138
(Reading database ... 36959 files and directories currently installed.)
Preparing to unpack .../symcon_5.1-3138_armhf.deb ...
IP-Symcon is not running.
Unpacking symcon (5.1-3138) over (5.2-4062) ...
Setting up symcon (5.1-3138) ...
IP-Symcon is not running.
Starting...
IP-Symcon started with PID 16314
Processing triggers for systemd (232-25+deb9u11) ...
Processing triggers for man-db (2.7.6.1-2) ...
pi@raspberrypi:~ $
ich habe das ganz soeben noch einmal probiert. Leider noch immer der gleiche Fehler.
In der Anlage ist das gdb.log und ein putty.log wo meine Schritte ersichtlich sind.
dem kann ich mich anschließen.
Gilt auch für Buster, Kernel 4.19.66+, pi Revision 000e.
@Michael: in meiner mail jhabe ich auch schon davon berichtet, dass weder gdb ein log ausspuckt, noch Symcon soweit startet, dass ein log begonnen wird.
Die Stable läuft, testing und ninja nicht.
bin seit 6 Wochen auf IPS unterwegs und voll begeistert was ihr da macht!
Das Grundgesrüst steht und nun kommen die Feinheiten.
Mit der manuellen Moduleinbindung ist es oft nicht so einfach und den Modulstore finde ich als top Lösung.
ist schon bekannt wann 5.2 rauskommt.
Gibt es einen ungefähren Plan wann welche Module in den Store kommen?