speedyrite
08-04-2006, 03:49 AM
We've upgraded both our TiVos (#1 in October last year, #2 in January this year) to have a 400GB hard drive and also added a Cachecard with 512MB memory. #1 currently has an uptime of >73 days and only ever reboots when we tell it to, but #2 never seems to manage an uptime of more than a few days (in fact, it has sometimes stayed up for barely a day).
Research on the forums seemed to indicate that it may be a PSU related problem, so we fitted a new PSU to #2 - but this hasn't made any difference to stability, #2 is still rebooting regularly.
Further research on the forums suggested it may be a TivoWeb related problem, so we increased the value of TIVOSH_POOLSIZE from 2916352 to 3244032 - but this hasn't made any difference to stability, #2 is still rebooting regularly.
Stumped by what the cause of the problem is, we sat down for a think! Clutching wildly at straws, we noticed that the "recording profile" of both TiVos is somewhat different - #1 records mostly films and drama series on a selective basis, say maybe a couple of things a day - whereas #2 seems to be constantly recording lots of 30/40 minute shows, say 10-12 or more shows daily.
Here's some details taken from the TivoWeb info page on both TiVos this morning:
#1 Total (shows on Now Playing) is 134 using 282070MB (76.1%)
#1 Free Space Best is 88402MB (23.9%)
#1 Deleted is 61 using 87776MB (23.7%)
#2 Total (shows on Now Playing) is 291 using 236783MB (63.9%)
#2 Free Space Best is 133648MB (36.1%)
#2 Deleted is 170 using 132513MB (35.8%)
Q: Could the "recording profile" behaviour be somehow related to or affect the frequency of rebooting?
Finally, here's some info taken from kernel and tverr logs immediately following the last reboot by #2 at 9pm last night:
(from kernel log...)
Aug 3 20:04:29 (none) kernel: Tmk Assertion Failure:
Aug 3 20:04:29 (none) kernel: GetServiceInfo, line 43 ()
Aug 3 20:04:29 (none) kernel: Tmk Fatal Error: Thread ContextMgr event handler <152> died due to signal -2
(from tverr log...)
Aug 3 19:45:57 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 19:46:02 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:02 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:46:12 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:12 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:46:19 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 19:46:22 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:22 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:46:30 (none) Scheduler[150]: Error 0x00030007: line 5917
Aug 3 19:46:30 (none) Scheduler[150]: Error 0x00030007: line 6185
Aug 3 19:46:30 (none) Scheduler[150]: Error 0x00030007: line 1460
Aug 3 19:46:30 (none) Scheduler[150]: Error 0x00030007: line 1508
Aug 3 19:46:30 (none) Scheduler[150]: Error returned from HandleDataChanged: 0x00030007
Aug 3 19:46:33 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:33 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:46:41 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 19:46:42 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:42 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:46:53 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:53 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:47:01 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 19:47:03 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:47:03 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:47:13 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:47:13 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:01:45 (none) Scheduler[150]: Error 0x00030007: line 5917
Aug 3 20:01:45 (none) Scheduler[150]: Error 0x00030007: line 6185
Aug 3 20:01:45 (none) Scheduler[150]: Error 0x00030007: line 1460
Aug 3 20:01:45 (none) Scheduler[150]: Error 0x00030007: line 1508
Aug 3 20:01:45 (none) Scheduler[150]: Error returned from HandleDataChanged: 0x00030007
Aug 3 20:01:46 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 20:01:48 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:01:48 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:01:58 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:01:58 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:02:06 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 20:02:08 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:02:08 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:02:18 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:02:18 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:02:26 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 20:02:28 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:02:28 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:02:38 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:02:38 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:04:29 (none) DbSetupUtil[152]: DbServiceInfoUtil.C: Error in GetServiceInfo with 0x00030007
Aug 3 20:04:29 (none) TmkAssertionFailure[152]: (GetServiceInfo, line 43 ())
Aug 3 20:04:29 (none) ContextMgr event handler[152]: Tmk Fatal Error: Thread ContextMgr event handler <152> died due to signal -2
Aug 3 20:04:29 (none) ContextMgr event handler[152]: Tmk Thread Backtrace: 1a344ec 1a32a44 1be84a8 1c370e4 1c37848 1c37aec 1c35f6c 1bb228c 1bb1cb0 1ac3994 1abdef8 1bc97c8 1ac2c80 1abef88 1ac249c 1ac4ddc 1ac4358 1b91bb4 1c01e6c 1c249b8 1c23c84 1c23db0 1c27364 1c28374 1c28420 1c27504 1c23eb4 1c248fc 1c01ca8 1bf73bc 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 ipe
Aug 3 20:04:29 (none) ContextMgr event handler[152]: Tmk Fatal Error: Thread died due to signal -2
Aug 3 20:04:29 (none) ContextMgr event handler[152]: Invoking rule 834: rebooting system
Any suggestions or comments on the situation with #2 will be welcomed!
Research on the forums seemed to indicate that it may be a PSU related problem, so we fitted a new PSU to #2 - but this hasn't made any difference to stability, #2 is still rebooting regularly.
Further research on the forums suggested it may be a TivoWeb related problem, so we increased the value of TIVOSH_POOLSIZE from 2916352 to 3244032 - but this hasn't made any difference to stability, #2 is still rebooting regularly.
Stumped by what the cause of the problem is, we sat down for a think! Clutching wildly at straws, we noticed that the "recording profile" of both TiVos is somewhat different - #1 records mostly films and drama series on a selective basis, say maybe a couple of things a day - whereas #2 seems to be constantly recording lots of 30/40 minute shows, say 10-12 or more shows daily.
Here's some details taken from the TivoWeb info page on both TiVos this morning:
#1 Total (shows on Now Playing) is 134 using 282070MB (76.1%)
#1 Free Space Best is 88402MB (23.9%)
#1 Deleted is 61 using 87776MB (23.7%)
#2 Total (shows on Now Playing) is 291 using 236783MB (63.9%)
#2 Free Space Best is 133648MB (36.1%)
#2 Deleted is 170 using 132513MB (35.8%)
Q: Could the "recording profile" behaviour be somehow related to or affect the frequency of rebooting?
Finally, here's some info taken from kernel and tverr logs immediately following the last reboot by #2 at 9pm last night:
(from kernel log...)
Aug 3 20:04:29 (none) kernel: Tmk Assertion Failure:
Aug 3 20:04:29 (none) kernel: GetServiceInfo, line 43 ()
Aug 3 20:04:29 (none) kernel: Tmk Fatal Error: Thread ContextMgr event handler <152> died due to signal -2
(from tverr log...)
Aug 3 19:45:57 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 19:46:02 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:02 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:46:12 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:12 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:46:19 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 19:46:22 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:22 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:46:30 (none) Scheduler[150]: Error 0x00030007: line 5917
Aug 3 19:46:30 (none) Scheduler[150]: Error 0x00030007: line 6185
Aug 3 19:46:30 (none) Scheduler[150]: Error 0x00030007: line 1460
Aug 3 19:46:30 (none) Scheduler[150]: Error 0x00030007: line 1508
Aug 3 19:46:30 (none) Scheduler[150]: Error returned from HandleDataChanged: 0x00030007
Aug 3 19:46:33 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:33 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:46:41 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 19:46:42 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:42 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:46:53 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:46:53 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:47:01 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 19:47:03 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:47:03 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 19:47:13 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 19:47:13 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:01:45 (none) Scheduler[150]: Error 0x00030007: line 5917
Aug 3 20:01:45 (none) Scheduler[150]: Error 0x00030007: line 6185
Aug 3 20:01:45 (none) Scheduler[150]: Error 0x00030007: line 1460
Aug 3 20:01:45 (none) Scheduler[150]: Error 0x00030007: line 1508
Aug 3 20:01:45 (none) Scheduler[150]: Error returned from HandleDataChanged: 0x00030007
Aug 3 20:01:46 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 20:01:48 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:01:48 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:01:58 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:01:58 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:02:06 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 20:02:08 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:02:08 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:02:18 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:02:18 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:02:26 (none) Recorder[148]: Error checking showing: 0x00030007
Aug 3 20:02:28 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:02:28 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:02:38 (none) Recorder[148]: Error checking schedule: 0x00030007
Aug 3 20:02:38 (none) TvCheckScheduleTask::Run[148]: error 0x00030007
Aug 3 20:04:29 (none) DbSetupUtil[152]: DbServiceInfoUtil.C: Error in GetServiceInfo with 0x00030007
Aug 3 20:04:29 (none) TmkAssertionFailure[152]: (GetServiceInfo, line 43 ())
Aug 3 20:04:29 (none) ContextMgr event handler[152]: Tmk Fatal Error: Thread ContextMgr event handler <152> died due to signal -2
Aug 3 20:04:29 (none) ContextMgr event handler[152]: Tmk Thread Backtrace: 1a344ec 1a32a44 1be84a8 1c370e4 1c37848 1c37aec 1c35f6c 1bb228c 1bb1cb0 1ac3994 1abdef8 1bc97c8 1ac2c80 1abef88 1ac249c 1ac4ddc 1ac4358 1b91bb4 1c01e6c 1c249b8 1c23c84 1c23db0 1c27364 1c28374 1c28420 1c27504 1c23eb4 1c248fc 1c01ca8 1bf73bc 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 ipe
Aug 3 20:04:29 (none) ContextMgr event handler[152]: Tmk Fatal Error: Thread died due to signal -2
Aug 3 20:04:29 (none) ContextMgr event handler[152]: Invoking rule 834: rebooting system
Any suggestions or comments on the situation with #2 will be welcomed!