121 replies to this topic

[marjac]

Please fix smartreader with oscam and card nagravision.

Thanks

[Henksat]

This is OpenPli, not smartreader or Oscam forum....

[matrix64]

only one way to find out
I don't have those devices myself.

 

i can confirm that it works! i use the 9035 kernel module and the system boot regulary

 

D.

my a867 does not work.
I installed the kernel af9035 and a867  but the dtt key  is not recognized

et9000

[sypo]

This is OpenPli, not smartreader or Oscam forum....

Fortunately, there is no compulsion upgrade to a new kernel...

[phillipssat]

Whats about the known Problems (ET9X00) since new Kernel 3.8.7 with MKV-Files&DTS(high Bitrate) Audio ?

 

This Films don't run.... they stop at 00:00 nothing happens.

 

Again a gstreamer Problem !?  Hopefully someone can fix that Problem....

Edited by phillipssat, 19 May 2013 - 08:08.

[pieterg]

Still the same gstreamer issue.
A kernel update is not going to change that.

[phillipssat]

Do you know which guy can fix this or has fix it recently for the last Kernelupdate ??

[pieterg]

Again, it's not related to the kernel version. It's a gstreamer issue, which has been there since the beginning of openpli 3

[eozen81]

Today, for my Solo2 I have flashed OpenPLi-3.0-beta-vusolo2-20130519_usb.zip and insalled latest drivers from http://archive.vuplu...wnload/drivers/ but the device did not boot again. When will you release a stable version which will support latest Solo2 drivers please?

[Gennar1]

Some update about USB tuners on the new kernel 3.8.7.

Some drivers are reported to work fine:

- dvb-usb-v2 drivers (such as af9035 for Avermedia A835 and A867 sticks, or rtl28xxu sticks using the new kernel driver), after the patch from Pieterg;

- as102 driver;

- Sundtek driver;

 

Other are confirmed to crash the kernel with various error messages:

- em28xx drivers (such as PCTV290e);

- dvb-usb drivers (such as the old a867 or the out-of-kernel rtl2832 driver form Realtek);

 

For example, this is a crashlog from PCTV290e using the em28xx driver framework:

usb 1-2: new high-speed USB device number 3 using ehci-brcm
em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0)
em28xx: DVB interface 0 found
em28xx #0: chip ID is em28174
Unhandled kernel unaligned access[#1]:
Cpu 1
$ 0   : 00000000 10008b00 00000000 ffffffff
$ 4   : cdebe000 00000000 00000004 caf59c30
$ 8   : 34000000 807b7941 00000000 20706968
$12   : 0000011e e0ffffff 00000000 00000000
$16   : cdebe000 00000001 cdebe000 8004be40
$20   : 00000004 00000000 e25ed39c caf59c30
$24   : 00000008 e25ed360                  
$28   : caf58000 caf59bc8 cdebe4e0 e25ed388
Hi    : 0000237a
Lo    : b09c1000
epc   : e25ed158 em28xx_read_reg_req_len+0x48/0x250 [em28xx]
    Tainted: GF          O
ra    : e25ed388 em28xx_read_reg_req+0x28/0x3c [em28xx]
Status: 10008b03    KERNEL EXL IE 
Cause : 80800010
BadVA : ffffffff
PrId  : 0002a044 (Brcm4380)
Modules linked in: em28xx(+) videobuf_vmalloc videobuf_core tveeprom nfsd exportfs ftdi_sio usbserial ipv6 dvb(OF) modloader2(O) modloader(O) tpm(O)
Process modprobe (pid: 1710, threadinfo=caf58000, task=cfc2e488, tls=77432490)
Stack : 00000006 e25f51c8 00000000 00000000 00000000 00000000 807b70b2 0000001d
        00000000 ffffffff cae78000 cae78000 00000000 cdebe000 8004be40 80724680
        00000000 e25ed39c 00000001 e25ed388 00000000 802e731c 00000000 00000000
        00000001 caf59c44 caf59c44 cae78000 00000000 e25ec81c 00000000 cdebe000
        00000000 805e6ec0 00002013 0000024f 00000000 00000000 cf523420 cf523400
        ...
Call Trace:
[<e25ed158>] em28xx_read_reg_req_len+0x48/0x250 [em28xx]
[<e25ed388>] em28xx_read_reg_req+0x28/0x3c [em28xx]
[<e25ec81c>] em28xx_usb_probe+0x97c/0xcec [em28xx]
[<8040c3d8>] usb_probe_interface+0xf8/0x234
[<8034dbc0>] driver_probe_device+0xa0/0x2bc
[<8034de98>] __driver_attach+0xbc/0xc4
[<8034bf00>] bus_for_each_dev+0x5c/0xa8
[<8034d20c>] bus_add_driver+0x1b4/0x2b0
[<8034e234>] driver_register+0x90/0x1a0
[<8040b87c>] usb_register_driver+0x90/0x17c
[<80001588>] do_one_initcall+0x160/0x1e8
[<80073fcc>] load_module+0x1a1c/0x21b4
[<80074818>] sys_init_module+0xb4/0xec
[<8000e07c>] stack_done+0x20/0x40


Code: 8fb10060  30b500ff  30d4ffff <1440004f> 8c760000  2a220051  1040004e  3c12e260  3c038000 
---[ end trace 31dc3c2e5fdb62c1 ]---

while this is from a rtl2832 stick using the out-of-kernel driver from Realtek based on dvb-usb:

usb 1-2: new high-speed USB device number 3 using ehci-brcm
dvb-usb: found a 'RTL2832U DVB-T USB DEVICE' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (RTL2832U DVB-T USB DEVICE)
CPU 1 Unable to handle kernel paging request at virtual address 00000000, epc == 00000000, ra == 00000000
Oops[#1]:
Cpu 1
$ 0   : 00000000 10008b00 00000000 00000001
$ 4   : 00000000 00000000 00000001 ffff00fe
$ 8   : cb201fe0 00008b00 00000002 cde97680
$12   : 000562eb 00000000 00000000 7fdee5c0
$16   : 8034ac80 00000000 00000000 cb12894c
$20   : 80460000 e177247c e17724fc e17747c0
$24   : 77ad42a0 80012a9c                  
$28   : cb200000 cb201ad8 00000000 00000000
Hi    : 00000000
Lo    : 00000000
epc   : 00000000   (null)
    Tainted: GF          O
ra    : 00000000   (null)
Status: 10008b03    KERNEL EXL IE 
Cause : 00800008
BadVA : 00000000
PrId  : 0002a044 (Brcm4380)
Modules linked in: dvb_usb_rtl2832(+) dvb_usb nfsd exportfs ftdi_sio usbserial ipv6 dvb(OF) modloader2(O) modloader(O) tpm(O)
Process modprobe (pid: 478, threadinfo=cb200000, task=cf52b1f8, tls=7746c490)
Stack : cfcf4f00 cb1b7468 cb264680 80687e38 cb1ca700 cb128a1c 806296b0 cb175780
        80750000 8034b454 00000000 800c18d4 0000001c 802e3988 00000001 cb175780
        cb3e0000 cb128000 cb12894c cb12894c 80460000 e1803414 cb128a10 80750000
        806dd128 cb201b64 cb201b64 0000001d 00000000 8045bedc 806dd128 00000001
        806dd1d8 00000000 806dd128 00000001 80687e38 00000000 8072bb20 e1995298
        ...
Call Trace:
[<8034b454>] device_create_vargs+0xc4/0xe0
[<800c18d4>] kmem_cache_alloc+0xc0/0x104
[<802e3988>] __up_write+0x3c/0x230
[<80460000>] dvb_dmx_swfilter_packet+0x24/0x5e0
[<e1803414>] rtl2832u_fe_attach+0x8c/0xab4 [dvb_usb_rtl2832]
[<8045bedc>] dvb_register_device+0x210/0x328
[<80460000>] dvb_dmx_swfilter_packet+0x24/0x5e0
[<e177247c>] dvb_usb_fe_sleep+0x0/0x80 [dvb_usb]
[<e17724fc>] dvb_usb_fe_wakeup+0x0/0x8c [dvb_usb]
[<e17fe260>] rtl2832u_frontend_attach+0x20/0x38 [dvb_usb_rtl2832]
[<e1772c08>] dvb_usb_adapter_frontend_init+0xe0/0x1cc [dvb_usb]
[<805e6ef8>] printk+0x38/0x44
[<805e6ec0>] printk+0x0/0x44
[<800c0000>] dma_pool_create+0xc0/0x1e4
[<e1771bc8>] dvb_usb_device_init+0x554/0x75c [dvb_usb]
[<e1771674>] dvb_usb_device_init+0x0/0x75c [dvb_usb]
[<e17fe364>] rtl2832u_usb_probe+0x54/0x1a4 [dvb_usb_rtl2832]
[<8040c210>] usb_match_id+0x6c/0x98
[<8004f2b4>] blocking_notifier_call_chain+0x14/0x20
[<8040c3d8>] usb_probe_interface+0xf8/0x234
[<8034d8a0>] driver_sysfs_add+0x78/0xac
[<8034dbc0>] driver_probe_device+0xa0/0x2bc
[<8040c2a0>] usb_device_match+0x64/0xa4
[<8034de98>] __driver_attach+0xbc/0xc4
[<8034bbc4>] next_device+0x10/0x30
[<8034dddc>] __driver_attach+0x0/0xc4
[<8034bf00>] bus_for_each_dev+0x5c/0xa8
[<8034bb44>] bus_get+0x28/0x3c
[<8034d20c>] bus_add_driver+0x1b4/0x2b0
[<8034e178>] driver_find+0x18/0x44
[<8034e234>] driver_register+0x90/0x1a0
[<8040b87c>] usb_register_driver+0x90/0x17c
[<80012600>] blast_dcache64+0x0/0xf8
[<e185a000>] rtl2832u_usb_module_init+0x0/0x64 [dvb_usb_rtl2832]
[<e185a030>] rtl2832u_usb_module_init+0x30/0x64 [dvb_usb_rtl2832]
[<8008d9f4>] free_hot_cold_page+0x30/0x220
[<800b8f48>] remove_vm_area+0x64/0xf0
[<80001588>] do_one_initcall+0x160/0x1e8
[<800b917c>] __vunmap+0xe4/0x128
[<8004f2b4>] blocking_notifier_call_chain+0x14/0x20
[<80073fcc>] load_module+0x1a1c/0x21b4
[<80070220>] ddebug_dyndbg_module_param_cb+0x0/0x3c
[<800711f8>] module_sect_show+0x0/0x18
[<80074818>] sys_init_module+0xb4/0xec
[<8000e07c>] stack_done+0x20/0x40
[<800c28a8>] sys_close+0x0/0x50


Code: (Bad address in epc)

---[ end trace 55ace6c41ece0447 ]---

 

The errors may vary, but they are always unaligned memory access or invalid kernel pages requests or invalid instructions.

This kind of errors suggests there must be a memory corruption in the stack space of the affected drivers, that is caused by some other drivers that is producing a kernel stack overflow, overwriting some memory area with random garbage.

 

This link explains what may be happening (it's very detailed and informative):

https://sites.google...-stack-overflow

 

So a possible explanation of the errors we see with USB tuners is that the closed-source drivers from Xtrend are producing some kernel stack overflow (that is, they are using more than 8KB of stack memory), corrupting the stack memory of drivers that are loaded after them (such as the USB tuner drivers).

 

A simple way to verify this hypothesis would be to disable the internal tuners (so that the corresponding drivers are not loaded at all) and see if the errors on USB tuners disappears. Any suggestion on how to do this?

Edited by Gennar1, 19 May 2013 - 14:42.

[phillipssat]

Again, it's not related to the kernel version. It's a gstreamer issue, which has been there since the beginning of openpli 3

 

Yes i understand. But now who ist able zu fix gstreamer (mips) ??

[Gennar1]

 

only one way to find out
I don't have those devices myself.

 

i can confirm that it works! i use the 9035 kernel module and the system boot regulary

 

D.

my a867 does not work.
I installed the kernel af9035 and a867  but the dtt key  is not recognized

et9000

 

The a867 is supported by both the dvb-usb-a867 driver (which doesn't work currently) and the af9035 driver. So you have to switch to the latter:

 

opkg remove kernel-module-dvb-usb-a867
opkg install kernel-module-dvb-usb-v2 kernel-module-af9033 kernel-module-dvb-usb-af9035 kernel-module-mxl5007t
cd /lib/firmware
wget http://palosaari.fi/linux/v4l-dvb/firmware/af9035/dvb-usb-af9035-02.fw_0184ba128bee3befe2fc49f144a8dbab_12.5.13.0_6.8.13.0
mv dvb-usb-af9035-02.fw_0184ba128bee3befe2fc49f144a8dbab_12.5.13.0_6.8.13.0 dvb-usb-af9035-02.fw

then reboot using the switch on the back of the decoder.

[pieterg]

Both oopses appear to happen during the modprobe?
The second one is most interesting, it looks like a nullpointer.
Caused by a swfilter call, which happens too early, during the modprobe, before everything has been initialized?
I wouldn't expect data to be delivered untill the first feed is started, certainly not during the module init...

[pieterg]

So a possible explanation of the errors we see with USB tuners is that the closed-source drivers from Xtrend are producing some kernel stack overflow (that is, they are using more than 8KB of stack memory), corrupting the stack memory of drivers that are loaded after them (such as the USB tuner drivers).
 
A simple way to verify this hypothesis would be to disable the internal tuners (so that the corresponding drivers are not loaded at all) and see if the errors on USB tuners disappears. Any suggestion on how to do this?

just gave it a try without loading the et9x00 drivers;
(# before the modules in /etc/modules)

and with a Terratec T stick black (using the realtek kernel patch), inserting it still results in an oops with the same trace

Call Trace:
[<80460000>] dvb_dmx_swfilter_packet+0x24/0x5e0
[<e020e47c>] dvb_usb_fe_sleep+0x0/0x80 [dvb_usb]
[<e020e4fc>] dvb_usb_fe_wakeup+0x0/0x8c [dvb_usb]
[<8034e7e4>] klist_class_dev_get+0x0/0x8
[<800c18d4>] kmem_cache_alloc+0xc0/0x104
[<e029f3ec>] rtl2832u_fe_attach+0x64/0xab4 [dvb_usb_rtl2832]
[<80460000>] dvb_dmx_swfilter_packet+0x24/0x5e0
[<e029f414>] rtl2832u_fe_attach+0x8c/0xab4 [dvb_usb_rtl2832]
[<8045bedc>] dvb_register_device+0x210/0x328
[<80460000>] dvb_dmx_swfilter_packet+0x24/0x5e0
[<e020e47c>] dvb_usb_fe_sleep+0x0/0x80 [dvb_usb]
[<e020e4fc>] dvb_usb_fe_wakeup+0x0/0x8c [dvb_usb]
[<e029a260>] rtl2832u_frontend_attach+0x20/0x38 [dvb_usb_rtl2832]
[<e020ec08>] dvb_usb_adapter_frontend_init+0xe0/0x1cc [dvb_usb]
[<805e6ef8>] printk+0x38/0x44
[<805e6ec0>] printk+0x0/0x44
[<800c0000>] dma_pool_create+0xc0/0x1e4
[<e0210000>] usb_urb_init+0x1c4/0x380 [dvb_usb]
[<e020dbc8>] dvb_usb_device_init+0x554/0x75c [dvb_usb]
[<e020d674>] dvb_usb_device_init+0x0/0x75c [dvb_usb]
[<e029a3ec>] rtl2832u_usb_probe+0xdc/0x1a4 [dvb_usb_rtl2832]
[<8040c210>] usb_match_id+0x6c/0x98
[<8004f2b4>] blocking_notifier_call_chain+0x14/0x20
[<8040c3d8>] usb_probe_interface+0xf8/0x234
[<8034d8a0>] driver_sysfs_add+0x78/0xac
[<8034dbc0>] driver_probe_device+0xa0/0x2bc
[<8040c2a0>] usb_device_match+0x64/0xa4
[<8034de98>] __driver_attach+0xbc/0xc4
[<8034bbc4>] next_device+0x10/0x30
[<8034dddc>] __driver_attach+0x0/0xc4
[<8034bf00>] bus_for_each_dev+0x5c/0xa8
[<8034d09c>] bus_add_driver+0x44/0x2b0
[<8034d20c>] bus_add_driver+0x1b4/0x2b0
[<8034e178>] driver_find+0x18/0x44
[<8034e234>] driver_register+0x90/0x1a0
[<8040b87c>] usb_register_driver+0x90/0x17c
[<80012600>] blast_dcache64+0x0/0xf8
[<e02f6000>] rtl2832u_usb_module_init+0x0/0x64 [dvb_usb_rtl2832]
[<e02f6030>] rtl2832u_usb_module_init+0x30/0x64 [dvb_usb_rtl2832]
[<8008d9f4>] free_hot_cold_page+0x30/0x220
[<800c198c>] kfree+0x18/0x150
[<80001588>] do_one_initcall+0x160/0x1e8
[<800b917c>] __vunmap+0xe4/0x128
[<8004f2b4>] blocking_notifier_call_chain+0x14/0x20
[<80073fcc>] load_module+0x1a1c/0x21b4
[<80070220>] ddebug_dyndbg_module_param_cb+0x0/0x3c
[<800711f8>] module_sect_show+0x0/0x18
[<80074818>] sys_init_module+0xb4/0xec
[<8000e07c>] stack_done+0x20/0x40
[<800c28a8>] sys_close+0x0/0x50

Sometimes I get a different one though (both with and without loading the xtrend drivers)

Call Trace:
[<802dea3c>] kobject_get+0x14/0xa4
[<803497b0>] get_device+0x14/0x2c
[<8034e7e4>] klist_class_dev_get+0x0/0x8

So the crash does not seem to be caused by the xtrend drivers.

In the first trace, it almost seems like module_init is called twice at the same time, as each function occurs twice.
(both times with a different code offset though).

[pieterg]

btw, this Terratec T stick black (0CCD:00A9) seems to be supported by the in-kernel rtl28xx driver nowadays;

opkg remove kernel-module-dvb-usb-rtl2832
opkg install kernel-module-dvb-usb-rtl28xxu

results in a working dvb-t tuner.

[pieterg]

one more observation, .init and .sleep are called too early, before the dvb_frontend_fops are initialized:

[<e1de5414>] rtl2832u_fe_attach+0x8c/0xab4 [dvb_usb_rtl2832]
[<8045bedc>] dvb_register_device+0x210/0x328
[<80460000>] dvb_dmx_swfilter_packet+0x24/0x5e0
[<e1d5447c>] dvb_usb_fe_sleep+0x0/0x80 [dvb_usb]
[<e1d544fc>] dvb_usb_fe_wakeup+0x0/0x8c [dvb_usb]
[<e1de0260>] rtl2832u_frontend_attach+0x20/0x38 [dvb_usb_rtl2832]

Before rtl2832u_frontend_attach is called, .init and .sleep still have their defaults assigned; dvb_usb_fe_wakeup and dvb_usb_fe_sleep.
rtl2832u_frontend_attach calls rtl2832u_fe_attach, which fills the dvb_frontend_ops to use rtl2832_init and rtl2832_sleep.
But before this has happened, .init and .sleep seem to be called already.
Even if this is not the cause of the crash itself, it certainly shows something fishy is going on during the init...

[guirigui]

I have installed the ET6000 20130520 image today from scratch
Everything is OK as usual CrossEPG/CoolTVguide/Device manager for USB HDD mounting.

I can only confirm the issue when attempting to install the RTL2832 dongle Twintech UT30 or UT40
Found side by side 2 entries RTL2832 & RTL28xxU..

Nothing works...

Edited by guirigui, 20 May 2013 - 14:55.

[Gennar1]

just gave it a try without loading the et9x00 drivers;
(# before the modules in /etc/modules)

and with a Terratec T stick black (using the realtek kernel patch), inserting it still results in an oops with the same traceSo the crash does not seem to be caused by the xtrend drivers.

In the first trace, it almost seems like module_init is called twice at the same time, as each function occurs twice.
(both times with a different code offset though).

 

Very interesting findings.

Please note that I compiled a 3.8 kernel for i386, applied the same driver patches and everything works fine, including dvb-usb and em28xx devices. So it's a MIPS related issue (given that the Xtrend drivers are not the cause).

 

I also tried to backport the em28xx driver to the version that was working in kernel 3.6, but the crashes are still there. The Realtek driver is exactly the same, and there has been no change in the dvb-usb framework between 3.6 and 3.8. The driver is surely doing something suspicious during init, but it works on x86 and used to work also on MIPS with the 3.6 kernel, so I don't think this is the cause.

 

All drivers are crashing during initialization, either trying to access a sub-dev connected through I2C (em28xx) or trying to start a swfilter (rtl2832).

 

I found a few recent bugfixes related to memory corruption/bad memory mapping on MIPS:

http://www.linux-mip...5/msg00048.html

http://patchwork.lin...org/patch/4994/

http://patchwork.lin...org/patch/4995/

 

I don't know if this may help...

[guirigui]

Hi,

I would like to get my RTL2832 back at work....

Please let us know wich ETxxxx image to choose(date?) before the Kernel 3.8.7 update.

Unfortunatly, I have not kept any image backup...

Thanks

[Gennar1]

I have installed the ET6000 20130520 image today from scratch
Everything is OK as usual CrossEPG/CoolTVguide/Device manager for USB HDD mounting.

I can only confirm the issue when attempting to install the RTL2832 dongle Twintech UT30 or UT40
Found side by side 2 entries RTL2832 & RTL28xxU..

Nothing works...

Remove the dvb-usb-rtl2832 driver (from Realtek) and try again with just the new dvb-usb-rtl28xxu (from kernel).

It should work, as the FC0012 tuner is supported by current kernel.