Difference between revisions of "Bug Report"

From LinuxTVWiki
Jump to: navigation, search
(a quick merge of the content from V4L's "How to write good problem report" article, for user contribution history see: "V4L:How to write good problem report")
m (add note for current v4l list, some re-org, minor edits)
Line 1: Line 1:
If you find a bug please report it on the linux-dvb Mailing list. Please include all relevant information (what hardware, what environment) and try to provide a simple test case, this makes it much easier to sport down the actual problem.
+
If you find a bug please report it on:
 
+
* the linux-dvb Mailing list (for [[DVB]] devices) or
If you have an idea how to fix this bug please include the [[Bugfix]] in your mail.
+
* 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:
 
+
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
 
# 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
 
# identification of the device
# lspci -vnn  
+
# the output of lspci -vnn  
# Dmesg log of module tuning and probing. It also nice to add audio_debug options to modules, tuner_debug option to tuner module and debug option to tda9887
+
# 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.
 
# Television standard for your country.
 
# Television standard for your country.
 
# Exact sequence of actions that causes your problem.
 
# Exact sequence of actions that causes your problem.
# Generally, "your problem" is a combination of an app and a driver.  Also generally, the problem only exists in one of those, but it isn't always easy to tell where.  A big help is to check each part with various tools in the V4L [[Test Suite]].
+
 
 +
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]]).
 +
 
 +
Lastly, if you have an idea how to fix this bug please include the [[Bugfix]] in your email message!
  
  
 
[[Category:Development]]
 
[[Category:Development]]

Revision as of 02:51, 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 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:

  1. 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
  2. identification of the device
  3. the output of lspci -vnn
  4. 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.
  5. Television standard for your country.
  6. Exact sequence of actions that causes your 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).

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