No USB related messages at the time of failure?

Colin

On 27 May 2017 at 09:02, Mick Sulley <m...@sulley.info> wrote:
> 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
>
>
>
> On 27/05/17 08:24, Colin Law wrote:
>>
>> 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
>>
>> On 26 May 2017 at 21:35, Mick Sulley <m...@sulley.info> wrote:
>>>
>>> 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
>>>
>>>
>>>
>>> On 09/03/17 10:15, Mick Sulley wrote:
>>>>
>>>> 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
>>>> Owfs-developers@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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
>>> Owfs-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>> Owfs-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>
> ------------------------------------------------------------------------------
> 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
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------
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
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to