Issues with DSM 5.0-4458 Update 1

[cyrill]

Hi

I've just updated to the newest DSM version 5.0-4458 Update 1 (2014/03/26). And it seems that the DVBLink package / TVSource 4.7.0 9733 is having issues. I'm using a TBS DVB-C stick on a DS1010+ which is still properly recognized but whenever it's being accessed e.g. for recording or channel scan it fails and crashes the whole package (e.g. the website is not available anymore).

Here's the dmesg output after attaching the device

Code: Select all

[   76.262597] media: Linux media interface: v0.10
[   76.327840] Linux video capture interface: v2.00
[   76.332494] WARNING: You are using an experimental version of the media stack.
[   76.332498]  As the driver is backported to an older kernel, it doesn't offer
[   76.332502]  enough quality for its usage in production.
[   76.332504]  Use it with care.
[   76.332506] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
[   76.332510]  7d459937dc09bb8e448d9985ec4623779427d8a5 [media] Add driver for Samsung S5K5BAF camera sensor
[   76.332514]  2310e3c41a71f3db88039aabbd8c9ab5a4d57e65 [media] Add DT binding documentation for Samsung S5K5BAF camera sensor
[   76.332519]  347f7a3763601d7b466898d1f10080b7083ac4a3 [media] subdev autoselect only works if I2C and I2C_MUX is selected
[   76.483986] WARNING: You are using an experimental version of the media stack.
[   76.483990]  As the driver is backported to an older kernel, it doesn't offer
[   76.483993]  enough quality for its usage in production.
[   76.483996]  Use it with care.
[   76.483997] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
[   76.484000]  7d459937dc09bb8e448d9985ec4623779427d8a5 [media] Add driver for Samsung S5K5BAF camera sensor
[   76.484003]  2310e3c41a71f3db88039aabbd8c9ab5a4d57e65 [media] Add DT binding documentation for Samsung S5K5BAF camera sensor
[   76.484006]  347f7a3763601d7b466898d1f10080b7083ac4a3 [media] subdev autoselect only works if I2C and I2C_MUX is selected
[   76.563153] WARNING: You are using an experimental version of the media stack.
[   76.563161]  As the driver is backported to an older kernel, it doesn't offer
[   76.563165]  enough quality for its usage in production.
[   76.563169]  Use it with care.
[   76.563171] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
[   76.563175]  7d459937dc09bb8e448d9985ec4623779427d8a5 [media] Add driver for Samsung S5K5BAF camera sensor
[   76.563180]  2310e3c41a71f3db88039aabbd8c9ab5a4d57e65 [media] Add DT binding documentation for Samsung S5K5BAF camera sensor
[   76.563185]  347f7a3763601d7b466898d1f10080b7083ac4a3 [media] subdev autoselect only works if I2C and I2C_MUX is selected
[   76.877135] usbcore: registered new interface driver em28xx
[   76.898050] Em28xx: Initialized (Em28xx dvb Extension) extension
[   77.020321] usbcore: registered new interface driver dvb_usb_ttusb2
[   77.202270] usbcore: registered new interface driver dvb_usb_dib0700
[   77.309888] au0828 driver loaded
[   77.313672] usbcore: registered new interface driver au0828
[   77.371743] usbcore: registered new interface driver dw2102
[   77.478502] usbcore: registered new interface driver pctv452e
[   77.518168] usbcore: registered new interface driver tbsqbox2ci
[   77.574378] usbcore: registered new interface driver tbsdvbc
[   77.599174] usbcore: registered new interface driver tbs5680
[   77.638332] usbcore: registered new interface driver tbsqbox22
[   77.661440] usbcore: registered new interface driver Abilis Systems as10x usb driver
[   80.522840] init: synoindexd main process (12850) killed by TERM signal
[   80.903035] init: synomkthumbd main process (12872) killed by TERM signal
[   81.180770] init: synomkflvd main process (12879) killed by TERM signal
[   83.366414] usbcore: registered new interface driver snd-usb-audio
[   83.447728] usbcore: registered new interface driver snd-usb-hiface
[   86.757572] init: synoindexd main process (13884) killed by HUP signal
[   86.764354] init: synoindexd main process ended, respawning
[   86.840539] init: synomkthumbd main process (13895) killed by HUP signal
[   86.847512] init: synomkthumbd main process ended, respawning
[   86.936833] init: synomkflvd main process (13909) killed by HUP signal
[   86.944291] init: synomkflvd main process ended, respawning
[  155.223788] usbcore: deregistering interface driver snd-usb-hiface
[  155.276096] usbcore: deregistering interface driver snd-usb-audio
[  180.081592] init: crond main process (5030) killed by TERM signal
[  181.682101] init: smbd main process (10419) killed by TERM signal
[  233.607882] usbcore: registered new interface driver snd-usb-audio
[  233.685629] usbcore: registered new interface driver snd-usb-hiface
[  399.680073] usb 2-6: new high-speed USB device number 3 using ehci_hcd
[  399.821384] Got empty serial number. Generate serial number from product.
[  399.831885] usbip 2-6:1.0: Enter
[  399.831897] usbip 2-6:1.0: 2-6 is not in match_busid table... skip!
[  399.838410] dvb-usb: found a 'TBS DVBC USB2.0' in cold state, will try to load a firmware
[  400.069742] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-dvbc.fw'
[  400.116839] tbsdvbc: start downloading TBSDVBC firmware
[  400.240038] dvb-usb: found a 'TBS DVBC USB2.0' in warm state.
[  400.246559] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  400.259042] DVB: registering new adapter (TBS DVBC USB2.0)
[  400.272743] tbsdvbc: read eeprom failed.
[  400.276697] dvb-usb: MAC address reading failed.
[  400.290781] tbsdvbcfe: attach failed : 80
[  400.294873] dvb-usb: no frontend was attached by 'TBS DVBC USB2.0'
[  400.309611] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.7/usb2/2-6/input/input0
[  400.320140] dvb-usb: schedule remote query interval to 150 msecs.
[  400.326328] dvb-usb: TBS DVBC USB2.0 successfully initialized and connected.
[  400.333836] usb 2-6: USB disconnect, device number 3
[  400.347637] dvb-usb: TBS DVBC USB2.0 successfully deinitialized and disconnected.
[  401.882035] usb 2-6: new high-speed USB device number 4 using ehci_hcd
[  402.024919] usbip 2-6:1.0: Enter
[  402.024934] usbip 2-6:1.0: 2-6 is not in match_busid table... skip!
[  402.031319] dvb-usb: found a 'TBS DVBC USB2.0' in cold state, will try to load a firmware
[  402.068748] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-dvbc.fw'
[  402.114799] tbsdvbc: start downloading TBSDVBC firmware
[  402.243102] dvb-usb: found a 'TBS DVBC USB2.0' in warm state.
[  402.251071] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[  402.259751] DVB: registering new adapter (TBS DVBC USB2.0)
[  402.495377] dvb-usb: MAC address: ff:ff:ff:ff:ff:ff
[  402.529154] tbsdvbc: Attached TBSDVBCFE!
[  402.529161]
[  402.535193] usb 2-6: DVB: registering adapter 0 frontend 0 (TurboSight TBS DVBC frontend)...
[  402.545961] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.7/usb2/2-6/input/input1
[  402.556520] dvb-usb: schedule remote query interval to 150 msecs.
[  402.562694] dvb-usb: TBS DVBC USB2.0 successfully initialized and connected.


And this is what happens when I try to perform a scan

Code: Select all

[  936.077387] BUG: unable to handle kernel paging request at ffff8804dff35dc8
[  936.078333] IP: [<ffffffffa03eb514>] dvb_usb_fe_wakeup+0x44/0x70 [dvb_usb]
[  936.078333] PGD 1807063 PUD 0
[  936.078333] Oops: 0000 [#1] SMP
[  936.078333] CPU 3
[  936.078333] Modules linked in: snd_usb_hiface(O) snd_pcm_oss(O) snd_mixer_oss(O) snd_usb_audio(O) snd_pcm(O) snd_timer(O) snd_hwdep(O) snd_usbmidi_lib(O) snd_rawmidi(O) snd_seq_device(O) snd(O) snd_page_alloc(O) soundcore dvb_as102(O) dvb_usb_tbsqbox22(O) tbs5922fe(P) dvb_usb_tbs5680(O) dvb_usb_tbsdvbc(O) tbsdvbcfe(P) tbs5680fe(P) dvb_usb_tbsqbox2ci(O) stv090x(O) dvb_usb_pctv452e(O) stb6100(O) stb0899(O) lnbp22(O) ttpci_eeprom(O) dvb_usb_dw2102(O) ds3000(O) ts2020(O) au0828(O) au8522_dig(O) au8522_decoder(O) au8522_common(O) xc5000(O) s5h1411(O) dvb_usb_dib0700(O) dib9000(O) dib0070(O) dib7000p(O) dib0090(O) dib7000m(O) dib8000(O) dib3000mc(O) dibx000_common(O) dvb_usb_ttusb2(O) dvb_usb(O) tda827x(O) tda10048(O) tda10023(O) em28xx_dvb(O) em28xx(O) a8293(O) tda10071(O) m88ds3103(O) m88ts2022(O) tda18271(O) cxd2820r(O) videobuf2_vmalloc(O) videobuf2_memops(O) videobuf2_core(O) tuner(O) rc_core(O) dvb_core(O) v4l2_common(O) videobuf_vmalloc(O) videobuf_core(O) videodev(O) media(O) tveeprom(O) cifs udf isofs loop usbip(C) usbip_common_mod(C) usbhid hid usblp usb_storage uhci_hcd etxhci_hcd xhci_hcd ehci_hcd pineview_synobios(P) synoacl_vfs(P) zlib_deflate libcrc32c hfsplus md4 hmac i2c_algo_bit fuse vfat fat ecryptfs sha512_generic sha256_generic sha1_generic ecb aes_x86_64 authenc chainiv des_generic crc32c eseqiv krng ansi_cprng cts rng aes_generic md5 cbc cryptomgr pcompress aead crypto_hash crypto_blkcipher crypto_wq crypto_algapi cpufreq_stats freq_table dm_snapshot crc_itu_t crc_ccitt quota_v2 quota_tree usbcore psnap p8022 llc usb_common ipv6 zram(C) sg [last unloaded: soundcore]
[  936.078333]
[  936.078333] Pid: 25939, comm: kdvb-ad-0-fe-53 Tainted: P         C O 3.2.40 #4458 To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M.
[  936.078333] RIP: 0010:[<ffffffffa03eb514>]  [<ffffffffa03eb514>] dvb_usb_fe_wakeup+0x44/0x70 [dvb_usb]
[  936.078333] RSP: 0018:ffff880091943e30  EFLAGS: 00010202
[  936.078333] RAX: 00000004801806a8 RBX: ffff88005fdb5130 RCX: ffff8800be8d29c8
[  936.078333] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8800b620a010
[  936.078333] RBP: ffff8800b620a010 R08: ffff880091942000 R09: 0000000000000000
[  936.078333] R10: 0000000000000001 R11: 0000000000000000 R12: ffffffffa0351840
[  936.078333] R13: ffff8800a17be5b8 R14: 0000000000000000 R15: 0000000000000000
[  936.078333] FS:  0000000000000000(0000) GS:ffff8800bf580000(0000) knlGS:0000000000000000
[  936.078333] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  936.078333] CR2: ffff8804dff35dc8 CR3: 0000000074657000 CR4: 00000000000006e0
[  936.078333] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  936.078333] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  936.078333] Process kdvb-ad-0-fe-53 (pid: 25939, threadinfo ffff880091942000, task ffff8800be87a5e0)
[  936.078333] Stack:
[  936.078333]  ffff8800bf590780 ffff8800b620a010 ffff8800a17be400 ffffffffa034f352
[  936.078333]  ffff8800b620a010 ffffffffa03518a0 ffff880091943ef0 ffffffff813ff658
[  936.078333]  ffff880091943ec0 ffffffff00000000 ffff8800be87a5e0 ffff880091943fd8
[  936.078333] Call Trace:
[  936.078333]  [<ffffffffa034f352>] ? dvb_frontend_init+0x12/0x60 [dvb_core]
[  936.078333]  [<ffffffffa03518a0>] ? dvb_frontend_thread+0x60/0x4a0 [dvb_core]
[  936.078333]  [<ffffffff813ff658>] ? __schedule+0x248/0x620
[  936.078333]  [<ffffffffa0351840>] ? dvb_frontend_open+0x380/0x380 [dvb_core]
[  936.078333]  [<ffffffff810532f0>] ? kthread+0x80/0x90
[  936.078333]  [<ffffffff81402ef4>] ? kernel_thread_helper+0x4/0x10
[  936.078333]  [<ffffffff81053270>] ? kthread_worker_fn+0x160/0x160
[  936.078333]  [<ffffffff81402ef0>] ? gs_change+0xb/0xb
[  936.078333] Code: 00 03 00 00 48 8b 58 38 48 8b 3b e8 a7 ee ff ff be 01 00 00 00 48 89 ef e8 3a fd ff ff 48 63 85 00 05 00 00 48 69 c0 68 01 00 00 <48> 8b 84 03 f0 05 00 00 48 85 c0 74 05 48 89 ef ff d0 48 8b 5c
[  936.078333] RIP  [<ffffffffa03eb514>] dvb_usb_fe_wakeup+0x44/0x70 [dvb_usb]
[  936.078333]  RSP <ffff880091943e30>
[  936.078333] CR2: ffff8804dff35dc8
[  936.078333] ---[ end trace cb8d745bc160d3d3 ]---


[Oberon]

We are aware of the issue and are working on it together with TBS.
The current workaround is to reboot NAS without while keeping the stick connected. This should solve the issue until the following tuner disconnect/NAS power down.

[Double T]

Oberon,

Any update on this issue with the TBS tuner driver?
Just had a similar issue / crash, see attached dmesg output file.

[Double T]

Oberon,

Any update on this issue with the TBS tuner driver?
Just had a similar issue / crash, see attached dmesg output file.

Nice, even restarting the NAS (with tuners attached) did not resolve the issue... see next dmesg file...
All tuners start ok, but at the moment that I request via the client to tune to a specific channel, the driver crashes...

This happened 3x in a row: restart NAS, tune request, crash, restart NAS etc

I also noticed that after updating to DSM 5.0 as well as to DVBLing 4.7.0, that the tuners (all 3x) become really hot; even when not watching TV....
Since all 3 tuners show similar behavior... this can't be a manufacturing/quality issue

In the end, resolved it by disconnecting the tuners (power), restart of NAS (at the moment that the NAS was back up, the tuners were cool again (~5 min), stop DVBLink, reconnect the power to the tuners and restart DVBlink...

[Oberon]

TBS has become a bit unresponsive to our queries at the moment unfortunately. It might help if you write an e-mail to support at tbsdtv.com and euro_support at tbsdtv.com stating that you need their help to rebuild drivers for new Synology NAS platform.

[cyrill]

Ok thanks. I just sent them an e-mail, I'll report back when I receive a reply.

[Double T]

TBS has become a bit unresponsive to our queries at the moment unfortunately. It might help if you write an e-mail to support at tbsdtv.com and euro_support at tbsdtv.com stating that you need their help to rebuild drivers for new Synology NAS platform.

Oberon, I contacted TBS regarding the issues I observed... both by posting on their forum http://www.tbsdtv.com/forum/viewtopic.php?f=81&t=8929 as well as via a mail to both mentioned accounts..

Attached the feedback I received..
In short, they are in contact with DVBlogic to solve the issues and point towards a issue between the DSM 5.0 kernel with the driver.
However, they lack the knowledge of NAS based systems / DSM 5.0 to really go into details...

In the meantime I installed DVBLink 4.7.0 build 9919, which is working reasonable stable; no driver crashed observed yet
I have to admit: after the update to build 9919, I did not yet restart the NAS

[Oberon]

They do not need to have any knowledge on DSM5 or NAS. They just have to either rebuild the drivers (they know how to do it) or let us rebuild them. Neither have happened already for months

[Mirage-1]

Hi
are there any update on this topic ?

i m facing issues since i update to DSM 5 and DVB-Link to 4.7.0 build 9919
i already did a new installation for DVBLink from scratch but still have following issue:

- no response or freeze of DVBLink Web pages. restart of services don t help. Restart of server solve it for some time.
- Nightly shutdown of Syno fails (hang up).

i assume it is the TBS driver ?
Any other ideas ?

Thanks

Env:
DS211 /DSM 5.0-4458 Update 2

TT-connect CT-3650 CI - TechnoTrend AG
TBS 5680 - TBS Technologies

DVBLink 4.7.0 build 9919
TV-Source 9919
EPG Data Loader 9733

[Oberon]

Yes, looks like a driver crash to me. Can you please examine dmesg output next time it happens to see if there is indeed a crash?
As for driver rebuild - no it did not happen yet. You are welcome to write an e-mail to TBS support (support at tbsdtv.com and euro_support at tbsdtv.com) and ask about the status.

[Mirage-1]

Thanks for the quick feedback.

Sorry i m not familiar how to get a dmesg output.
can you give me a brief walk through or is there a howto you can reference for help ?

Thanks in advance
Udo

[Oberon]

It is a bit complex process for non-expert users unfortunately.
In a nutshel you need to enable ssh access on your NAS in the control panel, install putty client on your WIndows machine, connect to NAS, login with user root and your administrative password and then type dmesg on the command line. Copy as much of output as you can and paste it into a text file, attach the zipped file here.

[lfpommes]

Dear Customer support,
I run in the same issue - willl be be a fix available in future.
I bought the license as well as the dvb stick from dvblink and it does not work. I tried restart as well as reinstall. Is the problem the new kernel used by synologic?
I have seen the wake up of the usb, thats all.

I hope I will get an update from your supplier to fix the problem.

Thanks in advance...

[the_man]

Dear Customer support,
I run in the same issue - willl be be a fix available in future.
I bought the license as well as the dvb stick from dvblink and it does not work. I tried restart as well as reinstall. Is the problem the new kernel used by synologic?
I have seen the wake up of the usb, thats all.

I hope I will get an update from your supplier to fix the problem.

Thanks in advance...

it is desirable that you have created a new topic in more detail and describe your system and the error that occurred