Moderator Control Panel ]

Kernel oops when running tvheadend

Kernel oops when running tvheadend

Postby tordyvel » Fri Nov 16, 2012 3:00 am

HW:
- Asrock ION 330HT-BD
- Tuner TBS5922
SW:
- Openelec with kernel 3.6.6
- tvheadend 3.1.694 (I've tried earlier versions with same result)
- TBS Linux driver v121105 (I've tried with earlier versions with the same result)

At start the tuner loads it's firmware everything looks fine.
However when I enable tvheadend I get a kernel oops.
If i restart without the tuner tvheadend starts normally, although inserting the tuner again will not make it available in tvheadend.

Has anyone else seen this or have a workaround?

[ 8.360491] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in cold state, will try to load a firmware
[ 8.378850] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 20
[ 8.378909] hda_intel: Disabling MSI
[ 8.379561] snd_hda_intel 0000:00:08.0: setting latency timer to 64
[ 8.408439] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5922.fw'
[ 8.413733] tbsqbox22: start downloading TBSQBOX firmware
[ 8.534344] ACPI: PCI Interrupt Link [LN3A] enabled at IRQ 19
[ 8.540091] dvb-usb: found a 'TBS QBOX22 DVBS2 USB2.0' in warm state.
[ 8.540710] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 8.541124] DVB: registering new adapter (TBS QBOX22 DVBS2 USB2.0)
[ 8.584573] ath: EEPROM regdomain: 0x60
[ 8.584583] ath: EEPROM indicates we should expect a direct regpair map
[ 8.584594] ath: Country alpha2 being used: 00
[ 8.584599] ath: Regpair used: 0x60
[ 8.592411] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[ 8.594059] Registered led device: ath9k-phy0
[ 8.594082] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc90004e60000, irq=19
[ 8.710127] dvb-usb: MAC address: 00:22:ab:c0:24:05
[ 8.737887] tbs5922fe: module license 'TurboSight Proprietary: http://www.tbsdtv.com' taints kernel.
[ 8.737898] Disabling lock debugging due to kernel taint
[ 9.040085] TurboSight TBS 5922 Frontend Attaching...
[ 9.081011] QBOX22: TBS5922FE attached.
[ 9.112238] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 9.126366] DVB: registering adapter 0 frontend 0 (TurboSight TBS 5922 DVBS/S2 frontend)...
[ 9.131894] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:04.1/usb1/1-6/input/input6
[ 9.132260] dvb-usb: schedule remote query interval to 150 msecs.
[ 9.132277] dvb-usb: TBS QBOX22 DVBS2 USB2.0 successfully initialized and connected.
[ 9.132388] usbcore: registered new interface driver tbsqbox22
[ 9.547330] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:08.0/input/input7
[ 10.323812] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.0/sound/card0/input8
[ 10.324219] input: HDA NVidia Line as /devices/pci0000:00/0000:00:08.0/sound/card0/input9
[ 10.324842] input: HDA NVidia Mic as /devices/pci0000:00/0000:00:08.0/sound/card0/input10
[ 10.325508] input: HDA NVidia Line Out CLFE as /devices/pci0000:00/0000:00:08.0/sound/card0/input11
[ 10.326149] input: HDA NVidia Line Out Surround as /devices/pci0000:00/0000:00:08.0/sound/card0/input12
[ 10.327351] input: HDA NVidia Line Out Front as /devices/pci0000:00/0000:00:08.0/sound/card0/input13
[ 10.332341] ACPI: PCI Interrupt Link [LPMU] enabled at IRQ 23
[ 10.333404] ACPI: PCI Interrupt Link [SGRU] enabled at IRQ 22
[ 10.333470] nvidia 0000:01:00.0: setting latency timer to 64
[ 10.333484] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[ 10.334469] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 304.60 Sun Oct 14 20:23:00 PDT 2012
[ 14.426557] EXT4-fs (sda1): recovery complete
[ 14.426578] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 14.565842] EXT4-fs (sdc1): re-mounted. Opts: data=ordered,commit=0
[ 15.546748] EXT4-fs (sdb1): recovery complete
[ 15.546764] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 17.764963] EXT4-fs (sdc2): re-mounted. Opts: data=ordered,commit=0
[ 17.775548] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
[ 17.780215] EXT4-fs (sdb1): re-mounted. Opts: data=ordered,commit=0
[ 117.186167] BUG: unable to handle kernel NULL pointer dereference at 0000000000000038
[ 117.186182] IP: [<ffffffffa0064d59>] dvb_usb_fe_sleep+0xd/0x45 [dvb_usb]
[ 117.186200] PGD 0
[ 117.186206] Oops: 0000 [#1] SMP
[ 117.186212] Modules linked in: nvidia(PO) snd_hda_codec_hdmi snd_hda_codec_realtek tbsfe(O) tbs5922fe(PO) ath9k ath9k_common ath9k_hw snd_hda_intel dvb_usb_tbsqbox22(O) snd_hda_codec ath dvb_usb(O) snd_hwdep snd_pcm snd_timer snd snd_page_alloc coretemp nuvoton_cir(O) xhci_hcd uvesafb
[ 117.186249] CPU 3
[ 117.186259] Pid: 1698, comm: kdvb-ad-0-fe-0 Tainted: P O 3.6.6 #1 To Be Filled By O.E.M. To Be Filled By O.E.M./AMCP7AION-HT
[ 117.186265] RIP: 0010:[<ffffffffa0064d59>] [<ffffffffa0064d59>] dvb_usb_fe_sleep+0xd/0x45 [dvb_usb]
[ 117.186276] RSP: 0018:ffff8800b7677e30 EFLAGS: 00010282
[ 117.186281] RAX: 0000000000000000 RBX: ffff8800b6208c10 RCX: 0000000000000000
[ 117.186285] RDX: ffff8800b7677fd8 RSI: ffff8800b62f4cd0 RDI: ffff8800b6208c10
[ 117.186290] RBP: ffff8800b6208c10 R08: ffff8800b7676000 R09: 0000000000000000
[ 117.186294] R10: 0000000000000400 R11: 0000000000000003 R12: ffff8800b7677e88
[ 117.186298] R13: ffffffff81416cee R14: 0000000000000000 R15: 0000000000000000
[ 117.186304] FS: 0000000000000000(0000) GS:ffff8800bfd80000(0000) knlGS:0000000000000000
[ 117.186308] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 117.186312] CR2: 0000000000000038 CR3: 000000000180b000 CR4: 00000000000007a0
[ 117.186317] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 117.186321] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 117.186326] Process kdvb-ad-0-fe-0 (pid: 1698, threadinfo ffff8800b7676000, task ffff8800b62f4cd0)
[ 117.186329] Stack:
[ 117.186333] ffff8800b7677fd8 ffff8800b6208c10 ffff8800b6208c10 ffffffff81415a00
[ 117.186341] ffff8800b6208400 ffffffff81416d6e ffff8800b62f4cd0 ffff8800ba8cab40
[ 117.186349] 0000000000000000 ffffffff815750b5 ffff8800bf0fb8d0 0000000000000000
[ 117.186357] Call Trace:
[ 117.186371] [<ffffffff81415a00>] ? dvb_frontend_init+0x3e/0x7d
[ 117.186378] [<ffffffff81416d6e>] ? dvb_frontend_thread+0x80/0x563
[ 117.186388] [<ffffffff815750b5>] ? __schedule+0x361/0x379
[ 117.186395] [<ffffffff81416cee>] ? dvb_frontend_swzigzag+0x259/0x259
[ 117.186402] [<ffffffff81416cee>] ? dvb_frontend_swzigzag+0x259/0x259
[ 117.186411] [<ffffffff81039360>] ? kthread+0x68/0x70
[ 117.186419] [<ffffffff815773b4>] ? kernel_thread_helper+0x4/0x10
[ 117.186427] [<ffffffff810392f8>] ? kthread_freezable_should_stop+0x3c/0x3c
[ 117.186434] [<ffffffff815773b0>] ? gs_change+0xb/0xb
[ 117.186437] Code: 01 48 89 fb 74 0c 48 8d bf 88 0d 00 00 e8 2a 8d 38 e1 83 a3 40 0d 00 00 fe 31 c0 5b c3 90 55 53 48 89 fb 52 48 8b 87 e8 02 00 00 <48> 8b 68 38 48 63 87 b0 03 00 00 48 8b 84 c5 58 05 00 00 48 85
[ 117.186515] RIP [<ffffffffa0064d59>] dvb_usb_fe_sleep+0xd/0x45 [dvb_usb]
[ 117.186525] RSP <ffff8800b7677e30>
[ 117.186528] CR2: 0000000000000038
[ 117.186533] ---[ end trace 9210ff4110a8dad1 ]---
tordyvel
 
Posts: 5
Joined: Fri Aug 10, 2012 3:58 am

Re: Kernel oops when running tvheadend

Postby SergioDanielG » Fri Nov 16, 2012 8:25 am

Hi tordyvel.
Did you try tbs6925 with other software like szap-s2 or kaffeine or vlc?
Did you try starting your pc with tbs5922 conected or conecting tbs5922 and restarting tvheadend?
When tvheadend is running, this have listed dvb adapters in "Configuration -> TV Adapters"?

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

Re: Kernel oops when running tvheadend

Postby tordyvel » Fri Nov 16, 2012 1:52 pm

Hi and thanks for the reply,
I haven't tried the tuner with other software on the OpenELEC distribution.
It's a minimal distribution with small possibilities to add packages...

I've tested to have the tuner connected at boot and enable tvheadend, kernel oops.
I've tested to have the tuner disconnected at boot, later connect it and enable tvhedend, kernel oops.
I've tested to enable tvheadend, later connect the tuner (no oops but the tuner doesn't show up in tvheadend), restart tvheadend, kernel oops.

Whenever tvheadend finds the tuner a kernel oops occure which will also crash tvheadend.
Thanks
TordYvel
tordyvel
 
Posts: 5
Joined: Fri Aug 10, 2012 3:58 am

Re: Kernel oops when running tvheadend

Postby cody » Wed Nov 21, 2012 11:07 pm

does it work with other application than tvheadend like 'szap-s2' and 'scan-s2' included in the driver package? have you tested the box in other Linux installation. there are no any other similar complains and thus the only other thing i can suggest is to clean all DVB drivers from your installation with:

# rm -rf /lib/modules/<kernel_version>/kernel/drivers/media/

where of course "<kernel_version>" is replaced to correspond the correct path in your Linux installation and then re-install the drivers with "make install".
cody
 
Posts: 627
Joined: Tue Apr 13, 2010 11:20 pm

Re: Kernel oops when running tvheadend

Postby tordyvel » Fri Nov 23, 2012 2:23 pm

The distro I'm using is OpenELEC which cross compiles on another machine and creates an image to load.
So there is little options to adjust anything on target.

I've now tried with Ubuntu 12.10 and compiled the same drivers (this time on target) and using a slightly newer tvheadend (3.2.18) and now it works.

I'll try to add that tvheadend version to my OpenELEC image.

I still want to use OpenELEC though since it's a very stripped distro which ease the load on my Asrock 330.
I'd like an comment on what has happend leading up to the oops (maybe i'ts been called in an erronous way).
Thanks
tordyvel
 
Posts: 5
Joined: Fri Aug 10, 2012 3:58 am


Return to Linux

Who is online

Users browsing this forum: No registered users and 2 guests