How to file a good bug report

1. Where to report graphics bugs:

-- https://bugs.freedesktop.org
-- Category:
1) For 2D driver bug: Product=xorg. Components=Driver/intel.
2) For 3D driver bug: Product=Mesa.
2.1) For chipset i8xx/i915/i945/Q33/G33/Q35: Components=Drivers/DRI/i915.
2.2) For chipset i965/G35 and later: Components=Drivers/DRI/i965.

2. Information to provide:

1) A clear subject. Starting with [[Chipset] [Subsystem/Feature]] to highlight if needed, e.g. [915GM TV] or [EXA].
2) System environment:
-- chipset: (e.g. G965)
-- system architecture: ("uname -m")
-- xf86-video-intel/xserver/mesa/drm version: (If it's built by yourself, provide the git commit id or stable release version. If it's shipped with distribution, provide the package version.)
-- kernel version: ("uname -r")
-- Linux distribution:
-- Machine or mobo model:
3) Reproduce steps. Probability if not 100% reproducible.
4) Attachment:
-- Xorg.0.log
-- xorg.conf
-- dmesg
-- screenshot or photo (optional, a picture is worth a thousand words)
-- output of "xrandr --verbose" (if mode related issue)

3. Assistance to help debugging:

-- Add option "ModeDebug" "yes" in the Device section of xorg.conf to dump more register information into Xorg log.
-- For 3D issues, run with LIBGL_DEBUG=verbose in the environment.
-- Provide gdb backtrace. See the guide for how to use gdb for X server crash.
-- If the display mode broken with the current driver but you have another method to get it work (e.g. using the old i810-1.x driver), use reg_dump tool (in xf86-video-intel package) to dump the register info under the both conditions.
-- For performance issue, please provide profiling data, e.g. by using sysprof.
-- For regression, try using git-bisect to locate the commit which caused the regression.
-- Compare with other products or configurations if possible.

4. Tips

-- Specific: Each bug report is for only one issue/problem. If you found several issues in one test, please separate them into several bugs.
-- Close the bug if the orignially reported issue resolved. For new issues, open new bugs instead of continuing the discussion in the old bug.
-- Attach log with explicitly choosing content type as "plain text (text/plain)". Don't use zipped files.
-- After answering developer's NEEDINFO, make sure 'NEEDINFO' cleared in keywords field and reassign back to the developer owner.
-- Attach monitor directly to the machine, rather than via a KVM or other devices.
-- Better don't have framebuffer kernel module (CONFIG_FB) loaded or built-in.
-- Using warm reboot to try the new code is not completely clean for the gfx environment. Better do a power cycle instead.

Appendix: recommended bug report template:

Bug description:

System environment:
-- chipset:
-- system architecture: XX-bit
-- xf86-video-intel:
-- xserver:
-- mesa:
-- drm:
-- kernel:
-- Linux distribution:
-- Machine or mobo model:

Reproducing steps:

Additional info:

How to file a good bug report

1. Where to report graphics bugs:

-- https://bugs.freedesktop.org
-- Category:
1) For 2D driver bug: Product=xorg. Components=Driver/intel.
2) For 3D driver bug: Product=Mesa.
2.1) For chipset i8xx/i915/i945/Q33/G33/Q35: Components=Drivers/DRI/i915.
2.2) For chipset i965/G35 and later: Components=Drivers/DRI/i965.

2. Information to provide:

1) A clear subject. Starting with [[Chipset] [Subsystem/Feature]] to highlight if needed, e.g. [915GM TV] or [EXA].
2) System environment:
-- chipset: (e.g. G965)
-- system architecture: ("uname -m")
-- xf86-video-intel/xserver/mesa/drm version: (If it's built by yourself, provide the git commit id or stable release version. If it's shipped with distribution, provide the package version.)
-- kernel version: ("uname -r")
-- Linux distribution:
-- Machine or mobo model:
3) Reproduce steps. Probability if not 100% reproducible.
4) Attachment:
-- Xorg.0.log
-- xorg.conf
-- dmesg
-- screenshot or photo (optional, a picture is worth a thousand words)
-- output of "xrandr --verbose" (if mode related issue)

3. Assistance to help debugging:

-- Add option "ModeDebug" "yes" in the Device section of xorg.conf to dump more register information into Xorg log.
-- For 3D issues, run with LIBGL_DEBUG=verbose in the environment.
-- Provide gdb backtrace. See the guide for how to use gdb for X server crash.
-- If the display mode broken with the current driver but you have another method to get it work (e.g. using the old i810-1.x driver), use intel_reg_dumper tool (reg_dump in xf86-video-intel package) to dump the register info under the both conditions.
-- For regression, try using git-bisect to locate the commit which caused the regression.
-- Compare with other products or configurations if possible.
-- For VT switch problems, use intel_reg_dumper tool to dump the register info: 1) prior to VT switch 2) after VT switch.
-- For suspend/resume problems, we also need register dumps, but only from a text console:
1) VT switch to a text console
2) capture the output from intel_reg_dumper in a file
3) suspend your machine (using echo mem or disk > /sys/power/state)
4) on resume, before VT switching back to X, capture another register dump
5) attach both pre- and post- suspend register dumps to the bug report

4. Tips

-- Specific: Each bug report is for only one issue/problem. If you found several issues in one test, please separate them into several bugs.
-- Close the bug if the orignially reported issue resolved. For new issues, open new bugs instead of continuing the discussion in the old bug.
-- Attach log with explicitly choosing content type as "plain text (text/plain)". Don't use zipped files.
-- After answering developer's NEEDINFO, make sure 'NEEDINFO' cleared in keywords field and reassign back to the developer owner.
-- Attach monitor directly to the machine, rather than via a KVM or other devices.
-- Better don't have framebuffer kernel module (CONFIG_FB) loaded or built-in.
-- Using warm reboot to try the new code is not completely clean for the gfx environment. Better do a power cycle instead.

Appendix: recommended bug report template:

Bug description:

System environment:
-- chipset:
-- system architecture: XX-bit
-- xf86-video-intel:
-- xserver:
-- mesa:
-- drm:
-- kernel:
-- Linux distribution:
-- Machine or mobo model:

Reproducing steps:

Additional info: