... | ... | @@ -7,22 +7,19 @@ Bugs should be filed in this projects' [issue tracker](https://gitlab.freedeskto |
|
|
* How often does the steps listed above trigger the issue? For example: always, 1 out 3 times.
|
|
|
* Which platforms and features are affected (if you can).
|
|
|
* The following information about your system:
|
|
|
* System architecture: ("uname -m")
|
|
|
* Kernel version: ("uname -r"). Again, please consider using latest drm-tip from [http://cgit.freedesktop.org/drm-tip](http://cgit.freedesktop.org/drm-tip)
|
|
|
* System architecture: (`uname -m`)
|
|
|
* Kernel version: (`uname -r`). Again, please consider using latest drm-tip from [http://cgit.freedesktop.org/drm-tip](http://cgit.freedesktop.org/drm-tip)
|
|
|
* Linux distribution
|
|
|
* Machine or mother board model (use [dmidecode](https://linux.die.net/man/8/dmidecode) if needed)
|
|
|
* Display connector: (such as HDMI, DP, eDP, ...)
|
|
|
* A full dmesg with debug information and/or a GPU crash dump:
|
|
|
* To obtain a dmesg with debug information, add `drm.debug=0xe log_buf_len=4M` to your kernel command line, then reboot and reproduce the issue again. Make sure to attach the full dmesg all the way from boot. (Please use "Attach a file" to attach the logs to the issue, avoid linking to logs on external sites.)
|
|
|
* In the case of a GPU hang, dmesg will contain a "GPU crash dump saved to /sys/class/drm/card0/error" message. The contents of that file are crucial to debugging the issue. Note that the contents of that file are generated by the kernel when it is read, so it will appear to have zero bytes. Reading the file contents with cat will produce the expected result. For example, use
|
|
|
|
|
|
$ cat /sys/class/drm/card0/error | bz2 > error.bz2
|
|
|
|
|
|
* In the case of a GPU hang, dmesg will contain a "GPU crash dump saved to /sys/class/drm/card0/error" message. The contents of that file are crucial to debugging the issue. Note that the contents of that file are generated by the kernel when it is read, so it will appear to have zero bytes. Reading the file contents with cat will produce the expected result. For example, use `cat /sys/class/drm/card0/error | bzip2 > error.bz2`.
|
|
|
* Note that a new bug is preferred over adding your GPU crash dump to an already open bug. Most often the cause for the GPU hangs are different, and it is easy for the developers to mark bugs as duplicate.
|
|
|
|
|
|
* Other attachments if relevant:
|
|
|
* screenshot or photo (a picture is worth a thousand words);
|
|
|
* output of "xrandr --verbose" for display mode issue;
|
|
|
* output of `xrandr --verbose` for display mode issue;
|
|
|
* intel_reg_dumper output (see [the guide](https://01.org/linuxgraphics/documentation/using-intel-reg-dumper)) and VBIOS dump (see [the guide](https://01.org/linuxgraphics/documentation/how-dump-video-bios-0)) for display issues;
|
|
|
* for GPU hang, get the last batch buffer (see [the guide](https://01.org/linuxgraphics/documentation/how-get-last-batch-buffer-gpu-hang));
|
|
|
* for suspend/resume problems, refer to [the guide](https://01.org/linuxgraphics/documentation/development/how-debug-suspend-resume-issues).
|
... | ... | |