Alpha Tester - Getting hideous reboots

General Discussion

Re: Alpha Tester - Getting hideous reboots

Postby Automan » Thu May 26, 2011 9:01 pm

mikerr wrote:I would advise deselecting channels that have no guide data in channels I receive,
as altEPG doesn't populate it with "to be announced" 2 hour chunks that tivo/tribune used to - its just totally blank.

[edit]ah, I see groovyclam beat me to it above


Will do but the problem only seemed to start on my box after today's daily call with the new format data which appends rather than replaces the data....

EDIT: The 16 channels with no guide data have been removed - I did not realise there were so many....

Automan.
Automan
TiVo lover
TiVo lover
 
Posts: 92
Joined: Tue May 17, 2011 9:06 am
Location: South Coast, Sussex, UK

Re: Alpha Tester - Getting hideous reboots

Postby Automan » Fri May 27, 2011 5:13 am

Removing channels with no guide data did not help :(

Code: Select all

May 27 01:03:59 (none) Scheduler[158]: Tmk Fatal Error: Thread Scheduler <158> died due to signal 11
May 27 01:03:59 (none) Scheduler[158]: NIP 0x1b96220 link 0x1b96554 ctr 28957736
May 27 01:03:59 (none) Scheduler[158]: R00 0x00000000 R01 0x7fffead0 R02 0x00000100 R03 0x7fb40020
May 27 01:03:59 (none) Scheduler[158]: R04 0x00000020 R05 0x7fbb48ec R06 0x00000000 R07 0x00000000
May 27 01:03:59 (none) Scheduler[158]: R08 0x80808080 R09 0x00000003 R10 0x0000012c R11 0x0000000c
May 27 01:03:59 (none) Scheduler[158]: R12 0x44200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 01:03:59 (none) Scheduler[158]: R16 0x018bdd4c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 01:03:59 (none) Scheduler[158]: R20 0x7fffed38 R21 0x7fffeba8 R22 0x00000000 R23 0x7fbaf584
May 27 01:03:59 (none) Scheduler[158]: R24 0x00000001 R25 0x7fbab41c R26 0x00030021 R27 0x00000000
May 27 01:03:59 (none) Scheduler[158]: R28 0x7fb40020 R29 0x7fbb48ec R30 0x00000014 R31 0x7fbb48d8
May 27 01:03:59 (none) Scheduler[158]: Tmk Thread Backtrace: 1a344fc 7fffe9e8 1b9645c 1b95fd4 19a0530 19a0378 1b347dc 1b335ac 1b342dc 1b3367c 1b1d990 1b1d70c 1af55a4 1af99fc 1c3acb8 1bdd718 1bde5c4 1bf42a8 1b5b5f8 1bdd1b0 1b91bb4 1c0644c 1c063bc 1c23c84 1c23df4 1c27364 1c28374 1c28420 1c27504 1c06298 1c06148 1bf71a4 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 ipe
May 27 01:03:59 (none) Scheduler[158]: Tmk Fatal Error: Thread died due to signal 11
May 27 01:03:59 (none) Scheduler[158]: Invoking rule 834: rebooting system
May 27 03:06:52 (none) Scheduler[158]: Tmk Fatal Error: Thread Scheduler <158> died due to signal 11
May 27 03:06:52 (none) Scheduler[158]: NIP 0x1b96220 link 0x1b96554 ctr 28957736
May 27 03:06:52 (none) Scheduler[158]: R00 0x00000014 R01 0x7fffe980 R02 0x00000100 R03 0x7fb40020
May 27 03:06:52 (none) Scheduler[158]: R04 0x00000011 R05 0x7fb9f27c R06 0x00000000 R07 0x00000000
May 27 03:06:52 (none) Scheduler[158]: R08 0x80808080 R09 0x00000003 R10 0x00000001 R11 0x7fb40020
May 27 03:06:52 (none) Scheduler[158]: R12 0x44200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 03:06:52 (none) Scheduler[158]: R16 0x018bdd4c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 03:06:52 (none) Scheduler[158]: R20 0x7fffebe8 R21 0x7fffea58 R22 0x00000000 R23 0x7fb77aa0
May 27 03:06:52 (none) Scheduler[158]: R24 0x00000001 R25 0x7fb78cb0 R26 0x00030021 R27 0x00000000
May 27 03:06:52 (none) Scheduler[158]: R28 0x7fb40020 R29 0x7fb9f27c R30 0x00000014 R31 0x7fb9f268
May 27 03:06:52 (none) Scheduler[158]: Tmk Thread Backtrace: 1a344fc 7fffe898 1b9645c 1b95fd4 19a0530 19a0378 1b347dc 1b335ac 1b342dc 1b3367c 1b1d990 1b1d70c 1af55a4 1af898c 1c3ac30 1bdd718 1bde5c4 1bf42a8 1b5b5f8 1bdd1b0 1b91bb4 1c0644c 1c063bc 1c23c84 1c23df4 1c27364 1c28374 1c28420 1c27504 1c06298 1c06148 1bf71a4 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 ipe
May 27 03:06:52 (none) Scheduler[158]: Tmk Fatal Error: Thread died due to signal 11
May 27 03:06:52 (none) Scheduler[158]: Invoking rule 834: rebooting system
May 27 03:15:34 (none) Scheduler[158]: Tmk Fatal Error: Thread Scheduler <158> died due to signal 11
May 27 03:15:34 (none) Scheduler[158]: NIP 0x1b96220 link 0x1b96554 ctr 28957736
May 27 03:15:34 (none) Scheduler[158]: R00 0x00000000 R01 0x7fffead0 R02 0x00000100 R03 0x7fb40020
May 27 03:15:34 (none) Scheduler[158]: R04 0x00000021 R05 0x7fbeba20 R06 0x00000000 R07 0x00000000
May 27 03:15:34 (none) Scheduler[158]: R08 0x80808080 R09 0x00000003 R10 0x00000001 R11 0x7fb40020
May 27 03:15:34 (none) Scheduler[158]: R12 0x44200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 03:15:34 (none) Scheduler[158]: R16 0x018bdd4c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 03:15:34 (none) Scheduler[158]: R20 0x7fffed38 R21 0x7fffeba8 R22 0x00000000 R23 0x7fb90444
May 27 03:15:34 (none) Scheduler[158]: R24 0x00000001 R25 0x7fbd4618 R26 0x00030021 R27 0x00000000
May 27 03:15:34 (none) Scheduler[158]: R28 0x7fb40020 R29 0x7fbeba20 R30 0x00000014 R31 0x7fbeba0c
May 27 03:15:34 (none) Scheduler[158]: Tmk Thread Backtrace: 1a344fc 7fffe9e8 1b9645c 1b95fd4 19a0530 19a0378 1b347dc 1b335ac 1b342dc 1b3367c 1b1d990 1b1d70c 1af55a4 1af99fc 1c3acb8 1bdd718 1bde5c4 1bf42a8 1b5b5f8 1bdd1b0 1b91bb4 1c0644c 1c063bc 1c23c84 1c23df4 1c27364 1c28374 1c28420 1c27504 1c06298 1c06148 1bf71a4 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 ipe
May 27 03:15:34 (none) Scheduler[158]: Tmk Fatal Error: Thread died due to signal 11
May 27 03:15:34 (none) Scheduler[158]: Invoking rule 834: rebooting system
May 27 03:36:59 (none) TmkAssertionFailure[158]: (AssertValidPointer, line 2021 ())
May 27 03:36:59 (none) Scheduler[158]: Tmk Fatal Error: Thread Scheduler <158> died due to signal -2
May 27 03:36:59 (none) Scheduler[158]: Tmk Thread Backtrace: 1a344ec 1a32a44 1b96114 1b9645c 1b95fd4 1b9b2f0 1b96d20 1b49078 1aa4508 1b96d20 1b3c9f4 1b3d0dc 1b3de98 1b3dafc 1b3d460 1b3d240 1b4d608 1b495b8 1b171a8 1b16f98 1af55a4 1af898c 1af9404 1bdd77c 1bde5c4 1bf42a8 1b5b5f8 1bdd1b0 1b91bb4 1c0644c 1c063bc 1c23c84 1c23df4 1c27364 1c28374 1c28420 1c27504 1c06298 1c06148 1bf71a4 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 ipe
May 27 03:36:59 (none) Scheduler[158]: Tmk Fatal Error: Thread died due to signal -2
May 27 03:36:59 (none) Scheduler[158]: Invoking rule 834: rebooting system


Automan.
Automan
TiVo lover
TiVo lover
 
Posts: 92
Joined: Tue May 17, 2011 9:06 am
Location: South Coast, Sussex, UK

Re: Alpha Tester - Getting hideous reboots

Postby groovyclam » Fri May 27, 2011 8:06 am

My guided setup I chose "SKY + RF"

This is the output from the count script - it ran with NO errors at 9am this morning:

Examined 23000 records
Table - 1
SwModule - 9
StationDay - 1940
Headend - 6
SoundFile - 18
Image - 264
IrBlastData - 176
IrFormat - 190
ResourceGroup - 49
LogoGroup - 2
LoopSet - 12
IrTivoFormat - 86
PostalCode - 2
Font - 2
Program - 14221
Genre - 208
Station - 706
Component - 900
Series - 3730
ComponentCode - 577
DataSet - 31
SwSystem - 1
VideoClip - 74
Total - 23205


The TiVo had feaked out many times throughout the night ( from kernel log):

May 26 22:31:30 (none) kernel: Tmk Fatal Error: Thread Prioritizer <148> died due to signal 11
May 26 22:31:30 (none) kernel: NIP 0x1b3c354 link 0x1b3d250 ctr 28875344
May 26 22:31:30 (none) kernel: R00 0x01b3d250 R01 0x7fffef30 R02 0x00000100 R03 0x7fbc3208
May 26 22:31:30 (none) kernel: R04 0x000000fe R05 0x00000001 R06 0x00000000 R07 0x7ffff0f8
May 26 22:31:30 (none) kernel: R08 0x00000000 R09 0x6c6c2900 R10 0x000001a9 R11 0x7fecd000
May 26 22:31:30 (none) kernel: R12 0x35d97800 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 26 22:31:30 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 26 22:31:30 (none) kernel: R20 0x01840000 R21 0x018d250c R22 0x00000000 R23 0x7ffff0f8
May 26 22:31:30 (none) kernel: R24 0x7ffff078 R25 0x003c99dd R26 0x00000000 R27 0x00000000
May 26 22:31:30 (none) kernel: R28 0x7ffff0f8 R29 0x7fffefd8 R30 0x7ffff0f8 R31 0x00000000

reboot...

May 26 22:36:40 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 26 22:36:40 (none) kernel: NIP 0x1b9638c link 0x1b96338 ctr 27618392
May 26 22:36:40 (none) kernel: R00 0x006e7548 R01 0x7fffeb40 R02 0x00000100 R03 0x7fb40020
May 26 22:36:40 (none) kernel: R04 0x7fbf9fb0 R05 0x7fbf9f8c R06 0x00000000 R07 0x00000080
May 26 22:36:40 (none) kernel: R08 0x80808080 R09 0x802e14f8 R10 0x00000000 R11 0x006e7548
May 26 22:36:40 (none) kernel: R12 0x44200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 26 22:36:40 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 26 22:36:40 (none) kernel: R20 0x7fffeddc R21 0x7fffec48 R22 0x00000000 R23 0x00000000
May 26 22:36:40 (none) kernel: R24 0x7fffed68 R25 0x00000000 R26 0x7fffecb8 R27 0x00000002
May 26 22:36:40 (none) kernel: R28 0x00000003 R29 0x00000024 R30 0x7fb40020 R31 0x7fbf9f8c

reboot...

May 27 00:05:17 (none) kernel: Tmk Assertion Failure:
May 27 00:05:17 (none) kernel: AssertValidPointer, line 2022 ()
May 27 00:05:17 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal -2

reboot...

May 27 01:11:23 (none) kernel: Tmk Assertion Failure:
May 27 01:11:23 (none) kernel: AssertValidPointer, line 2021 ()
May 27 01:11:23 (none) kernel: Tmk Fatal Error: Thread Prioritizer <145> died due to signal -2

rebooot...

May 27 01:25:00 (none) kernel: mediaswitch: returning 0 from standin tune after tuning to ch -3 with adjust 0
May 27 01:25:04 (none) kernel: Done with this packet
May 27 01:25:24 (none) kernel: Tmk Assertion Failure:
May 27 01:25:24 (none) kernel: AssertValidPointer, line 2021 ()
May 27 01:25:24 (none) kernel: Tmk Fatal Error: Thread Prioritizer <148> died due to signal -2

reboot...

May 27 01:30:45 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 01:30:45 (none) kernel: NIP 0x1b9638c link 0x1b96338 ctr 28875344
May 27 01:30:45 (none) kernel: R00 0x006c28d0 R01 0x7fffeab0 R02 0x00000100 R03 0x7fb40020
May 27 01:30:45 (none) kernel: R04 0x7fbf9728 R05 0x7fbf96f8 R06 0x00000000 R07 0x00000000
May 27 01:30:45 (none) kernel: R08 0x00000000 R09 0x802bbff8 R10 0x00000000 R11 0x006c28d0
May 27 01:30:45 (none) kernel: R12 0x42200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 01:30:45 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 01:30:45 (none) kernel: R20 0x7fffeddc R21 0x7fffec48 R22 0x00000000 R23 0x00000000
May 27 01:30:45 (none) kernel: R24 0x7fffed68 R25 0x7fb40020 R26 0x01d30000 R27 0x7febca08
May 27 01:30:45 (none) kernel: R28 0x00000001 R29 0x00000030 R30 0x7fb40020 R31 0x7fbf96f8

reboot...

May 27 01:35:51 (none) kernel: Tmk Assertion Failure:
May 27 01:35:51 (none) kernel: AssertValidPointer, line 2021 ()
May 27 01:35:51 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal -2

reboot...

May 27 01:41:13 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 01:41:13 (none) kernel: NIP 0x1b96c78 link 0x1b9479c ctr 27618524
May 27 01:41:13 (none) kernel: R00 0xadbeefe2 R01 0x7fffeef0 R02 0x00000100 R03 0xadbeefde
May 27 01:41:13 (none) kernel: R04 0x7fba92c4 R05 0x00000000 R06 0x00000000 R07 0x7fffef68
May 27 01:41:13 (none) kernel: R08 0x7fffef68 R09 0x00000000 R10 0xfffffff9 R11 0x7fb624fc
May 27 01:41:13 (none) kernel: R12 0xd640fa00 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 01:41:13 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 01:41:13 (none) kernel: R20 0x01840000 R21 0x018d250c R22 0x7ffff1a8 R23 0x00000000
May 27 01:41:13 (none) kernel: R24 0x7ffff098 R25 0x00000001 R26 0x7fba8da4 R27 0x00000000
May 27 01:41:13 (none) kernel: R28 0x00000000 R29 0x7fffef38 R30 0x7fba92c4 R31 0x00000000

reboot...

May 27 01:46:37 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 01:46:37 (none) kernel: NIP 0x1b1dc94 link 0x1b1dc8c ctr 28873300
May 27 01:46:37 (none) kernel: R00 0x01b1dc8c R01 0x7fffed90 R02 0x00000100 R03 0x7fb4ba18
May 27 01:46:37 (none) kernel: Tmk Fatal Error: Thread Mediaswitch0 <143> died due to signal 11
May 27 01:46:37 (none) kernel: NIP 0x1b96194 link 0x1b9a638 ctr 27618432
May 27 01:46:37 (none) kernel: R00 0x01b73528 R01 0x7fffae60 R02 0x00000100 R03 0xadbeefde
May 27 01:46:37 (none) kernel: R04 0x7fffaea8 R05 0x00000000 R06 0x00000000 R07 0x00000950
May 27 01:46:37 (none) kernel: R08 0x00000000 R09 0x3000f3a8 R10 0x00002ff0 R11 0x00000004
May 27 01:46:37 (none) kernel: R12 0xf08b1b50 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 01:46:37 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xfffffffb
May 27 01:46:37 (none) kernel: R20 0x7fffafc8 R21 0x7fffafd8 R22 0x00002f50 R23 0x00000001
May 27 01:46:37 (none) kernel: R24 0x00002ff0 R25 0x00000000 R26 0x3000f1b4 R27 0x00002fe0
May 27 01:46:37 (none) kernel: R28 0x7fffaea8 R29 0x7fb4c0b0 R30 0x3000f1b4 R31 0x30006008
May 27 01:46:37 (none) kernel: 1a344fc 7fffad78 1b73d44 1b73528 1b6c920 1b62648 1b61ff8 1c1cf84 1c1d1fc 1c23c84 1c23df4 1c27364 1c28374 1c28420 1c27504 1c1c4c4 1c10004 1c0fd2c 1c0e1a8 1c06ea0 1bf7094 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 R04 0x7fb40b78 R05 0x00000002 R06 0x00000001 R07 0x7fffedd0
May 27 01:46:37 (none) kernel: R08 0xdeadbeef R09 0xadbeefde R10 0x80458f40 R11 0x7fffee00
May 27 01:46:37 (none) kernel: R12 0x24200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 01:46:37 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 01:46:37 (none) kernel: R20 0xffffffff R21 0x00000000 R22 0x7fb61f8c R23 0x00000001
May 27 01:46:37 (none) kernel: R24 0x7fffef48 R25 0x7fffee48 R26 0x7fffee68 R27 0x7fffee38
May 27 01:46:37 (none) kernel: R28 0x7fb61f60 R29 0x00000000 R30 0x00000000 R31 0x7fb61f60
May 27 01:46:37 (none) kernel: 1a344fc 7fffeca8 1b1dc8c 1b1dc04 1b1d70c 1af55a4 1af898c 1c3ac30 1bdd718 1bde5c4 1bf42a8 1b5b5f8 1bdd1b0 1b91bb4 1c0644c 1c063bc 1c23c84 1c23df4 1c27364 1c28374 1c28420 1c27504 1c06298 1c06148 1bf71a4 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 Tmk Fatal Error: Thread UI Timer Heartbeat <136> died due to signal 11
May 27 01:46:37 (none) kernel: NIP 0x1b9118c link 0x1b91164 ctr 28908140
May 27 01:46:37 (none) kernel: R00 0xadbeefde R01 0x7ffff3a0 R02 0x00000100 R03 0x00000000
May 27 01:46:37 (none) kernel: R04 0x00000000 R05 0x00000001 R06 0x00000000 R07 0x7ffff418
May 27 01:46:37 (none) kernel: R08 0x00000000 R09 0xadbeefde R10 0x01db22f0 R11 0x00000001
May 27 01:46:37 (none) kernel: R12 0x4628a200 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 01:46:37 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 01:46:37 (none) kernel: R20 0x01840000 R21 0x7fb4b0cc R22 0x7ffff3b8 R23 0x00000000
May 27 01:46:37 (none) kernel: R24 0x00000000 R25 0x7fb41038 R26 0x00000000 R27 0x7fb41028
May 27 01:46:37 (none) kernel: R28 0x01daa5e0 R29 0x7fb4b0cc R30 0x7ffff3c8 R31 0x7ffff438
May 27 01:46:37 (none) kernel: 1a344fc 7ffff2b8 1b91164 1c0d2ec 1c0d26c 1c23c84 1c23df4 1c27364 1c28374 1c28420 1c27504 1c0d1f4 1bf706c 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 Tmk Fatal Error: Thread Prioritizer <148> died due to signal 11
May 27 01:46:37 (none) kernel: NIP 0x1b96edc link 0x1b96ec4 ctr 28908140
May 27 01:46:37 (none) kernel: R00 0xadbeefde R01 0x7ffff270 R02 0x00000100 R03 0xadbeefde
May 27 01:46:37 (none) kernel: R04 0x00000008 R05 0x00000001 R06 0x00000000 R07 0xfa000000
May 27 01:46:37 (none) kernel: R08 0x7ffff268 R09 0x00000000 R10 0x00000000 R11 0x7ffff3e0
May 27 01:46:37 (none) kernel: R12 0x7fec71b0 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 01:46:37 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 01:46:37 (none) kernel: R20 0x01840000 R21 0x018d250c R22 0x0000001e R23 0x6cb79e91
May 27 01:46:37 (none) kernel: R24 0x01cf0000 R25 0x7fb4f0c0 R26 0x7ffff2e8 R27 0x7fb41038
May 27 01:46:37 (none) kernel: R28 0x7ffff2f8 R29 0x7ffff2fc R30 0x00000008 R31 0x7fb4067c
May 27 01:46:42 (none)
May 27 01:46:42 (none) kernel: ^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^->o^C (null) <-1379995682> died due to signal 11
May 27 01:46:42 (none) kernel: NIP 0x1b956fc link 0x1b956e8 ctr 27618392
May 27 01:46:42 (none) kernel: R00 0x01b956e8 R01 0x7ffff0e0 R02 0x00000100 R03 0xadbeefdf
May 27 01:46:42 (none) kernel: R04 0x0000008a R05 0x00000001 R06 0xadbeefde R07 0x7ffff128
May 27 01:46:42 (none) kernel: R08 0x00000000 R09 0x7fb4c334 R10 0x00000000 R11 0x00000000
May 27 01:46:42 (none) kernel: R12 0x00000000 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 01:46:42 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 01:46:42 (none) kernel: R20 0x01840000 R21 0x00000000 R22 0x01d9d370 R23 0x7ffff598
May 27 01:46:42 (none) kernel: R24 0x7ffff578 R25 0x7ffff498 R26 0x7ffff458 R27 0x01da0000
May 27 01:46:42 (none) kernel: R28 0x00000000 R29 0x0000008a R30 0x7fb4c324 R31 0xadbeefde

reboot...

May 27 01:51:58 (none) kernel: Tmk Assertion Failure:
May 27 01:51:58 (none) kernel: AssertValidPointer, line 2021 ()
May 27 01:51:58 (none) kernel: Tmk Fatal Error: Thread Scheduler <144> died due to signal -2

reboot...

May 27 01:57:23 (none) kernel: Tmk Assertion Failure:
May 27 01:57:23 (none) kernel: AssertValidPointer, line 2021 ()
May 27 01:57:23 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal -2

reboot...

May 27 02:02:48 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 02:02:48 (none) kernel: NIP 0x1b96220 link 0x1b96338 ctr 28873300
May 27 02:02:48 (none) kernel: R00 0x00beefde R01 0x7fffeb90 R02 0x00000100 R03 0x7fb40020
May 27 02:02:48 (none) kernel: R04 0x00000023 R05 0x7fbfa3ec R06 0x00000000 R07 0x00000000
May 27 02:02:48 (none) kernel: R08 0xdeadbeef R09 0x7fb40100 R10 0xadbeefde R11 0xadbeefde
May 27 02:02:48 (none) kernel: R12 0x44200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 02:02:48 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 02:02:48 (none) kernel: R20 0x7fffeddc R21 0x7fffec48 R22 0x00000000 R23 0x00000000
May 27 02:02:48 (none) kernel: R24 0x7fffed68 R25 0x00000000 R26 0x7fffecb8 R27 0x00000002
May 27 02:02:48 (none) kernel: R28 0x00000001 R29 0x00000040 R30 0x7fb40020 R31 0x7fbfa3ec

reboot...

May 27 04:25:12 (none) kernel: Tmk Assertion Failure:
May 27 04:25:12 (none) kernel: AssertValidPointer, line 2021 ()
May 27 04:25:12 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal -2

reboot...

May 27 04:30:45 (none) kernel: Tmk Assertion Failure:
May 27 04:30:45 (none) kernel: AssertValidPointer, line 2021 ()
May 27 04:30:45 (none) kernel: Tmk Fatal Error: Thread Prioritizer <145> died due to signal -2

reboot...

May 27 04:36:07 (none) kernel: Tmk Fatal Error: Thread ContextMgr event handler <149> died due to signal 11
May 27 04:36:07 (none) kernel: NIP 0x1b96220 link 0x1b96338 ctr 28067208
May 27 04:36:07 (none) kernel: R00 0x00beefde R01 0x7ffff040 R02 0x00000100 R03 0x7fb40020
May 27 04:36:07 (none) kernel: R04 0x00000024 R05 0x7fbf8d60 R06 0x00000000 R07 0x00000000
May 27 04:36:07 (none) kernel: R08 0x00000000 R09 0x7fb40100 R10 0xadbeefde R11 0xadbeefde
May 27 04:36:07 (none) kernel: R12 0xe8d4a510 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 04:36:07 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 04:36:07 (none) kernel: R20 0x01840000 R21 0x018d250c R22 0x00000000 R23 0x7fb44f68
May 27 04:36:07 (none) kernel: R24 0x7fb44d18 R25 0x01cd8034 R26 0x00000000 R27 0x00000001
May 27 04:36:07 (none) kernel: R28 0x00000001 R29 0x00000070 R30 0x7fb40020 R31 0x7fbf8d60
May 27 04:36:07 (none) kernel: 1a344fc 7fffef58 0 1b95dcc 1b96b2c 1b4205c 1b3069c 1b21c6c 1b23ef4 1ac45ec 1b91bb4 1c01e6c 1c249b8 1c23c84 1c23db0 1c27364 1c28374 1c28420 1c27504 1c23eb4 1c248fc 1c01ca8 1bf73bc 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 04:36:07 (none) kernel: NIP 0x1b41720 link 0x1b416fc ctr 28957736
May 27 04:36:07 (none) kernel: R00 0x7fbf88e4 R01 0x7fffeb80 R02 0x00000100 R03 0x7fbf88e0
May 27 04:36:07 (none) kernel: R04 0x00000002 R05 0xadbeefdf R06 0xadbeefdd R07 0x000000ad
May 27 04:36:07 (none) kernel: R08 0x80808080 R09 0xadbeefde R10 0x7fbf88e0 R11 0x7fbf87cc
May 27 04:36:07 (none) kernel: R12 0x24200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 04:36:07 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 04:36:07 (none) kernel: R20 0x7fffeddc R21 0x7fffec48 R22 0x00000000 R23 0x00000000
May 27 04:36:07 (none) kernel: R24 0x7fffed68 R25 0x00000000 R26 0x7fffecb8 R27 0x00000001
May 27 04:36:07 (none) kernel: R28 0x7fbf8744 R29 0x00000000 R30 0x0003001e R31 0x7fffec98

reboot...

May 27 04:41:27 (none) kernel: Tmk Assertion Failure:
May 27 04:41:27 (none) kernel: AssertValidPointer, line 2021 ()
May 27 04:41:28 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal -2

reboot...

May 27 04:47:04 (none) kernel: Tmk Assertion Failure:
May 27 04:47:04 (none) kernel: AssertValidPointer, line 2021 ()
May 27 04:47:04 (none) kernel: Tmk Fatal Error: Thread Prioritizer <148> died due to signal -2

reboot...

May 27 04:52:25 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 04:52:25 (none) kernel: NIP 0x1b41720 link 0x1b416fc ctr 28957736
May 27 04:52:25 (none) kernel: R00 0x7fbf95e0 R01 0x7fffeb80 R02 0x00000100 R03 0x7fbf95dc
May 27 04:52:25 (none) kernel: R04 0x00000002 R05 0xadbeefdf R06 0x00000000 R07 0x00000000
May 27 04:52:25 (none) kernel: R08 0xdeadbeef R09 0xadbeefde R10 0x7fbf95dc R11 0x00000d44
May 27 04:52:25 (none) kernel: R12 0x24200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 04:52:25 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 04:52:25 (none) kernel: R20 0x7fffeddc R21 0x7fffec48 R22 0x00000000 R23 0x00000000
May 27 04:52:25 (none) kernel: R24 0x7fffed68 R25 0x00000000 R26 0x7fffecb8 R27 0x00000001
May 27 04:52:25 (none) kernel: R28 0x7fbf9040 R29 0x00000000 R30 0x0003001e R31 0x7fffec98
May 27 04:52:25 (none) kernel: 1a344fc 7fffea98 1b96bfc 1b423b4 1b3483c 1b33934 1b1d990 1b1d70c 1af55a4 1af898c 1c3ac30 1bdd718 1bde5c4 1bf42a8 1b5b5f8 1bdd1b0 1b91bb4 1c0644c 1c063bc 1c23c84 1c23df4 1c27364 1c28374 1c28420 1c27504 1c06298 1c06148 1bf71a4 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 Tmk Fatal Error: Thread TvRecorder <145> died due to signal 11
May 27 04:52:25 (none) kernel: NIP 0x1a55ac4 link 0x1a48738 ctr 27559480
May 27 04:52:25 (none) kernel: R00 0x00000001 R01 0x7fffe780 R02 0x00000100 R03 0xadbeefde
May 27 04:52:25 (none) kernel: R04 0x01d48b24 R05 0x0000000f R06 0x00000000 R07 0x00000002
May 27 04:52:25 (none) kernel: R08 0x80808080 R09 0x00000001 R10 0x00000004 R11 0xadbeefde
May 27 04:52:25 (none) kernel: R12 0x00000000 R13 0x01da9208 R14 0xffffffff R15 0x00000073
May 27 04:52:25 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0x00000000 R19 0x00000001
May 27 04:52:25 (none) kernel: R20 0x00000000 R21 0x018d250c R22 0x00000000 R23 0x00000001
May 27 04:52:25 (none) kernel: R24 0x00000000 R25 0x7fffed28 R26 0x0000000f R27 0x7fffebe8
May 27 04:52:25 (none) kernel: R28 0x7ffff090 R29 0x0000000f R30 0xadbeefde R31 0x7fffe780

reboot...

May 27 04:57:45 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 04:57:45 (none) kernel: NIP 0x1b96220 link 0x1b96338 ctr 28873300
May 27 04:57:45 (none) kernel: R00 0x00beefde R01 0x7fffeb70 R02 0x00000100 R03 0x7fb40020
May 27 04:57:45 (none) kernel: R04 0x00000023 R05 0x7fbfadf4 R06 0x00000000 R07 0xee6b2800
May 27 04:57:45 (none) kernel: R08 0x00002f49 R09 0x7fb40100 R10 0xadbeefde R11 0xadbeefde
May 27 04:57:45 (none) kernel: R12 0x60399a00 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 04:57:45 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 04:57:45 (none) kernel: R20 0x7fffeddc R21 0x7fffec48 R22 0x00000000 R23 0x00000000
May 27 04:57:45 (none) kernel: R24 0x7fffed68 R25 0x00000000 R26 0x7fffecb8 R27 0x003c9adc
May 27 04:57:45 (none) kernel: R28 0x00000001 R29 0x00000064 R30 0x7fb40020 R31 0x7fbfadf4

reboot...

May 27 05:02:59 (none) kernel: Filesystem assert: false at tmtrans.C line 723 in int TmTransaction::ReadyForActivation()
May 27 05:03:00 (none) kernel: Filesystem flagged as inconsistent!
May 27 05:03:02 (none) kernel: Tmk Assertion Failure: false
May 27 05:03:02 (none) kernel: int TmTransaction::ReadyForActivation(), line 723 (tmtrans.C)
May 27 05:03:03 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal -2

reboot...


At this point the logs show the tivo going through an fsck because it wasn't happy with the filesystem.

Partway through the fsck it reboots again!!!

May 27 05:11:14 (none) kernel: FIXING: file 1377 refcount (changing from 4 to 2) object reasonable
May 27 05:11:14 (none) kernel: FIXING: file 1378 refcount (changing from 8 to 2) object reasonable
May 27 05:11:14 (none) kernel: FIXING: file 1379 refcount (changing from 5 to 2) object reasonable
May 27 05:11:14 (none) kernel: FIXING: file 1380 refcount (changing from 4 to 2) object reasonable
May 27 05:11:14 (none) kernel: FIXING: file 1381 refcount (changing from 4 to 2) object reasonable
May 27 05:11:14 (none) kernel: FIXING: file 1382 refcount (changing from 11 to 2) object reasonable
May 27 05:11:14 (none) kernel: FIXING: file 1383 refcount (changing from 11 to 2) object reasonable
May 27 05:11:14 (none) kernel: FIXING: file 1384 refcount (changing from 7 to 2) object reasonable
May 27 05:11:14 (none) kernel: FIXING: file 1385 refcount (changing from 6 1b95fd4 1b9b2dc 1b96d20 1acec84 1ace170 1abb718 1839cc0 1abcc80 1ac4bb8 1b91bb4 1c01e84 1c249b8 1c23c84 1c23db0 1c27364 1c28374 1c28420 1c27504 1c23eb4 1c248fc 1c01ca8 1bf73bc 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 ipe
May 25 21:35:08 (none) ContextMgr event handler[149]: Tmk Fatal Error: Thread died due to signal -2
May 25 21:35:08 (none) ContextMgr event handler[149]: Invoking rule 834: rebooting system

reboot...

May 27 05:16:24 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 05:16:24 (none) kernel: NIP 0x1b96220 link 0x1b96338 ctr 28957736
May 27 05:16:24 (none) kernel: R00 0x00beefde R01 0x7fffecc0 R02 0x00000100 R03 0x7fb40020
May 27 05:16:24 (none) kernel: R04 0x00000007 R05 0x7fb6445c R06 0x00000000 R07 0x80808080
May 27 05:16:24 (none) kernel: R08 0x80808080 R09 0x7fb40100 R10 0xadbeefde R11 0x00000000
May 27 05:16:24 (none) kernel: R12 0x42200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 05:16:24 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 05:16:24 (none) kernel: R20 0x7fffef2c R21 0x7fffed98 R22 0x00000000 R23 0x7fb63d04
May 27 05:16:24 (none) kernel: R24 0x00000007 R25 0x7fb61418 R26 0x0003001f R27 0x00000000
May 27 05:16:24 (none) kernel: R28 0x00000009 R29 0x00000018 R30 0x7fb40020 R31 0x7fb6445c

reboot...

May 27 05:21:36 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 05:21:36 (none) kernel: NIP 0x1b41720 link 0x1b416fc ctr 28957736
May 27 05:21:36 (none) kernel: R00 0x7fbfa7f8 R01 0x7fffeb80 R02 0x00000100 R03 0x7fbfa7f4
May 27 05:21:36 (none) kernel: R04 0x00000002 R05 0xadbeefdf R06 0x00000000 R07 0x00000000
May 27 05:21:36 (none) kernel: R08 0xdeadbeef R09 0xadbeefde R10 0x7fbfa7f4 R11 0x00000bb0
May 27 05:21:36 (none) kernel: R12 0x24200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 05:21:36 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 05:21:36 (none) kernel: R20 0x7fffeddc R21 0x7fffec48 R22 0x00000000 R23 0x00000000
May 27 05:21:36 (none) kernel: R24 0x7fffed68 R25 0x00000000 R26 0x7fffecb8 R27 0x00000001
May 27 05:21:36 (none) kernel: R28 0x7fbfa350 R29 0x00000000 R30 0x0003001e R31 0x7fffec98
May 27 05:21:40 (none) kernel: 1a344fc 7fffea98 1b96bfc 1b423b4 1b3483c 1b33934 1b1d990 1b1d70c 1af55a4 1af898c 1c3ac30 1bdd718 1bde5c4 1bf42a8 1b5b5f8 1bdd1b0 1b91bb4 1c0644c 1c063bc 1c23c84 1c23df4 1c27364 1c28374 1c28420 1c27504 1c06298 1c06148 1bf71a4 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 Tmk Fatal Error: Thread TvRecorder <145> died due to signal 11
May 27 05:21:40 (none) kernel: NIP 0x1b96220 link 0x1b96338 ctr 27618524
May 27 05:21:40 (none) kernel: R00 0x00beefde R01 0x7fffee50 R02 0x00000100 R03 0x7fb40020
May 27 05:21:40 (none) kernel: R04 0x00000006 R05 0x7fbfa740 R06 0x00000000 R07 0x00008000
May 27 05:21:40 (none) kernel: R08 0x80808080 R09 0x7fb40100 R10 0xadbeefde R11 0x00000000
May 27 05:21:40 (none) kernel: R12 0x22200082 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 05:21:40 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 05:21:40 (none) kernel: R20 0x01840000 R21 0x018d250c R22 0x00000000 R23 0x00000001
May 27 05:21:40 (none) kernel: R24 0x00000001 R25 0x01ce5b8c R26 0x00000000 R27 0x7fffef58
May 27 05:21:40 (none) kernel: R28 0x00000003 R29 0x00000018 R30 0x7fb40020 R31 0x7fbfa740

reboot...

May 27 05:26:49 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 05:26:49 (none) kernel: NIP 0x1b9638c link 0x1b96338 ctr 28875344
May 27 05:26:49 (none) kernel: R00 0x006e753c R01 0x7fffeab0 R02 0x00000100 R03 0x7fb40020
May 27 05:26:49 (none) kernel: R04 0x7fbaae20 R05 0x7fbaadf0 R06 0x00000000 R07 0x00000000
May 27 05:26:49 (none) kernel: R08 0x00000000 R09 0x8029235c R10 0x00000000 R11 0x006e753c
May 27 05:26:49 (none) kernel: R12 0x42200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 05:26:49 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 05:26:49 (none) kernel: R20 0x7fffeddc R21 0x7fffec48 R22 0x00000000 R23 0x00000000
May 27 05:26:49 (none) kernel: R24 0x7fffed68 R25 0x7fb40020 R26 0x01d30000 R27 0x7febca08
May 27 05:26:49 (none) kernel: R28 0x00000001 R29 0x00000030 R30 0x7fb40020 R31 0x7fbaadf0

reboot...

May 27 05:32:14 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 05:32:14 (none) kernel: NIP 0x1b41720 link 0x1b416fc ctr 28957736
May 27 05:32:14 (none) kernel: R00 0x7fbfa150 R01 0x7fffeb80 R02 0x00000100 R03 0x7fbfa14c
May 27 05:32:14 (none) kernel: R04 0x00000002 R05 0xadbeefdf R06 0x00000000 R07 0x00000003
May 27 05:32:14 (none) kernel: R08 0x80808080 R09 0xadbeefde R10 0x7fbfa14c R11 0x7fbfa9dc
May 27 05:32:14 (none) kernel: R12 0x44200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 05:32:14 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 05:32:14 (none) kernel: R20 0x7fffeddc R21 0x7fffec48 R22 0x00000000 R23 0x00000000
May 27 05:32:14 (none) kernel: R24 0x7fffed68 R25 0x00000000 R26 0x7fffecb8 R27 0x00000001
May 27 05:32:14 (none) kernel: R28 0x7fbaaaa0 R29 0x00000000 R30 0x0003001e R31 0x7fffec98

reboot...

May 27 05:37:26 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 05:37:26 (none) kernel: NIP 0x1b96220 link 0x1b96338 ctr 28873300
May 27 05:37:26 (none) kernel: R00 0x00beefde R01 0x7fffeb90 R02 0x00000100 R03 0x7fb40020
May 27 05:37:26 (none) kernel: R04 0x00000027 R05 0x7fbfc6a0 R06 0x00000000 R07 0x00000000
May 27 05:37:26 (none) kernel: R08 0xdeadbeef R09 0x7fb40100 R10 0xadbeefde R11 0xadbeefde
May 27 05:37:26 (none) kernel: R12 0x24200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 05:37:26 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 05:37:26 (none) kernel: R20 0x7fffeddc R21 0x7fffec48 R22 0x00000000 R23 0x00000000
May 27 05:37:26 (none) kernel: R24 0x7fffed68 R25 0x00000000 R26 0x7fffecb8 R27 0x00000002
May 27 05:37:26 (none) kernel: R28 0x00000001 R29 0x00000040 R30 0x7fb40020 R31 0x7fbfc6a0

reboot...

May 27 07:41:13 (none) kernel: Tmk Fatal Error: Thread Scheduler <147> died due to signal 11
May 27 07:41:13 (none) kernel: NIP 0x1b9638c link 0x1b96338 ctr 28875344
May 27 07:41:13 (none) kernel: R00 0x006e7558 R01 0x7fffeb40 R02 0x00000100 R03 0x7fb40020
May 27 07:41:13 (none) kernel: R04 0x7fb7c90c R05 0x7fb7c8f8 R06 0x00000000 R07 0x00008080
May 27 07:41:13 (none) kernel: R08 0x80808080 R09 0x80263e64 R10 0x00000000 R11 0x006e7558
May 27 07:41:13 (none) kernel: R12 0x42200022 R13 0x01da9208 R14 0x00000000 R15 0x00000000
May 27 07:41:13 (none) kernel: R16 0x018bdd8c R17 0x00000000 R18 0xffffffff R19 0xffffffff
May 27 07:41:13 (none) kernel: R20 0x7fffeddc R21 0x7fffec48 R22 0x00000000 R23 0x00000000
May 27 07:41:13 (none) kernel: R24 0x7fffed68 R25 0x00000000 R26 0x7fffecb8 R27 0x00000001
May 27 07:41:13 (none) kernel: R28 0x00000003 R29 0x00000014 R30 0x7fb40020 R31 0x7fb7c8f8


It's been up so far from that reboot however my kernel log is a bit screwed ( probably from the rebooting or fsck repair ) as I have this extract inbetween 05:11 and 05:15

KAJABOOHOO 1eb297
KAKADU 1f2feb
KAKWA 1ea3ec
KAL 1f3a96
KALAHAR 1f41ae
KALAHARI 1dbd14 1dc6f0 1e5357 1e9631
KALAKAAR 1e2693
KALAMAZOO 1e060b 1f22de
KALEIDOSCOPE 1eaa46
KALICHARAN 1e8fd3
KAM 1f08e0
KAMAAL 1f4558
KAMEHAMEHA 1e9518
KAMI 1cf6fc
KAMIKAZES 1f1745
KAMIKAZI 1dbdef 1dc76a
KAMISPAZI 1cf6fc
KAMP 1e3277
KANCHANABURI 1e858c
KANDY 1ea8d3
KANE 1e7045
KANGAROO 1e9f21 1f22be
KANGAROOS 1f30e3
KANHAIYA 1e3a83
KANSAS 1e38ce 1e3a9f 1e9e83
KANYE 1cff64 1df746 1f2d79 1f2f2d 1f30fb 1f3663 1f3714 7d145
KAPLINKSY 1c16bb 1ed5dc
KARA 1e9df9
KARACHI 1e97e4
KARAOKE 1d9d71 1ea1d3 1ebd88 1ed2a0
KARATE 1dbb0a 1ea152 1ec756
KARDASHIAN 1d666b 1ed662
KARDASHIANS 1d64ec 1d666b 1d9ace 1df8d4 1e28b0 1e3a09 1e43c9 1e56ff 1e64a4 1e71da 1e806a 1e8f2e 1e974b 1ed662 1ed663 1f1969 1f232a 1f2f20 1f3ae0 1f3ae1
KAREGA 1f369d
KAREN 1e54cb 1e9777 1e97d6
KARENGE 1e872b
KARL 1d5375 1e7f21 1e809b
KARLOFF 1d7f13
KARMA 1e63d1 1ed875 1f294e 1f36db
KARNI 1e57d1
KARO 1e712b
KAROL 1e4fcb
KAROT 1daa88
KARRIEREN 1e9534
KARTING 1e6e


Obviously some part of the database!

Because of this I am going to do a complete database cleardown and new guided setup.

I will choose "SKY + RF" but I am only going to choose a few channels that AltEPG has listings for and see how that goes on.
groovyclam
Almost there...
Almost there...
 
Posts: 47
Joined: Wed Feb 16, 2011 12:17 pm
Location: United Kingdom

Re: Alpha Tester - Getting hideous reboots

Postby groovyclam » Fri May 27, 2011 10:15 am

I have chosen the option to clear down the prog data and todo list.

I then chose to do guided setup and chose "Aerial + Digital Satellite"

I chose "Sky" ( not HD ) lineup but only chose channels I know AltEPG has data for.

It is now currently indexing for 4-8 hours and I will post the count script output again after it has finished that step.

I will be away for the weekend so can't report on reboots ( if any ) until Monday but I will not be putting any wishlists in, just season passes for channels with AltEPG data.

However I will have to set some manual records for EuroSport which I have not chosen in my lineup but I need to record for tennis at the moment.

If the TiVo survives the weekend without a reboot I personally would blame the problem on channels that AltEPG give in a lineup but put no programme records in, but let's wait and see.
groovyclam
Almost there...
Almost there...
 
Posts: 47
Joined: Wed Feb 16, 2011 12:17 pm
Location: United Kingdom

Re: Alpha Tester - Getting hideous reboots

Postby Automan » Fri May 27, 2011 11:09 am

I think my one is less than happy after so many reboots - Lost count of how many times I have seen the Tivo startup movie :)

I am doing a clear & delete everything and putting back on Tivo data for a bit.

Automan.
Automan
TiVo lover
TiVo lover
 
Posts: 92
Joined: Tue May 17, 2011 9:06 am
Location: South Coast, Sussex, UK

Re: Alpha Tester - Getting hideous reboots

Postby Automan » Fri May 27, 2011 1:03 pm

gcobb wrote:Automan, thanks.

I don't suppose anyone can run my script on a Tivo which is set up to use Satellite + RF with the normal Tivo service (and has never connected to the AltEPG)?


My box is up and running again on the Tribune EPG (delete and clear everything)

Running tivosh count-db.tcl generates the following...

Code: Select all
Visit TC.co.uk for upgrades and info !
Filesystem on / set to READONLY - type rw to make READ/WRITE
TiVo: {/var/hack} % tivosh count-db.tcl
Examined 500 records
Examined 1000 records
Examined 1500 records
Examined 2000 records
Examined 2500 records
Examined 3000 records
Examined 3500 records
Examined 4000 records
Examined 4500 records
Examined 5000 records
Examined 5500 records
Examined 6000 records
Examined 6500 records
Warning - could not open object 879695: can't open object (errDbNotFound)

Examined 7000 records
Warning - could not open object 879696: can't open object (errDbNotFound)

Examined 7500 records
Examined 8000 records
Examined 8500 records
Examined 9000 records
Examined 9500 records
Examined 10000 records
Examined 10500 records
Examined 11000 records
Examined 11500 records
Examined 12000 records
Examined 12500 records
Examined 13000 records
Examined 13500 records
Examined 14000 records
Examined 14500 records
Examined 15000 records
Examined 15500 records
Examined 16000 records
Examined 16500 records
Examined 17000 records
Examined 17500 records
Examined 18000 records
Examined 18500 records
Examined 19000 records
Examined 19500 records
Examined 20000 records
Examined 20500 records
Examined 21000 records
Examined 21500 records
Examined 22000 records
Examined 22500 records
Examined 23000 records
Examined 23500 records
Examined 24000 records
Examined 24500 records
Examined 25000 records
Examined 25500 records
Examined 26000 records
Examined 26500 records
Examined 27000 records
Examined 27500 records
Examined 28000 records
Examined 28500 records
Examined 29000 records
Examined 29500 records
Examined 30000 records
Examined 30500 records
Examined 31000 records
Examined 31500 records
Examined 32000 records
Examined 32500 records
Examined 33000 records
Examined 33500 records
Examined 34000 records
Examined 34500 records
Examined 35000 records
Examined 35500 records
Examined 36000 records
Examined 36500 records
Examined 37000 records
Examined 37500 records
Examined 38000 records
Examined 38500 records
Examined 39000 records
Examined 39500 records
Examined 40000 records
Examined 40500 records
Examined 41000 records
Examined 41500 records
Examined 42000 records
Examined 42500 records
Examined 43000 records
Examined 43500 records
Examined 44000 records
Examined 44500 records
Examined 45000 records
Examined 45500 records
Examined 46000 records
Examined 46500 records
Examined 47000 records
Examined 47500 records
Examined 48000 records
Examined 48500 records
Examined 49000 records
Examined 49500 records
Examined 50000 records
Examined 50500 records
Examined 51000 records
Examined 51500 records
Examined 52000 records
Examined 52500 records
Examined 53000 records
Examined 53500 records
Table - 1
SwModule - 9
StationDay - 12075
Headend - 15
SoundFile - 18
Image - 262
IrBlastData - 176
IrFormat - 190
ResourceGroup - 49
LoopSet - 12
PostalCode - 2
IrTivoFormat - 88
Font - 2
Program - 28765
Genre - 207
Station - 713
Series - 9378
Component - 901
ComponentCode - 581
DataSet - 8
SwSystem - 1
VideoClip - 74
Total - 53529
TiVo: {/var/hack} %
TiVo: {/var/hack} %


Automan.
Last edited by Automan on Fri May 27, 2011 1:20 pm, edited 1 time in total.
Automan
TiVo lover
TiVo lover
 
Posts: 92
Joined: Tue May 17, 2011 9:06 am
Location: South Coast, Sussex, UK

Re: Alpha Tester - Getting hideous reboots

Postby groovyclam » Fri May 27, 2011 1:17 pm

Here is my count output after a new guided setup to AltEPG -> RF + Digital Satellite -> SKY lineup -> only chose channels that AltEPG does listings for.

This time it ran with errors:

Examined 11500 records
Examined 12000 records
Examined 12500 records
Examined 13000 records
Examined 13500 records
Warning - could not open object 2545: can't open object (errTmBackgroundHoldoff)

retrying after errTmBackgroundHoldoff ...
Warning - could not open object 2545: can't open object (errTmBackgroundHoldoff)

retrying after errTmBackgroundHoldoff ...
Warning - could not open object 2545: can't open object (errTmBackgroundHoldoff)

retrying after errTmBackgroundHoldoff ...
Examined 14000 records
Examined 14500 records
Examined 15000 records
Examined 15500 records
Examined 16000 records
Examined 16500 records
Examined 17000 records
Warning - could not open object 3934885: can't open object (errTmBackgroundHoldoff)

retrying after errTmBackgroundHoldoff ...
Warning - could not open object 3934885: can't open object (errTmBackgroundHoldoff)

retrying after errTmBackgroundHoldoff ...
Examined 17500 records
Table - 1
SwModule - 9
StationDay - 1796
Headend - 6
SoundFile - 18
Image - 264
IrBlastData - 176
IrFormat - 190
ResourceGroup - 49
LogoGroup - 2
LoopSet - 12
IrTivoFormat - 86
PostalCode - 2
Font - 2
Program - 9610
Genre - 208
Station - 704
Component - 900
Series - 3115
ComponentCode - 577
DataSet - 31
SwSystem - 1
VideoClip - 74
Total - 17838
groovyclam
Almost there...
Almost there...
 
Posts: 47
Joined: Wed Feb 16, 2011 12:17 pm
Location: United Kingdom

Re: Alpha Tester - Getting hideous reboots

Postby gcobb » Fri May 27, 2011 1:34 pm

Automan wrote:My box is up and running again on the Tribune EPG (delete and clear everything)

Running tivosh count-db.tcl generates the following...

Thanks, Automan. If your box survives (and the numbers do not go down) then that blows away the theory that the problem is the sheer volume of entries (in particular, the Program number is much higher now you have switched back to Tribune).

I am still trying to reproduce. I have seen one occurrence of this crash -- but only one so far.
gcobb
AltEPG Team
AltEPG Team
 
Posts: 255
Joined: Sun Feb 20, 2011 8:36 pm

Re: Alpha Tester - Getting hideous reboots

Postby gcobb » Fri May 27, 2011 1:39 pm

groovyclam wrote:Here is my count output after a new guided setup to AltEPG -> RF + Digital Satellite -> SKY lineup -> only chose channels that AltEPG does listings for.

This time it ran with errors:

Thanks. I am not sure what conclusions to draw, but getting the data is helpful.

By the way, errTmBackgroundHoldoff isn't a real error -- if another process is accessing the database at the same time then one of them will get this "error" back, which is a message to retry the access. My script doesn't bother to hide those.
gcobb
AltEPG Team
AltEPG Team
 
Posts: 255
Joined: Sun Feb 20, 2011 8:36 pm

Re: Alpha Tester - Getting hideous reboots

Postby groovyclam » Fri May 27, 2011 2:29 pm

It's now 4 and a half hours after the guided setup and I just put in my season passes and some manual records on EuroSport with no crashes.

I also used the live TV overlay to cycle through the 20 or so subset of channels of the Sky lineup I chose to receive listings for without any crashes. In my previous experience this would generate a crash within half an hour or so.

As I have said before I personally suspect that choosing a channel in your lineup, that AltEPG has no listings for, causes the problem.

Automan's experience of then deselecting them doesn't get rid of the problem once you are experiencing it.

I can't report to the forum for another two days from now but if I get through the weekend without any crashes I will then add some channels back into my lineup that AltEPG doesn't have data for. If that causes the problem to start again on my setup then I think that proves the case.

I'll report back in two days.
groovyclam
Almost there...
Almost there...
 
Posts: 47
Joined: Wed Feb 16, 2011 12:17 pm
Location: United Kingdom

Re: Alpha Tester - Getting hideous reboots

Postby Automan » Fri May 27, 2011 7:54 pm

Back on the old tribune data after a clear & delete my Tivo has been up 0d 7h 03m 34s

tverr only contains two entries...

May 27 13:02:16 (none) TmkMediaswitch::Trace[155]: BOGUS EVENT LENGTH: 827186 SID:0xe0
May 27 13:02:16 (none) TmkMediaswitch::Trace[155]: BOGUS AUDIO LENGTH: 32832

Was it only the two of us that were having these reboot issues?

Automan.
Automan
TiVo lover
TiVo lover
 
Posts: 92
Joined: Tue May 17, 2011 9:06 am
Location: South Coast, Sussex, UK

Re: Alpha Tester - Getting hideous reboots

Postby jrg » Sat May 28, 2011 11:45 am

Automan wrote:Was it only the two of us that were having these reboot issues?


I had reboots, after my original switch to the AltEPG - but I was suspicious of the Season Pass -> Wishlist conversion that I'd done using Mikerr's original script and whether that might have corrupted something (because it duplicated some wishlists, and errored on a manual recording.)

Anyway, after clearing program listings data & season passes, forcing a load of the AltEPG data, and then loading back in the (saved) wishlist-based season passes I thought everything had remained stable with no reboots. Though it looks like it actually rebooted early this morning. I'll continue to monitor.

The Tivoweb 'info' page works again now, though. After the first AltEPG load something was causing a TCL exception.
jrg
Almost there...
Almost there...
 
Posts: 27
Joined: Tue Feb 15, 2011 10:01 pm
Location: London, UK

Re: Alpha Tester - Getting hideous reboots

Postby Automan » Sat May 28, 2011 11:59 am

jrg wrote:
Automan wrote:Was it only the two of us that were having these reboot issues?


I had reboots, after my original switch to the AltEPG - but I was suspicious of the Season Pass -> Wishlist conversion that I'd done using Mikerr's original script and whether that might have corrupted something (because it duplicated some wishlists, and errored on a manual recording.)

Anyway, after clearing program listings data & season passes, forcing a load of the AltEPG data, and then loading back in the (saved) wishlist-based season passes I thought everything had remained stable with no reboots. Though it looks like it actually rebooted early this morning. I'll continue to monitor.

The Tivoweb 'info' page works again now, though. After the first AltEPG load something was causing a TCL exception.


The only wishlists I had were created from scratch on the box running the AltEPG.

I wonder if it is caused by the change in genre data and the missing data from the MFS?

DataSet 1316520/11 {
ServerVersion = 46
Data = 1316512/-1 1316519/-1 1316503/-1 1316504/-1 1316506/-1 1316507/-1 1316508/-1 1316509/-1 1316510/-1 1316511/-1 1316513/-1 1316514/-1 1316515/-1 1316517/-1 1316516/-1 1316505/-1
Date = 13762
ExpirationPolicy = 0
(attribute 0x410014 not in schema)
Name = GenreVersion
ServerId = 494
Version = 1
IndexPath = /DataSet/GenreVersion /Server/494
}

Automan.
Automan
TiVo lover
TiVo lover
 
Posts: 92
Joined: Tue May 17, 2011 9:06 am
Location: South Coast, Sussex, UK

Re: Alpha Tester - Getting hideous reboots

Postby healeydave » Sat May 28, 2011 12:33 pm

jrg wrote:
Automan wrote:Was it only the two of us that were having these reboot issues?

The Tivoweb 'info' page works again now, though. After the first AltEPG load something was causing a TCL exception.


Thats happens when you have no epg data or when it hasn't finished loading and indexing on the original system too!
Keeping the dream alive.
healeydave
AltEPG Team
AltEPG Team
 
Posts: 921
Joined: Mon Mar 20, 2006 7:42 pm
Location: Worcester

Re: Alpha Tester - Getting hideous reboots

Postby mrtickle » Sat May 28, 2011 8:19 pm

Interesting thread. I've had reboot problems in the past (with Tribune data) and had put it down to a bad bit of disc unluckily in MFS.

I much prefer that a channel without data is missing from the lineup completely so I'm really pleased that was done, rather than trying to add the 2-hr blocks placeholders. Those were only really ok on a channel that had temporarily stopped provided data to Tribune, but it's stupid if the channel never provided data IMHO. Running guided setup on a Sky lineup has always been a painful task when you get to the Channels I Receive screen; far too much dross channels that didn't provide data for 10 years. We'll have fewer channels in the lineup, faster indexing, smaller databases in MFS etc. All good.
--
links to my TiVo logos, TivoWebPlus 2.1.b3 UK-20120818, Tracker v3.3.3 & v3.3.4 (17th Jun 2013), GDchecker v1.06b, Digiguide checker v0.4.3-rc5 and Autospace v1.65 can all be found in this post.
mrtickle
TVGuide Admin
TVGuide Admin
 
Posts: 3292
Joined: Sat May 14, 2011 1:46 pm
Location: Birmingham, UK

PreviousNext

Return to General

Who is online

Users browsing this forum: No registered users and 10 guests

cron