Moderator Control Panel ]

dvb device is not always discoverd by linux kernel

dvb device is not always discoverd by linux kernel

Postby schlussbilanz » Thu Dec 31, 2015 7:18 am

Hi,

i use the TBS6981 card since 2012 (i belive..) and now i have a problem with the card.
sometimes during power on the system the card is not discoved by the linux kernel.

i use the card with Ubuntu 14.04 amd64 and the latest tbs driver.

lspci output when its ok:
Code: Select All Code
~# lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
03:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 04)


lspci output when its not ok (device 03:00.0 fails):
Code: Select All Code
~# lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)


does anybody know this problem?
i have changed the mainboard but it doesn't solved the problem.
Is the tbs card broken?

Best regards
Schlussbilanz
schlussbilanz
 
Posts: 14
Joined: Thu Aug 09, 2012 4:11 am
Location: Germany

Re: dvb device is not always discoverd by linux kernel

Postby schlussbilanz » Thu Dec 31, 2015 7:21 am

Is there a way to check the tbs card on errors?
schlussbilanz
 
Posts: 14
Joined: Thu Aug 09, 2012 4:11 am
Location: Germany

Re: dvb device is not always discoverd by linux kernel

Postby schlussbilanz » Thu Dec 31, 2015 8:01 am

dmesg output:

Code: Select All Code
[    5.377404] TurboSight TBS 6981 Frontend:
[    5.377404]  tbs6981fe - command is not responding
[    5.377409] TurboSight TBS 6981 Frontend:
[    5.377409]  tbs6981fe - running software failed
[    5.378632] BUG: unable to handle kernel NULL pointer dereference at 00000000000000b0
[    5.378638] IP: [<ffffffffc0119059>] tbsfe_attach+0x9/0xfb0 [tbsfe]
[    5.378643] PGD 360d7067 PUD 36083067 PMD 0
[    5.378646] Oops: 0002 [#1] SMP
[    5.378648] Modules linked in: tbsfe(OE) rfcomm ir_lirc_codec(OE) lirc_dev(OE) ir_mce_kbd_decoder(OE) ir_sony_decoder(OE) bnep bluetooth ir_jvc_decoder(OE) tbs6981fe(POE) ir_rc6_decoder(OE) ir_rc5_decoder(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache joydev fglrx(POE) hid_generic snd_hda_codec_via snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel intel_rapl iosf_mbi x86_pkg_temp_thermal snd_hda_controller intel_powerclamp snd_hda_codec snd_hwdep kvm_intel kvm crct10dif_pclmul crc32_pclmul snd_pcm ghash_clmulni_intel cryptd snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq serio_raw snd_seq_device snd_timer snd ir_nec_decoder(OE) cx23885(OE+) videobuf_dvb(OE) btcx_risc(OE) tveeprom(OE) cx2341x(OE) videobuf_dma_sg(OE) videobuf_core(OE) dvb_core(OE) rc_core(OE) v4l2_common(OE) videodev(OE) v4l2_compat_ioctl32(OE) lpc_ich soundcore amd_iommu_v2 8250_fintek mei_me usbhid video mei shpchp hid mac_hid intel_smartconnect parport_pc ppdev w83627ehf hwmon_vid coretemp lp parport psmouse ahci r8169 libahci mii
[    5.378690] CPU: 1 PID: 377 Comm: systemd-udevd Tainted: P           OE  3.19.0-25-generic #26~14.04.1-Ubuntu
[    5.378692] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61 Pro BTC, BIOS P1.40 02/25/2014
[    5.378693] task: ffff880119546220 ti: ffff8800d83c8000 task.ti: ffff8800d83c8000
[    5.378695] RIP: 0010:[<ffffffffc0119059>]  [<ffffffffc0119059>] tbsfe_attach+0x9/0xfb0 [tbsfe]
[    5.378698] RSP: 0018:ffff8800d83cb938  EFLAGS: 00010286
[    5.378699] RAX: 0000000000000000 RBX: ffff880035cb0000 RCX: 0000000000000001
[    5.378700] RDX: 0000000000000001 RSI: ffffffffc011b278 RDI: 0000000000000000
[    5.378701] RBP: ffff8800d83cba98 R08: ffffffff810f2c00 R09: 00000001802a0023
[    5.378702] R10: ffffea0003651fc0 R11: ffffffff81089a54 R12: ffff880035cb1640
[    5.378703] R13: ffff880035ca9800 R14: 0000000000000000 R15: ffff880035cb161c
[    5.378705] FS:  00007f22da58e880(0000) GS:ffff88011ec80000(0000) knlGS:0000000000000000
[    5.378706] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    5.378707] CR2: 00000000000000b0 CR3: 000000003617f000 CR4: 00000000000407e0
[    5.378709] Stack:
[    5.378710]  ffff8800d83cba98 ffffffffc02561bf 0000000000000006 0000000000000032
[    5.378712]  0000000000000246 ffff880035cb1650 ffff8800d83cb9a8 ffffffff810ca248
[    5.378714]  0000000000000002 00000000ffffffff 0000000000000000 0000000000000000
[    5.378716] Call Trace:
[    5.378729]  [<ffffffffc02561bf>] ? dvb_register+0x3ef/0x2430 [cx23885]
[    5.378735]  [<ffffffff810ca248>] ? console_unlock+0x1f8/0x460
[    5.378738]  [<ffffffff810ca834>] ? vprintk_emit+0x384/0x520
[    5.378742]  [<ffffffff810cab39>] ? vprintk_default+0x29/0x40
[    5.378746]  [<ffffffffc021e1b6>] ? videobuf_queue_core_init+0x116/0x1f0 [videobuf_core]
[    5.378753]  [<ffffffffc02584c8>] cx23885_dvb_register+0x128/0x160 [cx23885]
[    5.378759]  [<ffffffffc024cf53>] ? cx23885_ir_init+0x263/0x2f0 [cx23885]
[    5.378765]  [<ffffffffc0252f6f>] cx23885_initdev+0xf6f/0x1300 [cx23885]
[    5.378770]  [<ffffffff813f1ef5>] local_pci_probe+0x45/0xa0
[    5.378773]  [<ffffffff813f3195>] ? pci_match_device+0xe5/0x110
[    5.378776]  [<ffffffff813f32d9>] pci_device_probe+0xd9/0x130
[    5.378781]  [<ffffffff814f547d>] driver_probe_device+0x12d/0x3e0
[    5.378784]  [<ffffffff814f580b>] __driver_attach+0x9b/0xa0
[    5.378787]  [<ffffffff814f5770>] ? __device_attach+0x40/0x40
[    5.378789]  [<ffffffff814f3383>] bus_for_each_dev+0x63/0xa0
[    5.378792]  [<ffffffff814f4e5e>] driver_attach+0x1e/0x20
[    5.378794]  [<ffffffff814f4a50>] bus_add_driver+0x180/0x240
[    5.378798]  [<ffffffffc0274000>] ? 0xffffffffc0274000
[    5.378800]  [<ffffffff814f5ff4>] driver_register+0x64/0xf0
[    5.378803]  [<ffffffff813f183c>] __pci_register_driver+0x4c/0x50
[    5.378808]  [<ffffffffc0274033>] cx23885_init+0x33/0x1000 [cx23885]
[    5.378811]  [<ffffffff81002144>] do_one_initcall+0xd4/0x210
[    5.378815]  [<ffffffff811cf219>] ? kmem_cache_alloc_trace+0x199/0x220
[    5.378819]  [<ffffffff810f7b1d>] ? load_module+0x162d/0x1ca0
[    5.378822]  [<ffffffff810f7b56>] load_module+0x1666/0x1ca0
[    5.378825]  [<ffffffff810f3420>] ? store_uevent+0x40/0x40
[    5.378829]  [<ffffffff810f8306>] SyS_finit_module+0x86/0xb0
[    5.378834]  [<ffffffff817b668d>] system_call_fastpath+0x16/0x1b
[    5.378835] Code: 8d 14 36 09 d0 c3 66 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 5d c3 0f 1f 44 00 00 66 66 66 66 90 55 48 89 f8 <48> c7 87 b0 00 00 00 40 90 11 c0 48 c7 87 50 01 00 00 00 90 11
[    5.378857] RIP  [<ffffffffc0119059>] tbsfe_attach+0x9/0xfb0 [tbsfe]
[    5.378859]  RSP <ffff8800d83cb938>
[    5.378860] CR2: 00000000000000b0
[    5.378862] ---[ end trace 73828906aaa03f37 ]---
[    6.167677] r8169 0000:02:00.0 eth0: link up
[    6.167688] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    6.243616] init: plymouth-stop pre-start process (1619) terminated with status 1
[    6.999690] cx25840: disagrees about version of symbol v4l2_i2c_subdev_init
[    6.999697] cx25840: Unknown symbol v4l2_i2c_subdev_init (err -22)
[    6.999711] cx25840: disagrees about version of symbol v4l2_subdev_queryctrl
[    6.999713] cx25840: Unknown symbol v4l2_subdev_queryctrl (err -22)
[    6.999730] cx25840: disagrees about version of symbol v4l2_subdev_s_ext_ctrls
[    6.999732] cx25840: Unknown symbol v4l2_subdev_s_ext_ctrls (err -22)
[    6.999759] cx25840: Unknown symbol v4l2_ctrl_handler_init_class (err 0)
[    6.999777] cx25840: disagrees about version of symbol v4l2_subdev_try_ext_ctrls
[    6.999779] cx25840: Unknown symbol v4l2_subdev_try_ext_ctrls (err -22)
[    6.999791] cx25840: disagrees about version of symbol v4l2_ctrl_handler_log_status
[    6.999793] cx25840: Unknown symbol v4l2_ctrl_handler_log_status (err -22)
[    6.999803] cx25840: disagrees about version of symbol v4l2_ctrl_handler_setup
[    6.999805] cx25840: Unknown symbol v4l2_ctrl_handler_setup (err -22)
[    6.999818] cx25840: disagrees about version of symbol v4l2_subdev_s_ctrl
[    6.999820] cx25840: Unknown symbol v4l2_subdev_s_ctrl (err -22)
[    6.999833] cx25840: disagrees about version of symbol v4l2_device_unregister_subdev
[    6.999835] cx25840: Unknown symbol v4l2_device_unregister_subdev (err -22)
[    6.999856] cx25840: disagrees about version of symbol v4l2_subdev_g_ext_ctrls
[    6.999858] cx25840: Unknown symbol v4l2_subdev_g_ext_ctrls (err -22)
[    6.999871] cx25840: disagrees about version of symbol v4l2_subdev_g_ctrl
[    6.999873] cx25840: Unknown symbol v4l2_subdev_g_ctrl (err -22)
[    6.999883] cx25840: disagrees about version of symbol v4l2_ctrl_new_std
[    6.999885] cx25840: Unknown symbol v4l2_ctrl_new_std (err -22)
[    6.999896] cx25840: disagrees about version of symbol v4l2_ctrl_handler_free
[    6.999898] cx25840: Unknown symbol v4l2_ctrl_handler_free (err -22)
[    6.999910] cx25840: disagrees about version of symbol v4l2_subdev_querymenu
[    6.999912] cx25840: Unknown symbol v4l2_subdev_querymenu (err -22)
[    6.999926] cx25840: disagrees about version of symbol v4l2_ctrl_cluster
[    6.999929] cx25840: Unknown symbol v4l2_ctrl_cluster (err -22)
schlussbilanz
 
Posts: 14
Joined: Thu Aug 09, 2012 4:11 am
Location: Germany

Re: dvb device is not always discoverd by linux kernel

Postby SergioDanielG » Thu Dec 31, 2015 10:54 am

Hi schlussbilanz,

Did you try putting your card in other pci-e slot?
Additionally, I'll try
1) reinstall tbs drivers.
2) check ram module with memtest.
3) check hard disk.

Kind regards.
SergioDanielG
 
Posts: 356
Joined: Tue May 31, 2011 3:53 am
Location: Tostado (SF) Argentina

Re: dvb device is not always discoverd by linux kernel

Postby schlussbilanz » Thu Dec 31, 2015 5:49 pm

Hi,

i've tried another pci-e slot without any result.
I will check the hard disk and ram modules.

Best regards
schlussbilanz
 
Posts: 14
Joined: Thu Aug 09, 2012 4:11 am
Location: Germany

Re: dvb device is not always discoverd by linux kernel

Postby schlussbilanz » Sat Jan 02, 2016 5:44 am

So..
i've tried the harddisk and the ram modules.. no errors

I think the card is broken :-(
schlussbilanz
 
Posts: 14
Joined: Thu Aug 09, 2012 4:11 am
Location: Germany

Re: dvb device is not always discoverd by linux kernel

Postby SergioDanielG » Sat Jan 02, 2016 10:13 am

Yes, It's possible. Did you try reinstalling tbs driver? (you don't mention it)

Kind regards
SergioDanielG
 
Posts: 356
Joined: Tue May 31, 2011 3:53 am
Location: Tostado (SF) Argentina

Re: dvb device is not always discoverd by linux kernel

Postby schlussbilanz » Wed Jan 13, 2016 2:59 am

yes, i tried to reinstall the driver and reinstall the ubuntu...
i think i buy a new card...
schlussbilanz
 
Posts: 14
Joined: Thu Aug 09, 2012 4:11 am
Location: Germany

Re: dvb device is not always discoverd by linux kernel

Postby knasher » Mon May 23, 2016 10:17 pm

I'm getting the exact same issue, the card is visible on some boots, but not others. I've tried moving the card to a different pci slot, reinstalling the drivers, upgrading the firmware to the version included in the blob, but nothing seemed to help.

I'm running on debian jessie, the latest drivers, and I have another dvb-t card from tbs installed as well.
knasher
 
Posts: 1
Joined: Tue May 17, 2016 9:05 pm


Return to Linux

Who is online

Users browsing this forum: No registered users and 6 guests

cron