From Fedora Project Wiki
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

Quick links to bug lists

Possibly fixed in CURRENTRELEASE (Stick for prodding sleeping bugs with)

If the bug is against a previous point release kernel, and the reporter hasn't re-tested (this type of bugs must be set in NEEDINFO_REPORTER state):

Thank you for taking the time to report this bug. Updates to the kernel have been released since it was first reported. If you have time to update the package and re-test, please do so and report the results here. You can obtain the updated package by typing 'yum update kernel' or using the graphical updater, Software Update. If the problem no longer exists then please close this bug or it will be closed in a few weeks if there is no additional information lodged.

Installer bugs

If the bug refers to problems when installing Fedora in any of the possible ways CD, DVD, USB, network, etc (this type of bugs must be set in NEEDINFO_REPORTER state):

Thank you for taking the time to report this bug. Bugs involving the installation process cannot usually be resolved after release date. We therefore ask reporters to use one (or both) of the following options:
1. Test with a Fedora Unity re-spin. These can be found at and include updates for installer bugs which may resolve the problem for you.
2. Test with an Alpha, Beta or Release Candidate for the next version. These can be found at and by testing these we can work to resolve any installation issues so that the final release is free of such bugs.
However if the problem no longer exists then please close this bug or it will be closed in a few weeks if there is no additional information lodged.
Outdated fedoraunity spins
The spins at fedoraunity are not updated since 2010-03-03.
get-prerelease link
The get-prerelease link sometimes is not available or have not updated development releases.

Video Subsystem bugs

The various video subsystems that have kernel modesetting support would just prefer their bugs to be moved over to the xorg-x11-drv-{intel|nouveau|ati} component. There, their triagers can gather needed info and debug the issue. If the problem is in the kernel, those maintainers can fix it, no need to leave the bug assigned to the kernel.

This bug is in a video subsystem that has a kernel part. We track and work on these bugs via the driver package name instead of leaving them assigned to the kernel

NEW state bugs

If the bug is new and (this type of bugs must be key-worded in either WHITEBOARD or BLOCKER): Hello,

Thank you for taking the time to report this bug. I have added the proper keyword to this bug to bring it to the attention of the <subsystem-name> subsystem maintainer.
Can you attach the following information to this bug:

Then pick the info that is useful in this case:

  • smolt profile
  • dmesg output from boot before issue.
  • dmesg output after issue.
  • dmesg output from boot with 'quiet' option replaced with 'debug'
  • lspci output
  • lsusb output

For other necessary information check:

Bugs with TAINTED modules

Certain bug reports refer to a kernel module that is not open source software (mark this bugs with the keyword TAINTED):

Thank you for taking the time to report this bug. Sadly, your report contains information about a not open-sourced module. This means you have loaded a module into your kernel that we can't debug, making it difficult to isolate the issue. Can you reproduce the issue without loading the tainted <module-name> module?.
If you cannot duplicate the bug without the tainted module loaded it will be closed.
However, you can report it to the vendor of your non-free module.

Bug state transitions

  • A bug marked as MODIFIED has patches in testing and should not have their status changed. An exception to this is when a bug has been in MODIFIED state for some time (this usually indicates that the issue was fixed in an update, and no-one ever closed the bug. If in doubt, ping the reporter to retest with the latest build).
  • If a bug has been in NEEDINFO for several months with no follow-up from the reporter, there's not a great deal we can do. In this situation, closing the bug is the only recourse available (which does actually tend to 'wake up' some reporters who then reopen the bug).
  • When marking bugs as duplicates, we want the one with the most information to be the one that remains open, even if this means a higher numbered bug gets closed.
  • Don't close bugs marked beginning with [mmconf] or [msi] (bugs beginning with [$something] are usually specifically marked so developers can quickly see the main issue within the bug)


  • If there's an upstream ( bug that matches
  • In the Fedora bug, set 'external bugzilla references' to point to the upstream bug number
  • In the upstream bugzilla, add a comment along the lines of "also seen in Fedora."
  • If the report contains a lockdep trace, mark it as blocking FCMETA_LOCKDEP
  • If the bug is against an already released Fedora (Ie, Fedora 7) and there isn't much information to go on "my machine locked up" for eg, request that the user try to reproduce the problem using the kernel-debug kernel. The additional debugging checks may trigger some clues.
  • If the bug you are triaging contains a patch, please add [PATCH] to the beginning of the summary line of the bugzilla.
  • Sometimes a user will attach a kernel panic as a jpeg, or in worst case, as a tarball of their /var/log/messages.
  • It saves the kernel team time if the kernel oops parts of these are transcribed/cut out and pasted into the bug as text.
  • Additionally, making sure that text attachments of bugs have their MIME type set to text/plain can save some time.
  • You can ask reporters to try and duplicate with the latest nightly live composes:
  • You can ask reporters to try the newest kernel available in koji:
  • If the bug appears to be video/kernel modesetting related, reassign it to the xorg-x11-drv-{intel,ati,nouveau} component.
  • If the reporter is using a custom compiled kernel, close the bug as a duplicate of

Common Problems

Point reporters to: KernelCommonProblems

Bug assignment

For certain categories of bug, assigning/cc'ing people responsible for the relevant subsystem is a good idea. When reassigning Add to Cc:

Subsystem Reassign to Add to Cc: Other notes.
intel video xorg-x11-drv-intel
radeon video xorg-x11-drv-radeon
nouveau video xorg-x11-drv-ati
ACPI Add FCMETA_ACPI to 'blocks'
ELF interpreter
SATA * Add FCMETA_SATA to 'blocks'
USB Add FCMETA_USB to 'blocks'
SCSI Add FCMETA_SCSI to 'blocks'
Sound Add FCMETA_ALSA to 'blocks'
Broadcom wireless driver (bcm43xx)
Broadcom wired drivers (bnx2, bnx2x, b44, tg3)
EXT2/EXT3/JBD/XFS (Or pretty much any filesystem stuff goes to Eric)
CPU frequency scaling
3D (DRM/AGP) Change component to xorg-x11-drv-{intel,ati}
udev related
USB cameras
ptrace (and utrace)
IMA (integrity measurement)
r8169 ethernet driver