[linux-dvb] Possible EIT corruption using lastest patch for Nova-T 500 (from " dib7000p tuning problem solved")

Nicolas Will nico at youplala.net
Tue Jan 22 12:59:56 CET 2008


On Tue, 2008-01-22 at 12:41 +0100, Eduard Huguet wrote:
> Hi, 
>     I've just applied the patch and compiled the drivers. I haven't
> tested actual tuning, since I'm not in front of my computer now, but
> this is awaken and idle so MythTV is  currently simply scanning EIT
> data. So well, the following messages has started appearing on my
> mythbackend.log:
> 
> 2008-01-22 12:37:50.742 Error: offset>181, pes length & current can
> not be queried
> 2008-01-22 12:37:50.744 EITHelper: Added 2 events
> 2008-01-22 12:37: 51.217 EITHelper: Added 7 events
> 2008-01-22 12:37:51.339 330 secs left to system shutdown!
> 2008-01-22 12:37:51.706 EITHelper: Added 3 events
> 2008-01-22 12:37:52.164 EITHelper: Added 4 events
> 2008-01-22 12:37:52.593 EITHelper: Added 2 events
> 2008-01-22 12:37:53.011 EITHelper: Added 1 events
> 2008-01-22 12:37:53.428 EITHelper: Added 1 events
> 2008-01-22 12:37:55.208 Error: offset>181, pes length & current can
> not be queried 
> 2008-01-22 12:37:56.982 Error: offset>181, pes length & current can
> not be queried
> 2008-01-22 12:38:01.411 320 secs left to system shutdown!
> 2008-01-22 12:38:11.484 310 secs left to system shutdown!
> 2008-01-22 12:38: 15.448 EITHelper: Added 1 events
> 2008-01-22 12:38:21.553 300 secs left to system shutdown!
> 2008-01-22 12:38:26.326 Error: offset>181, pes length & current can
> not be queried
> 2008-01-22 12:38:31.626 290 secs left to system shutdown! 
> 2008-01-22 12:38:41.698 280 secs left to system shutdown!
> 2008-01-22 12:38:51.767 270 secs left to system shutdown!
> 2008-01-22 12:38:54.451 Error: offset>181, pes length & current can
> not be queried
> 
> 
> The error about "offset>181 etc..." is usually due to the card
> receiving corrupt data, and usually causes MySQL table corruption that
> must be fixed using "myisamchk". I'm pretty sure this wasn't appearing
> these past days, and today we are in a very good weather condition so
> I don't think it's related a bad signal reception. 
> 
> I'm going to unapply the patch and test again after repairing the
> database.
> 


I have none of these errors, and I have scanned my logs since the patch
got applied (Jan 21 20:31:39).

My DB looks clean and error-free.

For example:

        2008-01-22 11:15:59.680 EITScanner: Now looking for EIT data on multiplex of channel 1
        2008-01-22 11:16:58.558 EITScanner: Added 9 EIT Events
        2008-01-22 11:17:27.204 EITScanner: Added 124 EIT Events
        2008-01-22 11:19:57.640 EITScanner: Added 2 EIT Events
        2008-01-22 11:19:57.645 Reschedule requested for id -1.
        2008-01-22 11:19:58.489 Scheduled 69 items in 0.8 = 0.12 match + 0.73 place
        2008-01-22 11:21:10.416 EITScanner: Now looking for EIT data on multiplex of channel 10
        2008-01-22 11:21:20.914 EITScanner: Now looking for EIT data on multiplex of channel 11
        2008-01-22 11:22:14.621 EITScanner: Added 11 EIT Events
        2008-01-22 11:22:25.830 EITScanner: Added 7 EIT Events
        2008-01-22 11:23:59.271 EITScanner: Added 4 EIT Events
        2008-01-22 11:23:59.276 Reschedule requested for id -1.
        2008-01-22 11:24:00.100 Scheduled 69 items in 0.8 = 0.11 match + 0.71 place
        2008-01-22 11:26:11.878 EITScanner: Added 1 EIT Events
        2008-01-22 11:26:12.562 EITScanner: Added 2 EIT Events
        2008-01-22 11:26:21.165 EITScanner: Now looking for EIT data on multiplex of channel 16
        2008-01-22 11:26:48.442 EITScanner: Now looking for EIT data on multiplex of channel 12
        2008-01-22 11:27:28.193 EITScanner: Added 7 EIT Events
        2008-01-22 11:27:28.201 Reschedule requested for id -1.
        2008-01-22 11:27:28.993 Scheduled 69 items in 0.8 = 0.11 match + 0.68 place
        2008-01-22 11:27:53.426 EITScanner: Added 8 EIT Events
        2008-01-22 11:29:44.756 match[0]: -900 'Take a Bow' vs. 'Finley the Fire Engine'
        2008-01-22 11:31:03.319 EITScanner: Added 3 EIT Events
        2008-01-22 11:31:03.324 Reschedule requested for id -1.
        2008-01-22 11:31:04.138 Scheduled 69 items in 0.8 = 0.12 match + 0.69 place
        2008-01-22 11:31:06.353 EITScanner: Added 4 EIT Events
        2008-01-22 11:31:31.192 EITScanner: Added 1 EIT Events
        2008-01-22 11:31:31.660 EITScanner: Now looking for EIT data on multiplex of channel 71
        2008-01-22 11:32:13.242 EITScanner: Added 1 EIT Events
        2008-01-22 11:32:16.142 EITScanner: Now looking for EIT data on multiplex of channel 1
        2008-01-22 11:33:02.801 EITScanner: Added 389 EIT Events
        2008-01-22 11:33:22.705 EITScanner: Added 16 EIT Events
        2008-01-22 11:35:15.163 EITScanner: Added 1 EIT Events
        2008-01-22 11:35:15.164 Reschedule requested for id -1.
        2008-01-22 11:35:15.981 Scheduled 69 items in 0.8 = 0.09 match + 0.73 place
        2008-01-22 11:36:42.121 EITScanner: Now looking for EIT data on multiplex of channel 11
        2008-01-22 11:37:43.729 EITScanner: Now looking for EIT data on multiplex of channel 10
        2008-01-22 11:38:11.125 EITScanner: Added 92 EIT Events
        2008-01-22 11:38:11.130 Reschedule requested for id -1.
        2008-01-22 11:38:11.993 Scheduled 69 items in 0.9 = 0.13 match + 0.74 place
        2008-01-22 11:38:47.798 EITScanner: Added 11 EIT Events
        2008-01-22 11:41:52.794 EITScanner: Now looking for EIT data on multiplex of channel 12
        2008-01-22 11:42:55.752 EITScanner: Added 3 EIT Events
        2008-01-22 11:42:55.756 Reschedule requested for id -1.
        2008-01-22 11:42:56.611 Scheduled 69 items in 0.9 = 0.12 match + 0.73 place
        2008-01-22 11:43:11.329 EITScanner: Now looking for EIT data on multiplex of channel 16
        2008-01-22 11:44:14.730 EITScanner: Added 4 EIT Events
        2008-01-22 11:47:03.335 EITScanner: Now looking for EIT data on multiplex of channel 1
        2008-01-22 11:47:24.748 match[0]: 0 'Schools' vs. 'Schools: Starship'
        2008-01-22 11:48:31.062 EITScanner: Added 142 EIT Events
        2008-01-22 11:48:31.063 Reschedule requested for id -1.
        2008-01-22 11:48:31.916 Scheduled 69 items in 0.9 = 0.12 match + 0.73 place
        2008-01-22 11:48:39.159 EITScanner: Now looking for EIT data on multiplex of channel 71
        2008-01-22 11:50:01.990 EITScanner: Added 5 EIT Events

I've looked at my MythTV backend logs history, and all the offset errors
i have found happened *before* the reboot with the patched code:

        nico at favia:~$ grep "Error: offset" /var/log/mythtv/mythbackend*
        /var/log/mythtv/mythbackend.log.1:2008-01-21 07:59:45.003 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.1:2008-01-21 19:10:23.466 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.2:2008-01-20 12:50:51.348 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.2:2008-01-20 22:07:02.383 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.3:2008-01-19 17:22:48.765 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.4:2008-01-18 19:38:23.736 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.4:2008-01-18 19:39:13.174 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.4:2008-01-18 19:39:16.050 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.4:2008-01-18 20:00:28.389 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.4:2008-01-18 20:06:46.950 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.4:2008-01-18 20:11:12.236 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.6:2008-01-16 17:59:42.568 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.6:2008-01-16 18:01:08.713 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.6:2008-01-16 18:01:43.939 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.7:2008-01-15 10:49:37.751 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.7:2008-01-15 15:21:16.379 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.7:2008-01-15 15:21:32.546 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.7:2008-01-15 15:22:26.416 Error: offset>181, pes length & current can not be queried
        /var/log/mythtv/mythbackend.log.7:2008-01-15 15:24:40.447 Error: offset>181, pes length & current can not be queried


There is a chance your issue is not related to the patch, or that I am
very lucky...

Nico




More information about the linux-dvb mailing list