If you find a bug please report it on:
Information You Should Provide When Reporting a Bug
Please include as much relevant information as possible to help diagnosis the problem. For example, a good problem report should include:
- identification of the device with which you are having difficulty
- the device's subsystem ID, taken from the output of lspci -vnn (for PCI/PCIe devices) or lsusb -v (for USB based devices)
- the environment your running it under (e.g. Fedora 10, with kernel 220.127.116.11, 64-bit), and with what other hardware (e.g. ASUS Core 2 Duo motherboard)
- a note of whether you're using the built in kernel drivers supplied by your distro or if you have installed the v4l-dvb driver set, or those from one of the LinuxTV developers' repos
- the relevant portions of your dmesg log showing module probing and/or tuning (if applicable). It is also nice if you have added module debug options (for example: audio_debug, tuner_debug, tda9887 debug etc etc) for the driver module in question, and then provide the dmesg output.
- cite the television standard applicable for your device (e.g. ATSC tuner card, PAL capture card)
- Exact sequence of actions that causes your problem. If it is possible, try to provide a simple reproducible test case, as this makes it much easier to track down the actual problem.
Generally, "your problem" will likely be related to a driver, an app, or a combination of the two. It isn't always easy to tell where the exact problem lies. A big help is to check each part with various tools (for example, with analogue devices, you can try those in the V4L Test Suite).
You may also wish to seek the opinion of other users at the following mailing lists (though, they are largely deprecated now in favour of the LMML)
- the linux-dvb Mailing List (subscribers only) (for DVB devices) or
- the video4linux Mailing List (for V4L devices)
Alternatively, you may wish to draw attention to this or seek help through one of the irc.freenode.net channels (#v4l or #linuxtv or #dvb)
Finding the source of the error via git bisect (i.e. being proactive and helping out)
When a driver used to work on earlier versions of the Kernel, but doesn't work on newer ones, that means that a regression happened. Finding what change broke a driver is not easy, and usually need to be done by someone with the hardware. Thankfully, the tool used to handle patches at the Kernel (git) has a tool to allow identifying what change broke a driver. It is called git bisect.
You could get more info about that and how to use at:
Once the broken patch is identified, please report about that at the Linux-Media Mailing List.
Lastly, if you know or have an idea as to how to fix this bug, please submit a patch for it to the LMML.