Anyone having troubles with raspbian Stretch?

---

After running Pimatic on Raspbian Jessie for over a year, i recently ran into trouble because of what i thought was a faulty SD-card. Yesterday i decided to start over from scratch so i downloaded the raspbian stretch image and did a fresh pimatic install following this manual https://forum.pimatic.org/topic/2083/v0-9-install-pimatic-v0-9-from-scratch/2 .
First problem i encountered was ‘Error reading DS18B20Sensor’ which i fixed by adding the line ‘dtoverlay=w1-gpio’ to /boot/config.txt.

After that everything worked fine. At least i thought so. After about 17 hours the system froze, just after pimatic closed my window shutter.
This is the entry in pimatic-daemon.log:
17:33:43.791 [pimatic] info: rule sunset-rolladen-down: press button roll3 of device rolladen

The log file suggests the system is rebooting after that:

17:33:43.791 [pimatic] info: rule sunset-rolladen-down: press button roll3 of device rolladen 17:17:11.224 2017-11-03 Friday 17:17:23.139 [pimatic] info: Starting pimatic version 0.9.42 17:17:29.005 [pimatic, ppm] info: 2.15.12

Look at the timestamp: time is going back??

This is from syslog around that time:
Nov 3 13:17:01 raspberrypi CRON[1264]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 3 14:17:01 raspberrypi CRON[1317]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 3 15:17:01 raspberrypi CRON[1344]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 3 16:17:01 raspberrypi CRON[1373]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 3 17:17:01 raspberrypi CRON[1402]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 3 17:17:04 raspberrypi systemd-modules-load[109]: Inserted module 'i2c_dev' Nov 3 17:17:04 raspberrypi fake-hwclock[117]: Fri Nov 3 16:17:01 UTC 2017 Nov 3 17:17:04 raspberrypi systemd[1]: Started Create Static Device Nodes in /dev. Nov 3 17:17:04 raspberrypi systemd-fsck[119]: e2fsck 1.43.4 (31-Jan-2017) Nov 3 17:17:04 raspberrypi systemd[1]: Starting udev Kernel Device Manager... Nov 3 17:17:04 raspberrypi systemd-fsck[119]: /dev/mmcblk0p2: clean, 164257/473888 files, 1230066/1928704 blocks Nov 3 17:17:04 raspberrypi systemd[1]: Started File System Check on Root Device. Nov 3 17:17:04 raspberrypi systemd[1]: Starting Remount Root and Kernel File Systems...

I’m using a Pi 2 Model B v1.1. Is this kernel related and if so where can i find a jessie image? The don’t seem to be offered on raspberrypi.org anymore. Or am i having hardware trouble? Anybody got an idea?

hi
@fregger
you can found the jessie and older releases on raspian archiv

Regards

@unix thank you!

The real challenge of course would be to get things going on stretch as well. My understanding is that quite a lot has changed since kernel 3.18 with a configuration change to enable Device Tree support by default and having ipv6 enabled by default as well. Hence my question: is there anybody out there who has pimatic succesfully configured on Stretch? We might be able to whip up a ‘how-to-install’.

See also https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=97314

@fregger May be the firmware is too old?! Can you please check which version you have.
Simply call /opt/vc/bin/vcgencmd version and post the output.

@mwittig said in Anyone having troubles with raspbian Stretch?:

/opt/vc/bin/vcgencmd version

Looks quite recent to me:
Oct 24 2017 17:09:22 Copyright (c) 2012 Broadcom version a3d7660e6749e75e2c4ce4d377846abd3b3be283 (clean) (release)

Just now, the system froze again after about 20 hours but this time at least syslog gave me this:

==> /var/log/syslog <== Nov 5 23:33:48 raspberrypi kernel: [69170.154449] INFO: rcu_sched detected stalls on CPUs/tasks: Nov 5 23:33:48 raspberrypi kernel: [69170.154482] 0-...: (1 GPs behind) idle=701/1/0 softirq=127186/127186 fqs=12 Nov 5 23:33:48 raspberrypi kernel: [69170.154486] (detected by 2, t=2142 jiffies, g=62446, c=62445, q=22) Nov 5 23:33:48 raspberrypi kernel: [69170.154499] Task dump for CPU 0: Nov 5 23:33:48 raspberrypi kernel: [69170.154504] swapper/0 R running task 0 0 0 0x00000002

This has been bugging me for weeks now.

So i started from scratch with a Jessie image but my problem with the stalled CPU kept coming back: after 24 to 28 hours the Pi would freeze. Then i noticed that a couple of hours before the stall my three DS18B20 temperature sensors stopped giving any readings. So i searched and searched until i found this post that suggests that the Pi2 can’t handle simultaneous GPIO interrupts:

https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=137581

With that in mind i reconfigured the pimatic-ds18b20 plugin so that the three sensors at least are not trying to get readings simultaneously. Since then my Pi has been up for over 42 hours and counting.

Could i be on to something here? The funny thing is that before, also with Jessie the setup with the three ds18b20’s, the system had been running flawlessly for at least six months.

@sweetpi What’s your opinion on this?