Re: [mh] Detecting/recovering from PLM hang

[Marc M. <ma...@me...>]

On Mon, Jan 04, 2010 at 09:20:54AM -0500, Gregg Liming wrote:
> the new design because there's no command overloading.  #2 is more 
> problematic as I have never been able to reproduce the problem on demand 
> until I started the rewrite.  It turns out that it is possible to send 
> the PLM invalid messages that will cause a lockup.  IMO, that doesn't 
> speak very well of insteon designers.  But, to be fair, I should be 

For what it's worth, I got lockups out of the blue after 10 months of
having a fully working config, changed the PLM for a new one without
otherwise touching my config, and the lockups went away.
(as a reminder, the PLM would lockup within 15mn after being unplugged
and plugged back in when it had run flawlessly for months before that).

Just one data point to say that lockups can apparently be due to a PLM
that went bad.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/