27 replies to this topic

[Wizard1]

Hi Guys

 

I have a friend that owns an Xtrend ET8500 with Twin Satellite Tuners.  Since owing it (approx 6 Months) he has experienced random crashes & reboots.  I have recently re-flashed it to Openpli 6.0, unfortunately the crashes & reboots have become more frequent.  I own a Vu+Duo 2 & use Openpli 6.0 on it without any of the above problems.  I wonder If someone could look at the Crashlog attached & point me in the right direction.  It appears to be pointing at XMLimporter, but I'm not sure what the problem is.

 

 

Regards

 

Wizard

Attached Files

•  enigma2_crash_1511550975.log   1.99KB   2 downloads

[Dimitrij]

Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Plugins/Extensions/EPGImport/gen_xmltv.py", line 33, in iterator
    for r in xmltv_parser.enumFile(fd):
  File "/usr/lib/enigma2/python/Plugins/Extensions/EPGImport/xmltvconverter.py", line 70, in enumFile
    for elem in enumerateProgrammes(fileobj):
  File "/usr/lib/enigma2/python/Plugins/Extensions/EPGImport/xmltvconverter.py", line 46, in enumerateProgrammes
    for event, elem in iterparse(fp):
  File "<string>", line 91, in next
ParseError: not well-formed (invalid token): line 73628, column 39
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Plugins/Extensions/EPGImport/gen_xmltv.py", line 33, in iterator
    for r in xmltv_parser.enumFile(fd):
  File "/usr/lib/enigma2/python/Plugins/Extensions/EPGImport/xmltvconverter.py", line 70, in enumFile
    for elem in enumerateProgrammes(fileobj):
  File "/usr/lib/enigma2/python/Plugins/Extensions/EPGImport/xmltvconverter.py", line 46, in enumerateProgrammes
    for event, elem in iterparse(fp):
  File "<string>", line 91, in next
ParseError: not well-formed (invalid token): line 14178, column 19
PC: 76edfa68
    00000000 00000001 00000000 00000020
    00000003 71bfd350 00000000 00000000
    00000001 0000000b 71bfc3f8 00000000
    76ff33f4 00000000 00000000 00000000
    00000000 71bfd350 00000006 71bfd488
    00000002 00000001 77cc5000 00000005
    00000018 76ee0584 00000010 00000000
    7700fe00 71bfd2b8 71bfd608 76edf9f4
-------FATAL SIGNAL

xml source corrupt

[Wizard1]

Hi Dimitrij

 

What would you suggest to overcome this problem ?  I've uninstalled the epgimport plugin, then re-installed it.  The problem still persists.

 

Regards

 

Wizard

[Dimitrij]

xml source _{= internet}

_{not plugin}

[Wizard1]

Hi Dimitrij

 

Thanks for your advice.  As I understand it, its his Internet causing the problem.  For now I've asked him to disable the EPGimport plugin rather than un-installing it.  I hope this cures the problem.  Not sure how he can get around this problem, other than calling his ISP to check for Internet problems in his area.

 

Regards

 

Wizard

[WanWizard]

The question is: what is being imported? So it is not the plugin, it is the data the plugin downloads and tries to read. What does the epgimport log say?

[Wizard1]

Hi WanWizard

 

Where would I find the epgimport log ?  I've looked in both /usr/lib/enigma2/python/Plugins/Extensions/EPGImport/ and the /tmp directories.  The only thing I see in  /media/hdd/ are any Crashlogs that have been created.

 

Regards

 

Wizard

[WanWizard]

No clue, it could be in memory.

 

You can access it from the plugin, menu button, option 1 "slow log". There's an option to save it using a colour button.

[Wizard1]

Hi WanWizard

 

I've attached the last epgimport log file from his Xtrend ET8500.

 

Regards

 

Wizard

Attached Files

•  epgimport.log   6.28KB   3 downloads

Edited by Wizard1, 28 November 2017 - 19:00.

[WanWizard]

I don't see anything weird in there, and I import SKY UK myself as well. Given that fact, and the fact your other boxes import file, it seems unlikely the source is the cause of the crash.

 

I also think that a source issue would cause that Python error you posted, but Python errors don't cause segfaults.

 

I would start with making a backup (using Autobackup), and flash the box again, with either 6.0-release or 6.1-rc. If you make the backup on the same USB stick you flash the box with (or on the harddisk), it will be automatically restored after the flash. 

[Wizard1]

Hi WanWizard

 

I'd like to point out that this Xtrend ET8500 is at a friends house & not mine.  He is currently running Openpli 6.0, but also had problems with Openpli 4.0.  Random (Green Screen) Crashes, Random Rebooting & Random Lockups. 

 

As well as owning a Vu+Duo2, I also have an Xtrend ET8500.  I have used a number of my backup images on his Xtrend ET 8500 which also Crash, Lockup & Reboot.  My own Xtrend doesn't have any of these problems & works like a charm.

 

In hindsight, I recall him having similar issues with his old Vu+Duo.  He thought these problems were down to the age of the Vu+Duo & treated himself to a brand new Xtrend ET 8500.  Although I have suspected his Fibre Broadband Internet,  I think that Dimitrij has now confirmed that this may be his problem.  I have asked my friend to disable the EPGimport Plugin.  I'll see what happens over the next few days & report back. 

 

Regards

 

Wizard

[WanWizard]

Looks indeed like data corruption. Could happen in transfer (the new xz format is more susceptible to bit errors), but it could also happen because local storage (disk, stick) is on the way out or corrupt.

 

Random lockups or reboots can also be caused by a failty power supply or power source, especially when under load (multiple tuners active, recording or playback). The VU Duo power supply is notorious for it, but I haven't seen any reports for an ET8500.

[Erik Slagter]

The corruption can also occur from mismatching encodings. Seen that often enough. Provider says it's UTF-8 but in the end it appears to be Windows-1252.

[WanWizard]

But then the problem should occur on every box, and not only on one.

[Erik Slagter]

On one and one machine only sounds as driver bug... I know the et8500 has a few.

[Wizard1]

Hi Guys

 

My friends Xtrend ET8500 is still crashing even after disabling EPGimport.  See Crashlog.

 

Regards

 

Wizard

Attached Files

•  enigma2_crash_1511997615.log   852bytes   4 downloads

[WanWizard]

Segfault.

 

So somewhere something is poking into another process' memory.

 

What is the (end of the) dmesg output?

[Wizard1]

Hi WanWizard

 

Not sure what you mean by: What is the (end of the) dmesg output?

 

Regards

 

Wizard

[WanWizard]

issue the command "dmesg", and cut and paste the last x lines here, it usually has more info about the segfault. 

[Wizard1]

Hi WanWizard

 

Is this the info you require ?

 

Bad block table found at page 262080, version 0x01

Bad block table found at page 262016, version 0x01

Creating 3 MTD partitions on "brcmnand.0":

0x000000000000-0x000020000000 : "complete"

0x000000000000-0x000000600000 : "kernel"

0x000000600000-0x000020000000 : "rootfs"