On Mon, Apr 6, 2009 at 10:47 PM, Kemble Wagner <oobe.trouble@xxxxxxxxx> wrote:
---------- Forwarded message ----------
From: Kemble Wagner <oobe.trouble@xxxxxxxxx>
Date: Mon, Apr 6, 2009 at 1:23 AM
Subject: [Bug 229879] Re: My DVB-card is flooding the consol with "recv bulk message failed"
To: oobe.trouble@xxxxxxxxx
as mentioned im using 2.6.27-11-generic and as i said i havent had a
problem yet well the other day i did i experienced the same problems
that others here report including spam console etc. but i have not had
it before or since just chiming in to say that even when i have somthing
that i consider stable it still ends up like this on occasion so there
is yet to be a completely stable kernel or v4l-dvb tree on this matter.
it would be sensable if someone started a thread on the v4l-dvb mailing
list about this as ubuntu developers cannot fix this due to the fact
they only package the code that v4l-dvb produce which intern goes into
the kernel which distros then patch and package.
--
My DVB-card is flooding the consol with "recv bulk message failed"
https://bugs.launchpad.net/bugs/229879
You received this bug notification because you are a direct subscriber
of the bug."I also have this issue. I was originally running 7.10, then upgraded to
8.10 via 8.04. I think the suggestion from Kemble to post to the v4l-dvb
mailing list is sound. If the OP can create an initial posting I'll also
post to the same thread to highlight that this is affecting multiple
users."
Hello,
I am running Ubuntu 8.04 Server (amd64) and I have a "Devico FusionHDTV
DVB-T Dual Digital". It is a PCI-card but the second tuner is plugged
in thru USB2.
The first tuner (PCI-based) is working properly. I can tune signals,
watch livetv with it and I have not found any error messages when using
it alone. The PIC-tuner is located at "/dev/dvb/adapter0"
The second tuner is only found in cold state during boot and is not
activated. To solve that I had to download the "bluebird"-firmware from
http://www.linuxtv.org/downloads/firmware/dvb-usb-bluebird-01.fw and save it in /lib/firmware.
When I do a cold boot with the firmware available the second tuner (USB-tuner) is found but I sometimes receive this message during boot: "dvb-usb: bulk message failed: -71 (2/0)". The tuner is found and activated anyway and I see the second tuner as "/dev/dvb/adapter1" with the same nodes/files as the PCI-tuner (demux0, dvr0, frontend0, net0). I have not tried to use it yet.
When the computer has been online, idling, for some short random time (typically 10-15 minutes) I start to get floods of the following error message in the consol (typically one per second): "dvb-usb: bulk message failed: -110 (1/0)".
If I do a warm reboot I sometime reboot fine (without error messages shown at boottime) and sometimes with some similar error messages. I have seen "-71", "-22" and "-110".
During a forum-search I found this tread, but it does not seams related to my problem: http://ubuntuforums.org/showthread.php?t=373192
Bug #78949 seems to be related to this one, but its old and not for my hardware.
$ lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04
$ uname -a
Linux gandalf 2.6.24-16-server #1 SMP Thu Apr 10 13:15:38 UTC 2008 x86_64 GNU/Linux
- lspci -vv (17.1 KiB, text/plain)
- lsusb -vv (21.7 KiB, text/plain)
I found this tread and the post from 2007-12-15 looks intresting but I don't know if that is a sulotion for my card. http://www.itee.uq.edu.au/~chrisp/Linux-DVB/DVICO/
What is the defenition of "a newer card"?
I have a "FuionHDTV DVB-T Dual Digital" is that the same card as the post mention ("FusionHDTV DVB-T Dual Express")?
The new version of the firmware sounds interesting but is that one for my hardware or not?
The FusionHDTV DVT-T Dual Digital is different fromt he Dual Express - The Dual Express is a PCI-Express card
DVICO makes two USB/PCI cards - the Dual Digital (2), which has an actual USB port (that's the one I have, and i think the one you have?) and the dual digital 4 which has a pci -> usb bridge for the USB tuner.
I'm also running ubuntu 8.04 server and having the same problem Anders is having - the PCI tuner loads fine:
[ 67.505751] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
[ 67.505886] cx88[0]: subsystem: 18ac:db50, board: DViCO FusionHDTV DVB-T Dual Digital [card=44,autodetected]
[ 67.505889] cx88[0]: TV tuner type 4, Radio tuner type -1
[ 67.511394] cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
but the USB one gives error messages after it loads:
[ 69.092019] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in cold state, will try to load a firmware
[ 69.139716] dvb-usb: downloading firmware from file 'dvb-usb-bluebird-01.fw'
[ 69.236381] usb 2-3: USB disconnect, address 3
[ 69.240610] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
(so the firmware is loading fine, but then)
[ 71.057474] usb 2-3: new high speed USB device using ehci_hcd and address 4
[ 71.209202] usb 2-3: configuration #1 chosen from 1 choice
[ 71.209539] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in warm state.
[ 71.210596] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 71.220371] DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual USB)
[ 71.222823] DVB: registering frontend 1 (Zarlink MT352 DVB-T)...
[ 71.224278] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:02.1/usb2/2-3/input/input6
[ 71.257178] dvb-usb: schedule remote query interval to 150 msecs.
[ 71.257185] dvb-usb: DViCO FusionHDTV DVB-T Dual USB successfully initialized and connected.
[ 72.606458] dvb-usb: recv bulk message failed: -75
[ 82.039426] dvb-usb: bulk message failed: -71 (1/0)
[ 83.379617] dvb-usb: bulk message failed: -71 (1/0)
[ 84.057324] dvb-usb: bulk message failed: -71 (1/0)
[ 84.978737] dvb-usb: bulk message failed: -71 (1/0)
[ 85.730943] dvb-usb: bulk message failed: -71 (1/0)
[ 86.242278] dvb-usb: bulk message failed: -71 (1/0)
[ 87.117679] dvb-usb: bulk message failed: -71 (1/0)
[ 87.357889] dvb-usb: bulk message failed: -71 (1/0)
[ 88.003277] dvb-usb: bulk message failed: -71 (1/0)
... and so on.
I'm going to try the desktop kernel as i notice Anders is also running the server kernel. Will post my findings shortly.
Interestingly enough, the bulk message problems don't show up under the generic kernel until i actually try to tune a channel, but the same errors show up and I am still unable to tune anything.
I also think bug 93695 is related
I too have a Dvico dual digital card, and can confirm that it likes to spam the console.
In my case, it manifested itself by slowing down my keyboard responses to sometimes waiting seconds before all my keys appeared in the console at once (is it requiring a lot of kernel interrupts?)
It took a while for the drivers for this to become stable when I was using fedora about 18 months ago, and had to compile them from source, but after that, they worked well.
If I remember right, all I had to do for ubuntu was to install the firmware for the card, and after that, it was all fine... until, now. I have definately noticed it since 8.04, but it may have existed in 7.10 as well.
Here are some bits of the system log that alerted me to the problem:
{{{
898.916822] dvb-usb: bulk message failed: -110 (5/0)
[128899.915577] dvb-usb: bulk message failed: -110 (5/0)
[128900.914732] dvb-usb: bulk message failed: -110 (5/0)
[128901.913500] dvb-usb: bulk message failed: -110 (1/0)
[128902.912306] dvb-usb: bulk message failed: -110 (5/0)
[128903.911558] dvb-usb: bulk message failed: -110 (5/0)
[128904.909919] dvb-usb: bulk message failed: -110 (5/0)
[128905.908790] dvb-usb: bulk message failed: -110 (1/0)
[128906.907713] dvb-usb: bulk message failed: -110 (5/0)
[128907.906397] dvb-usb: bulk message failed: -110 (5/0)
[128908.905360] dvb-usb: bulk message failed: -110 (5/0)
[128909.903821] dvb-usb: bulk message failed: -110 (1/0)
[128910.902627] dvb-usb: bulk message failed: -110 (5/0)
[128911.901683] dvb-usb: bulk message failed: -110 (5/0)
[128912.900577] dvb-usb: bulk message failed: -110 (5/0)
[128913.899364] dvb-usb: bulk message failed: -110 (1/0)
[128914.898236] dvb-usb: bulk message failed: -110 (5/0)
[128915.896978] dvb-usb: bulk message failed: -110 (5/0)
[128916.895805] dvb-usb: bulk message failed: -110 (5/0)
[128917.894643] dvb-usb: bulk message failed: -110 (1/0)
[128918.893449] dvb-usb: bulk message failed: -110 (5/0)
[128919.892255] dvb-usb: bulk message failed: -110 (5/0)
[128920.891060] dvb-usb: bulk message failed: -110 (5/0)
[128921.889928] dvb-usb: bulk message failed: -110 (1/0)
[128922.888736] dvb-usb: bulk message failed: -110 (5/0)
[128923.887529] dvb-usb: bulk message failed: -110 (5/0)
[128925.365044] dvb-usb: bulk message failed: -110 (5/0)
[128926.505461] dvb-usb: bulk message failed: -110 (1/0)
[128927.504135] dvb-usb: bulk message failed: -110 (5/0)
[128928.503084] dvb-usb: bulk message failed: -110 (5/0)
[128929.501941] dvb-usb: bulk message failed: -110 (5/0)
[128930.500736] dvb-usb: bulk message failed: -110 (1/0)
[128931.499536] dvb-usb: bulk message failed: -110 (5/0)
[128932.498348] dvb-usb: bulk message failed: -110 (5/0)
[128933.497205] dvb-usb: bulk message failed: -110 (5/0)
[128934.496009] dvb-usb: bulk message failed: -110 (1/0)
[128935.494565] dvb-usb: bulk message failed: -110 (5/0)
[128936.493489] dvb-usb: bulk message failed: -110 (5/0)
[128937.492552] dvb-usb: bulk message failed: -110 (5/0)
[128938.950128] dvb-usb: bulk message failed: -110 (1/0)
}}}
Once reconnected, it caused lsusb to lock up, and I couldn't ctrl-c out of it.
Once I reboot the system, I'll see if I can get better system logs and lsusb o...
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.
| linux status: | New → Incomplete |
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!
| linux status: | Incomplete → Invalid |
What information is missing? I have not seen anyone asking for more information, other than me.
I own one of this cards and will help you with outputs and testing of the hardware if anyone tells me what to do.
Please, don't close/ignore this bug, it's not fixed. The USB-part of the hardware is not working.
Hello Anders,
Thank you for your interest in this bug.
The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Jaunty Jackalope. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.
| linux status: | Invalid → Incomplete |
I also have a DVICO Dual Digital 4 (PCI, not PCIe) and am running amd64 architecture. I'm running Mythbuntu 8.04 - I'm assuming this is based on the desktop kernel. My card identifies itself as 0fe9:db78 in lsusb. I set it up based on the instructions shown here: http://ubuntuforums.org/showthread.php?t=616103 and it works. However, I have a similar problem to that which Anders describes.
Frequently when I do a warm boot, the system exhibits similar behaviour:
- I get the "dvb-usb: bulk message failed: -110" at a frequency of about once a second
- I get similar keyboard issues with my usb keyboard (press k once and I get a dozen or so: "kkkkkkkkkkkkkkkkkk")
The only way I can get my system back to 'normal' again is to remove the dvb_usb_cxusb module:
modprobe -r dvb_usb_cxusb
of course I have to stop the mythbackend first.Doing all this is very difficult when every few keypresses get repeated a heap of times. Especially when I have to login as root to do it. Though my system is now usable, the tuner card won't work (not without that module I just removed) so I have to reboot for me to use the system as intended.
I could live with the issue on warm reboot; I just have to shutdown, wait a bit, then start up again. However, the system has recently started doing it whenever I shut down the mythbackend (for configuration for instance), and when I tested connecting with XBMC from another machine it did it as well.
Based on the forum thread I followed to set the card up, this seems to be a known issue among users of the card, but it's a royal pain in the neck and it would be great if it got fixed some time. I'm happy to provide additional information if that would be of assistance.
Cheers.
you could try using building a vanilla kernel thats what i used on 8.04 and
now im using intrepid i have no problems with the stock kernel 2.6.27-11
On Thu, Mar 12, 2009 at 8:36 PM, Jimbot <jkennon1@xxxxxxxxx> wrote:
this is affecting me too.
I can avoid it by shutting down for time instead of restarting...
What information could I collect to cast more light on it?
has anyone tried installing newer v4l-dvb drivers
sudo -i
apt-get update
apt-get install install mercurial build-essential linux-headers-`uname -r`
hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
make && make install
exit
or as i mentioned above dowloading the newest kernel from http://kernel.org and compiling it youself will also fix this
http://www.howtoforge.com/kernel_compilation_ubuntu
i for one can say that this used to fix the trouble for me however now in intrepid the stock kernel works fine for me.
Unfortunately, even with the latest v4l-dvb drivers I too experience those bulk errors in the log
They show up every 2 seconds
as mentioned im using 2.6.27-11-generic and as i said i havent had a problem yet well the other day i did i experienced the same problems that others here report including spam console etc. but i have not had it before or since just chiming in to say that even when i have somthing that i consider stable it still ends up like this on occasion so there is yet to be a completely stable kernel or v4l-dvb tree on this matter.
it would be sensable if someone started a thread on the v4l-dvb mailing list about this as ubuntu developers cannot fix this due to the fact they only package the code that v4l-dvb produce which intern goes into the kernel which distros then patch and package.
I also have this issue. I was originally running 7.10, then upgraded to 8.10 via 8.04. I think the suggestion from Kemble to post to the v4l-dvb mailing list is sound. If the OP can create an initial posting I'll also post to the same thread to highlight that this is affecting multiple users.
_______________________________________________ linux-dvb users mailing list For V4L/DVB development, please use instead linux-media@xxxxxxxxxxxxxxx linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Is there anyone that can help me with this bug, please?
Here is some more information I've discoverd.
When I try to install Mythbuntu 8.04 (amd64) with the usb-adapter installed my keyborard acts wierd. First the keyboard acts normal (while the DVB-adapter is in normal state) and when the adapter starts to flood error-messages the keyboard takes aproximately 5seconds for each keypress and at some random time the keyboard flood inputs when a key is pressed (if I press "k" I get "kkkkkkkkkkkkkkkkkkkkkkkkkkkkk" of random length). After the install I end up with a corrupt disk (Grub Error 5 after reboot from LiveCD).
This is a very serious problem for me and I need help to solve it.
Another thing to know is that Mythbuntu comes bundled with the firmware on the LiveCD and that causes this behaivor by default. Ubuntu does not have the firmware loaded by default.