Help! HR10-250 Stuck in a nasty reboot loop

[Yazhol]

Guys,

When I woke up Friday my HR10-250 was stuck in a reboot loop. It would get as far as 95% on aquiring satellite and then at the point where it normally gives you picture, BAM, it reboots... This is after months of perfect operation. I'm running 3.1.5f with telnet, ftp, mfs_ftp, tivowebplus, 30 sec skip, no scramble, automatic sort, backdoors enabled. And it was running 2x250gb drives.

I tried on Friday night after getting home from work to read the logs and figure out what's going on. I finally gave up on that and decided to put a known good image on the system. I pulled the drives and restored a known good image to a single drive and put it in the unit. It still does the same thing.... Thinking it may be a Hard Drive issue I use the other drive, that was the slave previously, and place my known good image on it. Same result. I re-image both drives a few times each time getting the same reboot at 95%... I then decide to use InstantCakeHD to restore a fresh image. The system boots up fine, with no hacks, etc. So for the heck of it I pull the drive with the "stock" image on it and put a drive in with my known good hacked image on it, it boots fine... For the last few days the unit has been operating like it should, with maybe 2 random reboots.

However I woke up this morning to once again find the unit in the same reboot loop. I have disabled all my hacks that are in rc.sysinit.author and that does not help.

Again, this is happening with a known good image that worked fine for months... And nothing was changed on the unit in that time.

I've pasted the error I found in my tverr log below. I've searched the boards on it and find nothing. Any clues??

Any help will be appreciated!

May 2 14:04:08 (none) TvVideoManager[199]: Tmk Fatal Error: Thread TvVideoManager <199> died due to signal 11
May 2 14:04:08 (none) TvVideoManager[199]: pc 0xaa7c90 status 0x8001d413 cause 0x000008 bva 0x81dbfde8 hi 00000000 lo 0x339cf788
May 2 14:04:08 (none) TvVideoManager[199]: R00 0x00000000 R01 0xb001d400 R02 0x00000000 R03 0x00000000
May 2 14:04:08 (none) TvVideoManager[199]: R04 0x7f5bfbe4 R05 0x0f795dfc R06 0x7f5bfbec R07 0x00000000
May 2 14:04:08 (none) TvVideoManager[199]: R08 0x00000000 R09 0x7fff7470 R10 0x00000000 R11 0x00000002
May 2 14:04:08 (none) TvVideoManager[199]: R12 0x00000000 R13 0x7c000000 R14 0x0000a510 R15 0xb6d92000
May 2 14:04:08 (none) TvVideoManager[199]: R16 0x7fff7478 R17 0x7f5bfbbc R18 0x7f5fc504 R19 0x7fff75d0
May 2 14:04:08 (none) TvVideoManager[199]: R20 0x00000004 R21 0xeeff3c10 R22 0x00000003 R23 0x7fff76a0
May 2 14:04:08 (none) TvVideoManager[199]: R24 0x00000000 R25 0x00b89778 R26 0x00000000 R27 0x00000000
May 2 14:04:08 (none) TvVideoManager[199]: R28 0x10048590 R29 0x7fff7460 R30 0x7f5beb98 R31 0x00aa7ba0
May 2 14:04:09 (none) TvVideoManager[199]: Tmk Thread Backtrace: aa7c90 992804 9b9cf0 9b8ce0 99ed10 99b8e8 dbca48 dbd410 dbd378 ded188 e09a98
May 2 14:04:09 (none) TvVideoManager[199]: Tmk Fatal Error: Thread died due to signal 11
May 2 14:04:09 (none) TvVideoManager[199]: Invoking rule 834: rebooting system

[Yazhol]

UPDATE: Using Clear And Delete Everything does nothing to solve the problem.


I've now got an unhacked 3.1.5f image running fine on a Hard Drive that was once 3.1.5f Hacked and stuck in the reboot loop. Doesn't seem to be a Hard Drive issue.

[vega]

you may want to check your cables from the dish to the receiver, and the dish alignment. looks like a signal loss issue. hopefully that is the problem, because the other source could be a failing input on the IRD.

[Yazhol]

It's not a cable issue.. And the IRD is only 3 months old...

I took a stock image and hacked it from the ground up adding 1 hack at a time. Been up now for 18 hours without a reboot. This doesn't explain why it was doing what it was doing with a known good image though...

[vega]

It's not a cable issue.. And the IRD is only 3 months old...

I took a stock image and hacked it from the ground up adding 1 hack at a time. Been up now for 18 hours without a reboot. This doesn't explain why it was doing what it was doing with a known good image though...

I hope your luck is better than mine. I had the exact same problem with mine, did pretty much the same, it lasted about 2 months without any problems, then no matter what I did, I could no longer get past the 96% mark. I sent it back to BestBuy, and luckily Hughes sent me a new receiver in 3 weeks with a letter explaining that the inputs were failing. They didn't even complain about the warranty sticker.

[Yazhol]

All went fine for one week... Now I'm back to where I was.... At 9:50 this morning I checked and the unit had been up for 1 day and 4 hours. At 9:55 it was back to the reboot loop again with the same entry in the logs.

Anyone have ANY idea????

May 10 14:57:13 (none) TvVideoManager[198]: Tmk Fatal Error: Thread TvVideoManager <198> died due to signal 11
May 10 14:57:13 (none) TvVideoManager[198]: pc 0xaa7c90 status 0x8001d413 cause 0x000008 bva 0x81dbfde8 hi 00000000 lo 0x1d49c5b0
May 10 14:57:13 (none) TvVideoManager[198]: R00 0x00000000 R01 0xb001d400 R02 0x00000000 R03 0x00000000
May 10 14:57:13 (none) TvVideoManager[198]: R04 0x7f5c005c R05 0x0f7c71dc R06 0x7f5c0054 R07 0x00000000
May 10 14:57:13 (none) TvVideoManager[198]: R08 0x00000000 R09 0x7fff7470 R10 0x00000000 R11 0x00000002
May 10 14:57:13 (none) TvVideoManager[198]: R12 0x00000000 R13 0x4f000000 R14 0x0000a510 R15 0xa268a000
May 10 14:57:13 (none) TvVideoManager[198]: R16 0x7fff7478 R17 0x7f5c0024 R18 0x7f5d1cb4 R19 0x7fff75d0
May 10 14:57:13 (none) TvVideoManager[198]: R20 0x00000006 R21 0x82e7ee3d R22 0x00000003 R23 0x7fff76a0
May 10 14:57:13 (none) TvVideoManager[198]: R24 0x00000000 R25 0x00b89778 R26 0x00000000 R27 0x00000000
May 10 14:57:13 (none) TvVideoManager[198]: R28 0x10048590 R29 0x7fff7460 R30 0x7f5bf530 R31 0x00aa7ba0
May 10 14:57:13 (none) TvVideoManager[198]: Tmk Thread Backtrace: aa7c90 992804 9b9cf0 9b8ce0 99ed10 99b8e8 dbca48 dbd410 dbd378 ded188 e09a98
May 10 14:57:13 (none) TvVideoManager[198]: Tmk Fatal Error: Thread died due to signal 11
May 10 14:57:13 (none) TvVideoManager[198]: Invoking rule 834: rebooting system