[Owfs-developers] System Lock-up?

Discussion:

Mick Sulley

2017-03-09 10:15:57 UTC

My system is Raspberry Pi 3 running owserver etc 3.1p5 with Sheepwalk
RPi3 adapter and RPi3a splitters giving me 8 channels. All devices are
powered, separately from the Pi. I use python code and pyownet to
monitor and control a mixture of about 35 DS1820 and DS2413

The system has been running fairly successfully for several years, but
today it failed. I think I can solve the basic failure, the thing that
puzzles me is that when I rebooted 2 of the 8 channels were missing. I
rebooted again, checked the cabled, still the same two channels
missing. I then shut it down and power cycled it and then all channels
were back again.

Is this a known issue? Is there any way to reset a channel other than
power cycle?

Thanks

Mick

Matthias Urlichs

2017-03-09 10:50:57 UTC

Permalink

Post by Mick Sulley
Is this a known issue?

Sometimes an IC gets into an inconsistent internal state when it gets
hit by e.g. a short power drop.
There's not much you can do about that.

Post by Mick Sulley
Is there any way to reset a channel other than
power cycle?

Not that I know of.
Frankly, if the chip is in a state like the one you describe, I wouldn't
trust a partial reset anyway.

--
-- Matthias Urlichs

Mick Sulley

2017-05-26 20:35:07 UTC

Permalink

Thanks for your comments Matthias. It happened again today, same
channels I think. Could it be temperature related? The Pi etc is in
the loft and it was around 40C in there today, so the Pi would be
somewhat above that.

Mick

Post by Mick Sulley
My system is Raspberry Pi 3 running owserver etc 3.1p5 with Sheepwalk
RPi3 adapter and RPi3a splitters giving me 8 channels. All devices are
powered, separately from the Pi. I use python code and pyownet to
monitor and control a mixture of about 35 DS1820 and DS2413
The system has been running fairly successfully for several years, but
today it failed. I think I can solve the basic failure, the thing that
puzzles me is that when I rebooted 2 of the 8 channels were missing. I
rebooted again, checked the cabled, still the same two channels
missing. I then shut it down and power cycled it and then all channels
were back again.
Is this a known issue? Is there any way to reset a channel other than
power cycle?
Thanks
Mick
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Owfs-developers mailing list
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Colin Law

2017-05-27 07:24:17 UTC

Permalink

Have a look in /var/log/syslog and see if there are any interesting
messages around the time of failure. If syslog does not go back far
enough look in /var/log/syslog.1

Colin

Thanks for your comments Matthias. It happened again today, same channels I
think. Could it be temperature related? The Pi etc is in the loft and it
was around 40C in there today, so the Pi would be somewhat above that.
Mick

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Owfs-developers mailing list
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Mick Sulley

2017-05-27 08:02:20 UTC

Permalink

There are loads of messages like this

May 25 08:21:32 pi-solar kernel: [1007793.425520] w1_master_driver
w1_bus_master1: Family 0 for 00.ec8a00000000.82 is not registered.
May 25 08:22:21 pi-solar kernel: [1007842.625340] w1_master_driver
w1_bus_master1: Family 0 for 00.1c8a00000000.f6 is not registered.
May 25 08:23:08 pi-solar kernel: [1007889.965685] w1_master_driver
w1_bus_master1: Family 0 for 00.9c8a00000000.7a is not registered.
May 25 08:23:44 pi-solar kernel: [1007925.365323] w1_master_driver
w1_bus_master1: Family 0 for 00.5c8a00000000.b0 is not registered.

That is before the problem, but then at the time of the problem it
changes to this

May 26 09:59:23 pi-solar kernel: [74474.176012] w1_master_driver
w1_bus_master1: Family 0 for 00.006000000000.5a is not registered.
May 26 09:59:23 pi-solar rsyslogd-2007: action 'action 17' suspended,
next retry is Fri May 26 09:59:53 2017 [try http://www.rsyslog.com/e/2007 ]
May 26 10:00:21 pi-solar kernel: [74532.526719] w1_master_driver
w1_bus_master1: Family 0 for 00.806000000000.d6 is not registered.
May 26 10:00:21 pi-solar rsyslogd-2007: action 'action 17' suspended,
next retry is Fri May 26 10:00:51 2017 [try http://www.rsyslog.com/e/2007 ]
May 26 10:00:57 pi-solar kernel: [74568.786610] w1_master_driver
w1_bus_master1: Family 0 for 00.406000000000.1c is not registered.
May 26 10:00:57 pi-solar rsyslogd-2007: action 'action 17' suspended,
next retry is Fri May 26 10:01:27 2017 [try http://www.rsyslog.com/e/2007 ]
May 26 10:01:34 pi-solar kernel: [74605.158192] w1_master_driver
w1_bus_master1: Family 0 for 00.c06000000000.90 is not registered.
May 26 10:01:34 pi-solar rsyslogd-2007: action 'action 17' suspended,
next retry is Fri May 26 10:02:04 2017 [try http://www.rsyslog.com/e/2007 ]

The action 17 may be nothing related, don't know. I have looked at
http://www.rsyslog.com/e/2007 and it didn't help me much.

Any ideas?

Thanks
Mick

Post by Colin Law
Have a look in /var/log/syslog and see if there are any interesting
messages around the time of failure. If syslog does not go back far
enough look in /var/log/syslog.1
Colin

Thanks for your comments Matthias. It happened again today, same channels I
think. Could it be temperature related? The Pi etc is in the loft and it
was around 40C in there today, so the Pi would be somewhat above that.
Mick

Colin Law

2017-05-27 10:12:41 UTC

Permalink

No USB related messages at the time of failure?

Colin

Post by Mick Sulley
There are loads of messages like this
May 25 08:21:32 pi-solar kernel: [1007793.425520] w1_master_driver
w1_bus_master1: Family 0 for 00.ec8a00000000.82 is not registered.
May 25 08:22:21 pi-solar kernel: [1007842.625340] w1_master_driver
w1_bus_master1: Family 0 for 00.1c8a00000000.f6 is not registered.
May 25 08:23:08 pi-solar kernel: [1007889.965685] w1_master_driver
w1_bus_master1: Family 0 for 00.9c8a00000000.7a is not registered.
May 25 08:23:44 pi-solar kernel: [1007925.365323] w1_master_driver
w1_bus_master1: Family 0 for 00.5c8a00000000.b0 is not registered.
That is before the problem, but then at the time of the problem it changes
to this
May 26 09:59:23 pi-solar kernel: [74474.176012] w1_master_driver
w1_bus_master1: Family 0 for 00.006000000000.5a is not registered.
May 26 09:59:23 pi-solar rsyslogd-2007: action 'action 17' suspended, next
retry is Fri May 26 09:59:53 2017 [try http://www.rsyslog.com/e/2007 ]
May 26 10:00:21 pi-solar kernel: [74532.526719] w1_master_driver
w1_bus_master1: Family 0 for 00.806000000000.d6 is not registered.
May 26 10:00:21 pi-solar rsyslogd-2007: action 'action 17' suspended, next
retry is Fri May 26 10:00:51 2017 [try http://www.rsyslog.com/e/2007 ]
May 26 10:00:57 pi-solar kernel: [74568.786610] w1_master_driver
w1_bus_master1: Family 0 for 00.406000000000.1c is not registered.
May 26 10:00:57 pi-solar rsyslogd-2007: action 'action 17' suspended, next
retry is Fri May 26 10:01:27 2017 [try http://www.rsyslog.com/e/2007 ]
May 26 10:01:34 pi-solar kernel: [74605.158192] w1_master_driver
w1_bus_master1: Family 0 for 00.c06000000000.90 is not registered.
May 26 10:01:34 pi-solar rsyslogd-2007: action 'action 17' suspended, next
retry is Fri May 26 10:02:04 2017 [try http://www.rsyslog.com/e/2007 ]
The action 17 may be nothing related, don't know. I have looked at
http://www.rsyslog.com/e/2007 and it didn't help me much.
Any ideas?
Thanks
Mick

Post by Colin Law
Have a look in /var/log/syslog and see if there are any interesting
messages around the time of failure. If syslog does not go back far
enough look in /var/log/syslog.1
Colin

Thanks for your comments Matthias. It happened again today, same channels I
think. Could it be temperature related? The Pi etc is in the loft and it
was around 40C in there today, so the Pi would be somewhat above that.
Mick

Mick Sulley

2017-05-27 14:09:36 UTC

Permalink

No usb messaged, but 1-wire is via a Sheepwalk RPi3 adapter and RPi3a
splitter

Post by Colin Law
No USB related messages at the time of failure?
Colin

Post by Colin Law
Have a look in /var/log/syslog and see if there are any interesting
messages around the time of failure. If syslog does not go back far
enough look in /var/log/syslog.1
Colin

Thanks for your comments Matthias. It happened again today, same channels I
think. Could it be temperature related? The Pi etc is in the loft and it
was around 40C in there today, so the Pi would be somewhat above that.
Mick

Mick Sulley

2017-05-27 21:37:07 UTC

Permalink

Thanks for your comments Jan, not what I wanted to hear but I'm sure you
are correct. The last time I used an oscilloscope I was in college and
had to wait for the valves to warm up before it would work :)

I do have a spare RPi3 adapter so I will try that first and see what the
log says then.

Mick

There is no "Family 0". Your setup is broken. Either the kernel is bogus
or your host adaptor.

Post by Mick Sulley
That is before the problem, but then at the time of the problem it
changes to this
May 26 09:59:23 pi-solar kernel: [74474.176012] w1_master_driver
w1_bus_master1: Family 0 for 00.006000000000.5a is not registered.

This looks horribly wrong. I doubt there is any chip with that ID out there.

Post by Mick Sulley
May 26 09:59:23 pi-solar rsyslogd-2007: action 'action 17' suspended,
next retry is Fri May 26 09:59:53 2017 [try http://www.rsyslog.com/e/2007 ]
May 26 10:00:21 pi-solar kernel: [74532.526719] w1_master_driver
w1_bus_master1: Family 0 for 00.806000000000.d6 is not registered.

Same here.

Post by Mick Sulley
May 26 10:00:21 pi-solar rsyslogd-2007: action 'action 17' suspended,
next retry is Fri May 26 10:00:51 2017 [try http://www.rsyslog.com/e/2007 ]
May 26 10:00:57 pi-solar kernel: [74568.786610] w1_master_driver
w1_bus_master1: Family 0 for 00.406000000000.1c is not registered.

Same here.

Post by Mick Sulley
May 26 10:00:57 pi-solar rsyslogd-2007: action 'action 17' suspended,
next retry is Fri May 26 10:01:27 2017 [try http://www.rsyslog.com/e/2007 ]
May 26 10:01:34 pi-solar kernel: [74605.158192] w1_master_driver
w1_bus_master1: Family 0 for 00.c06000000000.90 is not registered.

Same here.

Post by Mick Sulley
Any ideas.

This pretty much looks like random jitter on your bus line which is
mistaken for being chip ideas.
Hook up an oscilloscope to your bus line and look for serious jitter.
Kind regards
Jan

Continue reading on narkive:

Search results for '[Owfs-developers] System Lock-up?' (Questions and Answers)

replies

My system locks up everytime I access a hard disc on my system that i keep just for storage...Dr. Morton?

started 2006-05-17 20:50:09 UTC

software

replies

HELP! A trojan downloaded some fake antivirus program onto my laptop called "System Lock".....?

started 2011-03-08 23:12:41 UTC

security

replies

My Toyota Sienna 2006 LE Rear DVD says "System Lock"?