Difference between revisions of "Bug Report"

From LinuxTVWiki
Jump to: navigation, search
m (add the skeleton bisect section)
Line 18: Line 18:
 
Lastly, if you have an idea how to fix this bug please include the [[Bugfix]] in your email message!
 
Lastly, if you have an idea how to fix this bug please include the [[Bugfix]] in your email message!
  
 +
 +
==Finding the source of the error via a Hg Bisect (i.e. being proactive and helping out)==
 +
The following needs to be done:
 +
* Describe what a bisect is (i.e. the concept) and then how to perform a bisect
 +
* [http://www.selenic.com/mercurial/wiki/index.cgi/BisectExtension Hg Bisect info]
  
 
[[Category:Development]]
 
[[Category:Development]]

Revision as of 02:41, 2 June 2009

If you find a bug please report it on:

Please include as much relevant information as possible to help diagnosis the problem. For example, a good problem report should include:

  1. identification of the device with which your having difficulty
  2. the device's subsystem ID, taken from the output of lspci -vnn (for PCI/PCIe devices) or lsusb -v (for USB based devices)
  3. the environment your running it under (e.g. Fedora 10, with kernel 2.6.27.5, 64-bit), and with what other hardware (e.g. ASUS Core 2 Duo motherboard)
  4. 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
  5. the relevant portions of your dmesg log showing module probing and/or tuning (if applicable). It also nice to add 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.
  6. cite the television standard applicable for your device (e.g. ATSC tuner card, PAL capture card)
  7. 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).

Lastly, if you have an idea how to fix this bug please include the Bugfix in your email message!


Finding the source of the error via a Hg Bisect (i.e. being proactive and helping out)

The following needs to be done:

  • Describe what a bisect is (i.e. the concept) and then how to perform a bisect
  • Hg Bisect info