| Bug ID | 99313 |
|---|---|
| Summary | A few amdgpu errors with kernel 4.10-rc2 (Kaveri + Topaz) |
| Product | DRI |
| Version | XOrg git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | nmset@netcourrier.com |
Created atta=
chment 128806 [details]
dmesg for amdgpu on kernel 4.10-rc2
This is just to report a few errors with amdgpu in kernel 4.10-rc2 on my
laptop, featuring :
APU : AMD A10-7300 Radeon R6, 10 Compute Cores 4C+6G (from /proc/cpuinfo).
iGPU : 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri
HDMI/DP Audio Controller
dGPU : 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] T=
opaz
XT [Radeon R7 M260/M265 / M340/M360 / M440/M445]
Xorg : 1.18.4, on Arch Linux
$(dmesg |grep -i amdgpu) is in the attachement k4.10-rc2_amdgpu_dmesg.txt.
In brief, there are errors related to UVD and IB with Kaveri iGPU.
I do have a normal X session, except that the laptop never suspends, and th=
ings
can then go as bad as corrupting the file system beyond recognition by Grub.
I am posting this information in the hope it can be useful to developers.
Regards.
Erratum : iGPU : 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6 Graphics]
On further testing with 4.10-rcX up to commit cff3b2c : 'UVD not responding' error occurs if pg_mask is not specified. When pg_mask= is explicitly set to 0 or 1, no UVD errors are reported. X session is then normally usable. This is seen on another laptop with Kabini also.
| What | Removed | Added |
|---|---|---|
| See Also | https://bugzilla.kernel.org/show_bug.cgi?id=3D192161 |
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/125.