HD Extender locks up on occasion?

[jm987]

Was using components on one of them and HDMI/DVI cable on the other one. Still getting lock ups once in a while.

Haven't had any lock ups since I changed from component cables to svideo. (did that last night because the component cables made the picture very dark)

I've only had the issue with the latest firmware of the box. I haven't had the issue in a couple of days now. If I see the issue, I may switch back to 6.3.5 because I don't remember ever having it with that version.

[carlgar]

Originally Posted by jm987

I've only had the issue with the latest firmware of the box. I haven't had the issue in a couple of days now. If I see the issue, I may switch back to 6.3.5 because I don't remember ever having it with that version.

Good luck with that, be sure to post whether it works or not. I think it is more of a selective type memory issue. Since this issue can occur only once every serveral days it is very easy to encounter and just ignore as a fluke. I just happened to become aware of it very early because it appeared to be a extension of a known problem problem (Vista tcp stack issue) which had prevented me from using the MVP extender for several months.

[hemicuda]

nuts. wife just IM'd me and said we got a hard lockup on the HD100 a few minutes ago. I still have logging enabled so I can check it when I get home.

[carlgar]

Originally Posted by peternm22

I use to power off the box every night (the switch on the back), then I switched to putting it into standby every night so that startup time is faster. I haven't seen any difference in the frequency of lock ups.

I can now verify this. I just encountered another lockup and it was powered off last night. The lockup occured early in a 480i program while skipping. The log showed it trying to find a better position then the standard Vista TCP stack error. It looks like the server was trying to return the new position to the extender when it hung.

[scm]

Originally Posted by carlgar

Does anyone seeing these hangs power off the box overnight?

I'm not sure my issue is the same as the one discussed here. I did not power down or place my unit into standby and did not see lock-ups for the first few days. Then I found the discreet on/off codes and programmed them into my universal remote to place the extender into standby each time I turn off the TV. When I power-up the extender, I now get a random failure of the box to start-up that requires me to restart the Sage Service on my server. The Extender locks up at the logo screen. I've tried just restarting my router in case this was a network issue, but only a service restart helps.

I have also had now 3-4 lockups during playback that does seem similar to the issues discussed here.

[btrcp2000]

I have been running okay for a week or so, but saw some silliness last night watching basketball. The picture would freeze at the hour or half-hour mark, but I could just stop playback and retune the channel, so not a total lockup. I have seen this on the server, but this is the first I have seen on the extender.

This is with the 12242007 or thereabouts firmware which has seemed to be pretty stable. Tonight I will have about ten people downstairs watching the XU/WVU game on the other (my first) extender with the latest firmware, and they will all remind me of how the thing froze right at David Tyree's Super Bowl-saving catch a couple months ago. God help us all.

[jelentz@gmail.c]

I'm new to the sage scene - still working on getting the kinks out of the system. I have an HD100 (second run - only a few weeks old) and it always locks when I try to play an mpeg4 file. Running the same file through a sage client works, with a lot of stuttering, but doesn't lock. Running same file through windows media center and it plays fine. When the HD100 locks, I get solid power, link and IR lights. It won't respond to anything but the off switch on the back.

Just another bad lock story I guess. (Sorry, couldn't resist)

John

[carlgar]

If you are saying that you can get the HD extender to lock up 100% of the time, you should notify support. This problem has very difficult to track down because it is random. I suspect you are seeing a different problem but it still needs to be corrected.

[jelentz@gmail.c]

I have notified support. Waiting on a response though. Mainly wondering if anyone else is having issues with mpeg4 files.

[carlgar]

Today, at the request of support I changed from using dynamic ip to a static IP address. Has anyone encountered these hangs while using static ip addresses?

[hemicuda]

Been using static since day one. but then again, even my DHCP is static via a MAC address file on the router.

I woke up this morning to a powered off HD100. Remote would blink the light. Used the standby button to turn it on, but it froze on the splash screen. Sent an email to support w/ logs showing "hang detected." The Sage service also snapped up an additional 100MB of RAM. It normally runs in the 150-170MB range, but after an HD100 freeze it jumps into the mid 200s. Had to restart the service.

[ChubbyTiger]

I'm getting similar, random lockups. So far, they seem to be fixable by standby-ing the box. The service hasn't had any problems that I know of. Some of you have been talking about log files. What log are you looking at?

Also, my router is sort of a POS. Would it be possible that the problem is server/HD100 communication related? Has anybody taken the router/switch out of the equation to see if things change?

[carlgar]

The log files are the normal Sage server log files that are generated by adding the debug logging command to the properties file. See the FAQ for actual command. The log file is of no value for this hang, it is local to the HD extender.
This problem is not related to the network, but other problems could be the result of network issues.

I am hoping that the problem is related to the use of DHCP but I will not be sure until next tuesday ofr the next occurance of the issue.

[btrcp2000]

fwiw, i just put all my sage stuff (3 mvps, server, 2 hd ext's) on a brand new dlink gigabit switch from an old POS 10/100 switch that I paid $8 for a while back. I haven't achieved nirvana yet, but my hd ext's are much more stable. All I see now is an occasional frozen picture on a channel change, which can be fixed by hitting stop and re-tuning. I don't think I have had to standby at all since. I have original fw on one and most recent on the other.

[Taddeusz]

I've never been a huge fan of D-Link products but after hearing so much praise over the DIR-655 I ended up buying a DIR-625, which is basically the same thing but without the built-in gigabit switch. I already had a couple D-Link gigabit switches set up that everything was connected through. I was rather impressed with the DIR-625. Much nicer and more feature rich setup than all the other D-Link products.

But the way I have my network setup none of the actual local network traffic goes through my router only through the switches. Only internet bound traffic goes that way.

[reidfo]

I haven't followed this thread very closely, so I don't know if anyone else has posted about this. I installed Vista SP1 on my server a week or so ago and have not had lockups on either of my HD100 extenders since. *knock on wood* I was getting lockups constantly on changing channels, fast forward, you name it.

[carlgar]

You don't say what you were using before installing Vista SP1 but if you were running the original Vista you probably were seeing the original Vista TCP stack issue. That problem was corrected with the SP1 RC1 release. I have been running with Vista SP1 for quite a while and still see this issue on a regular (at least once a week) basis.

[pjpjpjpj]

I have started having a strange lock-up situation on my HD100 Extenders. It only happens when I try to enter a new "Favorite", and go to the "channel" option (where you choose what channel(s) the Favorite will record on). When I select that button, the Extender locks up (every other part of the "Favorites" menu works fine). It still receives the remote signal (green light flickers) but it's locked up. The only button that does anything is standby (it does go to standby). I tried "rebooting" from standby (holding "Home" for a few seconds) and that does not work. The only thing that brings it back is manually turning it off and back on with the switch on back.

While all of this is happening, Sage is still running fine on the server; in fact, I can pull up Sage on the server, go to the Favorites menu, go to that very show that I was adding as a "Favorite", and set the station option, with no problems at all.... so it must be just some glitch with the Extenders.

[hemicuda]

I also noticed during the last week of logging and emails to Sage support that logging actually seemed to make the problem worse. I had several lockups/freezes within a few hours one day w/ debug enabled.

[clayginn]

I have same issue that all a talking about. Do we need to report to Sage also or just wait for a fix?