Bugs should be reported through your AMD Customer Engagement Representative.
If you downloaded a release archive directly from the AMD web site and do not have an AMD Customer Engagement Representative, you may report bugs using the gitlab.freedesktop.org issue tracker with the label “AMDgpu-pro”.
Generating a Bug Report¶
In order to facilitate efficient investigation, it’s important to include as much detail as possible with the bug report. Perform the following steps before you file a bug report:
Create a destination folder for the report.
If you gather several reports, identify them with the date and if needed add a number at the end to differentiate between your reports, as shown in the following example.
$ LOGDIR=~/LOGS/20170913-1 $ mkdir -p $LOGDIR $ cd $LOGDIR
Gather basic configuration details.
$ sudo lshw -c cpu | grep product >> basic.conf $ lspci -nn | grep "VGA\|Display" >> basic.conf $ sudo dmidecode -t BIOS | grep Version >> basic.conf $ lsb_release -sd >> basic.conf $ uname -a >> basic.conf $ dkms status | grep "amdgpu\|radeon" >> basic.conf
Create detailed log files by running the following commands:
$ dkms status > dkms.status.log $ lsmod | grep amdgpu > lsmod.amdgpu.log $ dmesg > dmesg.log $ cp /var/log/Xorg.0.log . $ type -p dpkg && dpkg -l > package.log $ type -p rpm && rpm -qa > package.log
(Optional) To facilitate in-depth analysis, you can run the following commands:
$ lspci -vnn > lspci.vnn.log $ lspci -nn > lspci.nn.log $ sudo dmidecode > dmidecode.log $ uname -a > uname.a.log $ lsinitramfs /boot/initrd.img-`uname -r` > lsinitramfs.log $ sudo lshw > lshw.log $ modinfo amdgpu > modinfo.amdgpu.log $ glxinfo > glxinfo.log
Capturing the Output of Your Commands to a File¶
Start a script session to capture your commands to a log file.
$ script /tmp/install-log.txt
- Run all commands you want to capture in the script (for example, install
All-Open base driver).
$ amdgpu-install -y --usecase=graphics
End the capture session.