DVB tuner (dib0700) not work on karmic

Bug #429662 reported by sebseb01
100
This bug affects 16 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
Baltix
New
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Medium
Unassigned
Nominated for Karmic by sebseb01

Bug Description

At first usage of my dvb card this show in my dmesg : (it's correctly work on jaunty)

[10593.069580] BUG: unable to handle kernel NULL pointer dereference at 00000008
[10593.069595] IP: [<c03a3e23>] _request_firmware+0x1f3/0x250
[10593.069612] *pde = 00000000
[10593.069619] Oops: 0000 [#1] SMP
[10593.069628] last sysfs file: /sys/devices/virtual/net/pan0/statistics/collisions
[10593.069635] Modules linked in: binfmt_misc ppdev bridge stp bnep lp parport snd_hda_codec_nvhdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm arc4 snd_seq_dummy ecb snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer iwlagn iwlcore snd_seq_device mac80211 snd joydev tuner_xc2028 soundcore nvidia(P) cfg80211 snd_page_alloc uvcvideo videodev v4l1_compat jmb38x_ms memstick sdhci_pci sdhci led_class dvb_usb_dib0700 dib7000p dib7000m dvb_usb dvb_core dib3000mc dibx000_common dib0070 btusb psmouse serio_raw r8169 mii fbcon tileblit font bitblit softcursor i915 drm i2c_algo_bit video output intel_agp agpgart
[10593.069764]
[10593.069772] Pid: 4882, comm: kdvb-ad-0-fe-0 Tainted: P (2.6.31-10-generic #32-Ubuntu)
[10593.069780] EIP: 0060:[<c03a3e23>] EFLAGS: 00010202 CPU: 0
[10593.069787] EIP is at _request_firmware+0x1f3/0x250
[10593.069792] EAX: 00000000 EBX: f6595200 ECX: 00000001 EDX: c06feb34
[10593.069798] ESI: c070fbe0 EDI: eaff91c0 EBP: eaf01d30 ESP: eaf01cfc
[10593.069804] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[10593.069811] Process kdvb-ad-0-fe-0 (pid: 4882, ti=eaf00000 task=eac8b240 task.ti=eaf00000)
[10593.069816] Stack:
[10593.069819] 80000300 f6ba0c00 000000c0 03400000 00000006 eaf01d69 00000006 00000000
[10593.069835] <0> eaf01d94 f82e7062 f667ae80 00000000 00000000 eaf01d3c c03a3f22 00000001
[10593.069852] <0> eaf01dcc f98db741 eaf01e78 f82e785b 00000002 00000002 f73ec6a8 f73ec000
[10593.069871] Call Trace:
[10593.069890] [<f82e7062>] ? dib0700_ctrl_wr+0x52/0x70 [dvb_usb_dib0700]
[10593.069899] [<c03a3f22>] ? request_firmware+0x12/0x20
[10593.069912] [<f98db741>] ? load_all_firmwares+0x61/0x6b0 [tuner_xc2028]
[10593.069925] [<f82e785b>] ? dib0700_i2c_xfer_legacy+0x17b/0x1a0 [dvb_usb_dib0700]
[10593.069939] [<f82e7062>] ? dib0700_ctrl_wr+0x52/0x70 [dvb_usb_dib0700]
[10593.069952] [<f82e785b>] ? dib0700_i2c_xfer_legacy+0x17b/0x1a0 [dvb_usb_dib0700]
[10593.069963] [<f98dc68b>] ? check_firmware+0x45b/0x870 [tuner_xc2028]
[10593.069975] [<c0136bdd>] ? update_curr+0x21d/0x230
[10593.069985] [<c0310494>] ? rb_erase+0xb4/0x120
[10593.069997] [<f98dcb05>] ? generic_set_freq+0x65/0x500 [tuner_xc2028]
[10593.070011] [<f82e789b>] ? dib0700_i2c_xfer+0x1b/0x30 [dvb_usb_dib0700]
[10593.070021] [<c0437744>] ? i2c_transfer+0x94/0xc0
[10593.070033] [<f82d0074>] ? dib7000p_write_word+0x54/0x70 [dib7000p]
[10593.070045] [<f98dd275>] ? xc2028_set_params+0x185/0x276 [tuner_xc2028]
[10593.070055] [<c0569825>] ? schedule_timeout+0x185/0x200
[10593.070067] [<f82d229b>] ? dib7000p_set_frontend+0x4b/0x170 [dib7000p]
[10593.070078] [<c014bb45>] ? try_to_del_timer_sync+0x45/0x50
[10593.070102] [<f8298a41>] ? dvb_frontend_swzigzag_autotune+0x111/0x260 [dvb_core]
[10593.070113] [<c0137a17>] ? try_to_wake_up+0xf7/0x350
[10593.070122] [<c056af53>] ? _spin_lock_irq+0x13/0x20
[10593.070146] [<f8299601>] ? dvb_frontend_swzigzag+0x1d1/0x260 [dvb_core]
[10593.070168] [<f829a007>] ? dvb_frontend_thread+0x387/0x630 [dvb_core]
[10593.070178] [<c0157930>] ? autoremove_wake_function+0x0/0x40
[10593.070200] [<f8299c80>] ? dvb_frontend_thread+0x0/0x630 [dvb_core]
[10593.070208] [<c015763c>] ? kthread+0x7c/0x90
[10593.070215] [<c01575c0>] ? kthread+0x0/0x90
[10593.070223] [<c0103f17>] ? kernel_thread_helper+0x7/0x10
[10593.070228] Code: 00 00 00 c7 44 24 04 d0 80 00 00 89 fa 89 34 24 ff 55 e0 83 45 e4 04 8b 45 e4 8b 00 85 c0 89 45 e0 75 d6 e9 52 fe ff ff 8b 45 e8 <8b> 70 08 e8 a5 69 ff ff 89 5c 24 0c 89 74 24 08 89 44 24 04 c7
[10593.070326] EIP: [<c03a3e23>] _request_firmware+0x1f3/0x250 SS:ESP 0068:eaf01cfc
[10593.070338] CR2: 0000000000000008
[10593.070346] ---[ end trace 90332185c87bab54 ]---

during boot I view this message
[ 6.010897] dvb-usb: found a 'YUAN High-Tech STK7700PH' in warm state.
[ 6.010925] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 7.095532] dvb-usb: schedule remote query interval to 50 msecs.
[ 7.095535] dvb-usb: YUAN High-Tech STK7700PH successfully initialized and connected.
[ 7.095686] usbcore: registered new interface driver dvb_usb_dib0700

arky (arky)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi sebseb01,

Can you also attach your full dmesg output after trying to use this card. Also attaching your lsusb information would be good too. Thanks.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
sebseb01 (sebseb01) wrote :
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
sebseb01 (sebseb01) wrote :

Hi,

I send all asked file.

Thanks

Revision history for this message
sebseb01 (sebseb01) wrote :
Revision history for this message
sebseb01 (sebseb01) wrote :
Changed in linux:
status: Unknown → Confirmed
Revision history for this message
Devin Heitmueller (devin-heitmueller) wrote :

What product is the original user encountering this issue with? I submitted a PULL request on the linux-media mailing list for this earlier in the week, and want to confirm that it will address this particular product as well.

http://<email address hidden>/msg10242.html

Assuming that it addresses this particular dib0700 device as well, it would be trivial to backport this into stable.

Revision history for this message
Edouard PELLERIN (edouardp) wrote :

Just tried the patch from upstream (posted by sebseb01) on a pinnacle 320cx express card, and everything is working as expected. I recompiled the whole V4L-DVB stack from mercurial, and the patch was already applied. Could we expect this to make it in karmic final ? (or even a backport later ?)

Revision history for this message
Devin Heitmueller (devin-heitmueller) wrote :

djh - I got the fix merged upstream into v4l-dvb earlier in the week. Whether the Ubuntu maintainers want to backport the one-line fix to Karmic is entirely at their discretion.

Revision history for this message
Patrick Byrne (pjlbyrne) wrote :

This bug affects me too. Can anyone say whether the fix will be released for 9.10? How can I tell when it becomes avaiable, please?

Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Patrick Byrne (pjlbyrne) wrote :

Seems to have gone away on lucid with the latest kernel update. I have working DVB-T in VLC. Perhaps this bug can be closed now?

[ now if somebody can fix the NEXT bug (#361322) we can use totem for tv....... ]

Revision history for this message
sebseb01 (sebseb01) wrote :

I'm using me-tv and totem, I still have this kernel-oups ! I'll try it on vlc later

(kernel 2.6.31-16-generic)

Revision history for this message
Devin Heitmueller (devin-heitmueller) wrote :

The patch went into the kernel.org 2.6.31.7 stable, which was just released yesterday. Hence it's not surprising that it hasn't made it's way into Karmic yet.

When the Ubuntu guys pull in the latest upstream source, this fix will be in there.

Devin

Revision history for this message
Devin Heitmueller (devin-heitmueller) wrote :

I guess I should have checked my "kernel-team" email first: The upstream 2.6.31.7 got pulled in about two hours ago, so I suspect there should be a package available shortly.

Devin

Revision history for this message
Patrick Byrne (pjlbyrne) wrote :

..in my earlier post I forgot to indicate that I had to enable karmic 'proposed' updates to get the fix. sorry if I misled anyone.

Revision history for this message
embe (beeri) wrote :

Is there anything more needed? Still not working on my laptop.

I made today fresh installation of Koala. Because of this problem I returned to Jackalope. There I installed "ubuntu restricted extra", copied "xc3028-v27.fw" to /lib/firmware and provide dvb-channels.conf to Totem and Me-Tv. It works.

Now I am again back in Koala. I tried same things as in Jackalope and I updated all packages with proposed enabled ( 2.6.31-17 is 2.6.31.7?). TV is not working. According to dmesg and lsusb here, I should have same device. (Bus 002 Device 003: ID 1164:1f08 YUAN High-Tech Development Co., Ltd )

My dmesg is different. I am not sure if it is same bug. I am sending whole dmesg. After 75s I tried to run DVB in Totem. After 878s I enabled "Firmware for DVB cards" in Ubuntu Proprietary Driver managment (my translation) and I tried again Totem.

Please let me know if there is anything more needed to be done. Thank you.

Revision history for this message
embe (beeri) wrote :
Revision history for this message
Devin Heitmueller (devin-heitmueller) wrote :

Hello Embe,

The linux-image 2.6.31.17 package still contains the mainline 2.6.31.6, which does not include the fix. As soon as they release a package that includes the mainline 2.6.31.7, you should get the fix.

Devin

Revision history for this message
suntinel (suntinel-deactivatedaccount1) wrote :

Anything new with this situation? I am missing MeTV :(

Revision history for this message
aschalk (andreasschalk) wrote :

Hi, i just "worked around" that case by installing the 2.6.32 kernel from lucid on karmic (i'm using xubuntu)

You can find it here:
http://packages.ubuntu.com/search?keywords=linux-image&searchon=names&suite=lucid&section=all

Revision history for this message
Devin Heitmueller (devin-heitmueller) wrote :

I fixed this months ago (and got it merged upstream). If Ubuntu hasn't sucked in the backport, then you need to be complaining (it was merged into the kernel.org mainline 2.6.31.6).

You shouldn't have needed to install the Lucid kernel, assuming you are running the latest Karmic updates.

Devin

Revision history for this message
Devin Heitmueller (devin-heitmueller) wrote :
Revision history for this message
Devin Heitmueller (devin-heitmueller) wrote :

If people are still seeing this issue, they should make sure they are running the latest Karmic kernel update, and post the following:

The exact revision of the linux-image package they have installed
The full dmesg output including the oops.

Devin

Revision history for this message
Patrick Byrne (pjlbyrne) wrote :

I got the fix in 9.10, by turning on 'proposed updates' at least 2 months ago. Presumably this is in the main repository now for 9.10.

..and it worked!

Revision history for this message
suntinel (suntinel-deactivatedaccount1) wrote :

Just a dumb question. I am not sure - but does this fix cover the problem, that for example MeTV was not able to scan any channels (it hangs always up). And does this mean the Gigabyte U8000 (dib0700) should work now out-of-the-box ?
Thx

Revision history for this message
Patrick Byrne (pjlbyrne) wrote : Re: [Bug 429662] Re: DVB tuner (dib0700) not work on karmic

I don't know about MeTV, but the behaviour you described sounds like
what I saw with w_scan & scan - and that has now been fixed.

On 7 February 2010 03:25, suntinel <email address hidden> wrote:
> Just a dumb question. I am not sure - but does this fix cover the problem, that for example MeTV was not able to scan any channels (it hangs always up). And does this mean the Gigabyte U8000 (dib0700) should work now out-of-the-box ?
> Thx
>
> --
> DVB tuner (dib0700) not work on karmic
> https://bugs.launchpad.net/bugs/429662
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Patrick Byrne

Revision history for this message
suntinel (suntinel-deactivatedaccount1) wrote :

Hi,

i've tried aschalk's solution installing the lucid kernel on karmic. It works fine with Gigabyte U8000 and MeTV.

More detailed instructions here:

http://ubuntuforums.org/showthread.php?t=1339809

Revision history for this message
Patrick Byrne (pjlbyrne) wrote :
Changed in linux:
importance: Unknown → Medium
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
Changed in linux:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.