Certain channels cause reboot - HR10-250

[herbally]

I installed TivoWebPlus, and mfs_ftp, and subsequently my HR10-250 reboots every time I change the channel to 213 or 214 and certain others that I'm not sure of. Is this a frequent problem, and if so could someone give me a pointer as to how to correct it? Everything else works just fine including video extraction and remote management via web browser.

Seems as though the channels that cause reboot are preview channels.

Thanks in advance,
Herbally

[cheer]

I don't have this problem myself. However, I vaguely remember reading that a somewhat similar probel was traced to a bad tivoapp patch. You might try restoring your stock tivoapp and see if the problem goes away. If it does, then hunt down Alphawolf's thread on disabling tystream encryption and get the latest, greatest patch for 3.1.5f.

[herbally]

replaced tivoapp with original....can get channel 213 and 214 now but newly discovered that channel 24 will reboot...

[herbally]

Ok...I've repatched using alphawolf's post as a guideline, and once again encryption is disabled. After patching channel 213, 24 or 96 will all reboot the reciever. Seems like any channel not in the DTV channel list will cause a reboot, plus apparently some that are on the list(213).

Hopefully this info will help narrow it down..

I appreciate the assistance btw.

Herbally

[herbally]

Maybe this will help? this came from the tverr log...

Log cleared on Fri Mar 24, 2006 by TivoWebPlus
Mar 24 16:46:51 (none) TvVideoManager[181]: Tmk Fatal Error: Thread TvVideoManager <181> died due to signal 11
Mar 24 16:46:51 (none) TvVideoManager[181]: pc 0xaa7c90 status 0xa001d413 cause 0x000008 bva 0x81dbfde8 hi 00000000 lo 0x1f2ba510
Mar 24 16:46:51 (none) TvVideoManager[181]: R00 0x00000000 R01 0xb001d400 R02 0x00000000 R03 0x00000000
Mar 24 16:46:51 (none) TvVideoManager[181]: R04 0x7f5c5724 R05 0x00000000 R06 0x00000a28 R07 0x00000000
Mar 24 16:46:51 (none) TvVideoManager[181]: R08 0x1006c4a8 R09 0x7fff74b0 R10 0x00000000 R11 0x00000002
Mar 24 16:46:51 (none) TvVideoManager[181]: R12 0x00000000 R13 0x88000000 R14 0x0000a510 R15 0x00000000
Mar 24 16:46:51 (none) TvVideoManager[181]: R16 0x7fff74b8 R17 0x7f5c5704 R18 0x7f61d0f8 R19 0x7fff7610
Mar 24 16:46:51 (none) TvVideoManager[181]: R20 0x00000007 R21 0x4a440355 R22 0x00000003 R23 0x7fff76e0
Mar 24 16:46:51 (none) TvVideoManager[181]: R24 0x00000000 R25 0x00b89778 R26 0x00000000 R27 0x00000000
Mar 24 16:46:51 (none) TvVideoManager[181]: R28 0x10048590 R29 0x7fff74a0 R30 0x7f5c4680 R31 0x00aa7ba0
Mar 24 16:46:51 (none) TvVideoManager[181]: F00 0x3ff918d23a800000 F02 0x0000000000000001
Mar 24 16:46:51 (none) TvVideoManager[181]: F04 0xffffffffffffffff F06 0xffffffffffffffff
Mar 24 16:46:51 (none) TvVideoManager[181]: F08 0xffffffffffffffff F10 0xffffffffffffffff
Mar 24 16:46:51 (none) TvVideoManager[181]: F12 0xffffffffffffffff F14 0xffffffffffffffff
Mar 24 16:46:51 (none) TvVideoManager[181]: F16 0xffffffffffffffff F18 0xffffffffffffffff
Mar 24 16:46:51 (none) TvVideoManager[181]: F20 0xffffffffffffffff F22 0xffffffffffffffff
Mar 24 16:46:51 (none) TvVideoManager[181]: F24 0xffffffffffffffff F26 0xffffffffffffffff
Mar 24 16:46:51 (none) TvVideoManager[181]: F28 0xffffffffffffffff F30 0xffffffffffffffff
Mar 24 16:46:51 (none) TvVideoManager[181]: csr 0x001004 eir 0x005410
Mar 24 16:46:51 (none) TvVideoManager[181]: Tmk Thread Backtrace: aa7c90 992804 9b9cf0 9b8ce0 99ed10 99b8e8 dbca48 dbd410 dbd378 ded188 e09a98
Mar 24 16:46:51 (none) TvVideoManager[181]: Tmk Fatal Error: Thread died due to signal 11
Mar 24 16:46:51 (none) TvVideoManager[181]: Invoking rule 834: rebooting system

[Jamie]

Yep, you have exactly the same problem described here (http://www.dealdatabase.com/forum/showthread.php?p=248330#post248330) and it's the result of applying the 3.1.5 nocso patch to a 3.1.5f tivoapp. I know you said you reverted back to a stock tivoapp, but apparently it wasn't truly stock. A 3.1.5f tivoapp has md5sum: f22417c127b5b2f3a2d7d28c547e2575.

If you have any doubts of this diagnosis, you can check by hexdumping the section of tivoapp modified by the bad patch:bash-2.02# dd if=/tvbin/tivoapp bs=1 count=4 skip=6978700 | hexdump
4+0 records in
4+0 records out
0000000 005c 1021
0000004
That's the result you should get on an unpatched or properly patched 3.1.5f tivoapp. On a 3.1.5f tivoapp patched with the 3.1.5 patch you'll see 0000000 3c02 0000.

[PlainBill]

And at a guess, this problem is caused by following a guide written for 3.1.5, and never updated for later versions.

PlainBill

[herbally]

Jamie,

You're my hero!

I definitely remember following the instructions in Dsmooth's guide, and running into problems due to 3.1.5f. Only thing that seems odd is that the backup of tivoapp that I put on the tivobox app is apparently not my original somehow.

I see now what you guys mean about guides...sorry ew...guides are apparently the root of all evil. However, I learned what would've probably taken weeks in a couple days following that guide...so I guess they aren't all bad.

Anyway....thanks a lot...I really appreciate it.