User Tools

Site Tools


en:users:drivers:ath11k:bugreport

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:users:drivers:ath11k:bugreport [2021/02/11 19:10]
Kalle Valo Fix unclear sentence
en:users:drivers:ath11k:bugreport [2022/04/13 08:12] (current)
Kalle Valo Add a link to closed bugs, small cleanup to text.
Line 9: Line 9:
   * Component: network-wireless   * Component: network-wireless
   * Summary: start with string "​ath11k:"​   * Summary: start with string "​ath11k:"​
 +
 +Before filing see also the list of [[https://​bugzilla.kernel.org/​buglist.cgi?​bug_status=NEW&​bug_status=ASSIGNED&​bug_status=REOPENED&​list_id=1082403&​query_format=advanced&​short_desc=ath11k&​short_desc_type=allwordssubstr|open]] and [[https://​bugzilla.kernel.org/​buglist.cgi?​bug_status=RESOLVED&​bug_status=VERIFIED&​bug_status=REJECTED&​bug_status=DEFERRED&​bug_status=NEEDINFO&​bug_status=CLOSED&​list_id=1111073&​query_format=advanced&​short_desc=ath11k&​short_desc_type=allwordssubstr|closed]] ath11k bugs. 
  
 To make it easier for the developers to help, include in the bug report at least this information:​ To make it easier for the developers to help, include in the bug report at least this information:​
  
   * Exact kernel version. Is it a distro kernel or have you compiled it yourself? Any extra patches?   * Exact kernel version. Is it a distro kernel or have you compiled it yourself? Any extra patches?
 +  * Linux distribution version.
   * Host device information,​ for example if it's a laptop make and model, architecture,​ CPU etc.   * Host device information,​ for example if it's a laptop make and model, architecture,​ CPU etc.
   * BIOS version.   * BIOS version.
 +  * How many times have you seen the bug and how many times did you try to reproduce it? For example, the test failed 3 times out of 5 total times tested.
   * Output from: uname -a   * Output from: uname -a
   * Output from: lspci -mnn   * Output from: lspci -mnn
Line 20: Line 24:
   * Output from: dmesg | grep ath11k   * Output from: dmesg | grep ath11k
  
-See also [[https://​bugzilla.kernel.org/​buglist.cgi?​bug_status=NEW&​bug_status=ASSIGNED&​bug_status=REOPENED&​list_id=1082403&​query_format=advanced&​short_desc=ath11k&​short_desc_type=allwordssubstr|the list of open ath11k bugs]].+//Always open a new bug//, do not report your issue as a comment to an existing bug. Even if the symptoms are the same (eg. "​kernel freeze"​ or "​firmware crash"​),​ the actual bugs causing the issue might be very different. It's better that the developers do the analysis, and if it's really the same bug the developers will mark the report as duplicate. If people report their issues to an existing bug reports, it will become a mess for the developers to maintain them. 
 + 
 +https://​bugzilla.kernel.org ​is only for [[https://www.kernel.org/|upstream kernel.org releases]]. As distros (Ubuntu, Fedora etc) can modify ath11k on their own, and it's difficult to track what has changed, report bugs seen on distro kernels to the distro bug trackers
  
-Bugzilla is not actively followed by all developersso it'​s ​good idea to also send a short mail to [[en/​users/​Drivers/​ath11k/​mailinglist|the mailing list]]. Usually a post to the mailing list gathers more attention. Also questions should be sent to the mailing list.+Bugzilla is not a support forum, it is tool to collect and track actual bugs. All questions, comments and support requests should be sent to [[en/​users/​Drivers/​ath11k/​mailinglist|the mailing list]]. ​
  
 Patches are not submitted via bugzilla, see [[en/​users/​Drivers/​ath11k/​submittingpatches|Submitting patches]]. Patches are not submitted via bugzilla, see [[en/​users/​Drivers/​ath11k/​submittingpatches|Submitting patches]].
en/users/drivers/ath11k/bugreport.1613070644.txt.gz · Last modified: 2021/02/11 19:10 by Kalle Valo