This is an old revision of the document!
Query And Reports Pages
- [http://www.freebsd.org/cgi/query-pr.cgi GNATS Problem Report query ] webpage
- [http://www.freebsd.org/support/bugreports.html GNATS Problem Report Submission ] webpage
- [http://people.freebsd.org/~linimon/studies/prs/recentprs_day.html New PRs in the last 24 hours]; [http://people.freebsd.org/~linimon/studies/prs/recentprs_week.html New PRs in the last week]; [http://people.freebsd.org/~linimon/studies/prs/recentprs_month.html New PRs in the last month]. They are static and generated once a day for now.
- [http://people.freebsd.org/~linimon/studies/prs/stalefeedback.html PRs in the feedback state which have not been modified in 2 months]. That one is static and generated once a day for now.
- [http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html PRs recommended for committer evaluation by the bugbusting team]. That one is static and generated once a day for now.
- [http://people.freebsd.org/~linimon/studies/prs/pr_tag_index.html PRs indexed by tag]. That one is static and generated once a day for now.
- [http://people.freebsd.org/~linimon/studies/prs/prs_possibly_committed.html PRs which may have already been commited]. That one is static and generated once a day for now.
- [http://people.freebsd.org/~linimon/studies/prs/prs_for_tag_patch.html PRs with patches]. That one is static and generated once a day for now.
- [http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html Well-Known PRs as determined by the bugbusting team]. That one is static and generated once a day for now. (This one is new and includes commentary and analysis.)
How-Tos
- [http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/ Writing FreeBSD Problem Reports ]
- [http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pr-guidelines/ Problem Report Handling Guidelines ] (for FreeBSD contributors with access to GNATS)
- [wiki:self:KernelBugTriage Kernel Bug Report Triaging Guide ] (preliminary)
- Bugbusting [wiki:self:Bugbusting/TipsAndTricks Tips and Tricks ]
- How to deal with PRs that have been [wiki:self:Bugathons/patch flagged as having patches in them].
- [http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Kernel Debugging Guide ] in the [http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook Developer's Handbook ] * [http://www.bsdcan.org/2008/schedule/attachments/45_article.pdf Introduction to Debugging the FreeBSD Kernel] presented by JohnBaldwin at BSDCan 2008. Consider this to be recent extensions to the above. Recommended.
- [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html ACPI Debugging Guide ] in the Developer's Handbook. This is a good place to start if you are having problems with identifying hardware. (For instance, for many irq routing, hanging, device not accessible, panics, etc., you might want to see if disabling acpi fixes the problem in question. There are a large number of bad BIOS implementations out there; we put in hacks to work around as many as we can, but more are always needed.)
- Information about [“Debugging”] with gdb on FreeBSD
- Greg Lehey's [http://www.lemis.com/grog/Papers/Debug-tutorial/tutorial.pdf debugging tutorial]. This may not be as up-to-date as some of the above.
Email Resources
- The [http://docs.freebsd.org/mail/current/freebsd-bugbusters.html freebsd-bugbusters mailing list ] (for general discussion about bugbusting). Periodic postings include:
- Weekly posting of “PRs recommended for committer evaluation by the bugbusting team” (example: [http://docs.FreeBSD.org/cgi/mid.cgi?200801211115.m0LBF0rp050882 20080121 posting ])
- The [http://docs.freebsd.org/mail/current/freebsd-bugs.html freebsd-bugs mailing list ] (where incoming PRs for the kern, bin, and conf categories are posted, and sometimes discussion ensues). Periodic postings include:
- “Current problem reports” (example: [http://docs.FreeBSD.org/cgi/mid.cgi?200801211106.m0LB62f9045949 20080121 posting ])
- “Current problem reports containing patches” (example: [http://docs.FreeBSD.org/cgi/mid.cgi?200801211109.m0LB94Ul049051 20080121 posting ])
- “Current problem reports sorted by tag” (example: [http://docs.FreeBSD.org/cgi/mid.cgi?200801211109.m0LB99T2049059 20080121 posting ])
- Weekly emailed reminders of assigned PRs, to each assignee (including various mailing lists)
IRC Resources
- #freebsd-bugbusters IRC channel on EFNet
Other Wiki Resources
- Information about [“Bugathons”]
- [wiki:self:JeremyChadwick/Commonly_reported_issues Commonly Reported Issues] maintained by Jeremy Chadwick
- A list of committers willing to have PRs [wiki:self:AssigningPRs assigned to them]. (This is in addition to the auto-assigns to mailing lists, and for ports)
- [wiki:self:BugBusting/Volunteers signup sheet for volunteers]
- [wiki:self:BugBusting/HowToHelp how to help]
Resources For Committers
These scripts live on freefall. (See ~gnats/tools/README).
- ~gnats/tools/showwithtag: show PRs for tag <tag>
- ~gnats/tools/showwithpatches: show PRs for tag <patch>
- ~gnats/tools/show-random-pr: show a random PR for <tag> and <category>
- ~gnats/tools/show-random-unassigned-pr: show a random unassigned PR for <tag> and <category>
Metadiscussions
- [wiki:self:BugBusting/StateOfBugbusting The State of Bugbusting] talks about the state of bugbusting on FreeBSD, and discusses ideas for how we can improve.
- [http://people.freebsd.org/~linimon/presentations/prs2008/ FreeBSD Bugbusting: Where We Are, Where We Ought To Be]. This is MarkLinimon's presentation at [http://www.bsdcan.org BSDCan 2008], and includes some new analysis and ideas in addition to the above.
To-Do Items
- [wiki:self:MarkLinimon/ActionItems Mark Linimon's action items ]
- [wiki:self:PRsFor6.x PRs that only apply to 6.x]. Most of these only need MFCs.
Statistics
- [http://www.oook.cz/bsd/prstats/ GNATS PR statistics ] from pav
- [http://people.freebsd.org/~edwin/gnats/ GNATS PR statistics ] from edwin
Other Resources
- Auto-assignment of ports PRs (run by EdwinGroothuis)
- The bugmeister team, bugmeister@FreeBSD.org (responsible for the maintenance of the database and associated code)