• GNATS Problem Report query webpage
• GNATS Problem Report Submission webpage
• New PRs in the last 24 hours; New PRs in the last week; New PRs in the last month. They are static and generated once a day for now.
• PRs in the feedback state which have not been modified in 2 months. That one is static and generated once a day for now.
• PRs recommended for committer evaluation by the bugbusting team. That one is static and generated once a day for now.
• PRs indexed by manpage. That one is static and generated once a day for now.
• PRs indexed by tag. That one is static and generated once a day for now.
• PRs which may have already been commited. That one is static and generated once a day for now.
• PRs with patches. That one is static and generated once a day for now.
• 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.)

• Writing FreeBSD Problem Reports
• Problem Report Handling Guidelines (for FreeBSD contributors with access to GNATS)
• Kernel Bug Report Triaging Guide (preliminary)
• Bugbusting Tips and Tricks
• How to deal with PRs that have been flagged as having patches in them.
• Kernel Debugging Guide in the Developer's Handbook
• Introduction to Debugging the FreeBSD Kernel presented by JohnBaldwin at BSDCan 2008. Consider this to be recent extensions to the above. Recommended.
• 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 debugging tutorial. This may not be as up-to-date as some of the above.

• The 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: 20080121 posting)
• The 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: 20080121 posting)
  • “Current problem reports containing patches” (example: 20080121 posting)
  • “Current problem reports sorted by tag” (example: 20080121 posting)
• Weekly emailed reminders of assigned PRs, to each assignee (including various mailing lists)

• #freebsd-bugbusters IRC channel on EFNet

• Information about Bugathons
• Commonly Reported Issues maintained by Jeremy Chadwick
• A list of committers willing to have PRs assigned to them. (This is in addition to the auto-assigns to mailing lists, and for ports)
• signup sheet for volunteers
• how to help

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>

• The State of Bugbusting talks about the state of bugbusting on FreeBSD, and discusses ideas for how we can improve.
• FreeBSD Bugbusting: Where We Are, Where We Ought To Be. This is MarkLinimon's presentation at BSDCan 2008, and includes some new analysis and ideas in addition to the above.

• Mark Linimon's action items
• PRs that only apply to 6.x. Most of these only need MFCs.

• GNATS PR statistics from pav
• GNATS PR statistics from edwin

• Auto-assignment of ports PRs (run by EdwinGroothuis)
• The bugmeister team, bugmeister@FreeBSD.org (responsible for the maintenance of the database and associated code)
• Mirroring GNATS