Difference between revisions of "Bug Report"

From LinuxTVWiki
Jump to: navigation, search
m (add note for current v4l list, some re-org, minor edits)
(more refinements)
Line 2: Line 2:
 
* the linux-dvb Mailing list (for [[DVB]] devices) or
 
* the linux-dvb Mailing list (for [[DVB]] devices) or
 
* the linux-video mailing list (for [[V4L]] devices)
 
* the linux-video mailing list (for [[V4L]] devices)
Please include all relevant information (what hardware, what environment) and try to provide a simple test case, as this makes it much easier to track down the actual problem. A good problem report should include:
+
Please include as much relevant information as possible to help diagnosis the problem. For example, a good problem report should include:
# 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
+
# identification of the device with which your having difficulty
# identification of the device
+
# the output of lspci -vnn (for PCI/PCIe devices) or lsusb -v
# the output of lspci -vnn
+
# 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)
# the relevant portions of your dmesg log showing module probing and/or tuning. It also nice to add audio_debug options to modules, tuner_debug option to tuner module and debug option to tda9887, and then provide the dmesg output.
+
# 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  
# Television standard for your country.
+
# 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.
# Exact sequence of actions that causes your problem.
+
# 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 an app or the driver, 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]]).
+
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!
 
Lastly, if you have an idea how to fix this bug please include the [[Bugfix]] in your email message!

Revision as of 04:06, 31 December 2008

If you find a bug please report it on:

  • the linux-dvb Mailing list (for DVB devices) or
  • the linux-video mailing list (for V4L devices)

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 output of lspci -vnn (for PCI/PCIe devices) or lsusb -v
  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
  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!