| Bug ID | 95306 |
|---|---|
| Summary | Random Blank(black) screens on "Carrizo" |
| Product | DRI |
| Version | XOrg git |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | areginato@hotmail.com |
I've searched all over my logs, and can't find any faults. My HP Pavilion (A10-8700P) runing Kubuntu 16.04 and using the AMDgpu driver randomly black screens. A suspend/resume will get it working again for a very short period of time. I've been debuging this all week - I've tried a new kernel, I've also tried the amdgpu.exp_hd_support=1 boot parameter, I've gone through everything think it might have been a DPMS issue. When it occurs, it happens on the internal and external display if hooked up. For me, I can replicate the issue by booting the computer and letting it sit at the log in, or I log in and use the computer. The occurrence is random and never the same.
| What | Removed | Added |
|---|---|---|
| Severity | normal | major |
| OS | All | Linux (All) |
| Hardware | Other | x86-64 (AMD64) |
This bug affects me on Ubuntu 14.04, 15.10, 16.04, and Arch Li= nux. I too have the same AMD chip, A10-8700p, on an HP 17-g121wm. I can only get past the b= lack screen if I boot into low-graphics mode with the nomodeset parameter. I have scoured countless online resources looking for a solution to this problem. I hope someone knowledgeable and able to do something about it tak= es notice of this page and works on the bug.
Hi Josh, since the original reporter didn't, perhaps you can a= t least provide your xorg log and dmesg output?
Created attachment 125945 [details]
4.7.2 kernel with 2.49 glib2. The display did not go on again after resuming
from suspend.
Created attachment 125946 [details]
4.7.1 kernel with 2.49 glib2. The display blanked temporarily, function
restored for 10 minutes after switching to TTY and back.
Created attachment 125947 [d=
etails]
4.7.1 kernel with 2.49 glib2. The display blanked for good after blanking
temporarily.
APU: AMD FX-8800P (Carrizo, Volcanic Island) GPU: AMD Radeon R7 M360 (Topaz XT, Volcanic Island) OS: Archlinux X: 1.18.4 DE: Gnome 3.20, happens with other (KDE, XFCE, i3)=20 DM: GDM 3.20 Kernel: Various stable and rc releases 4.4 to 4.7.2 Glib2: 2.48.1 Problem: Screen blanks randomly. It usually happens with cold machine immediately after loading amdgpu module. After resume from suspend the scre= en turns on and blanks after a few seconds (always less than 1 minute). Even if the booting is successful it will happen at any time after that. The machine almost never runs for more than 30 minutes without blanking. Connecting VGA= or HDMI monitor causes immediate blank but starting with connected monitors or disconnecting them doesn't. Once screen blanks there is no way how to get it working (switching to console, playing with xrandr etc.) except for suspend (the few seconds is not worth it). It does not seem to affect console unles= s X is started.=20 Kernel: 4.5rc6 (and maybe some other) Glib2: 2.48.1, 2.49.5.11.gb82682e-1 Problem: It occurs only on cold boot, after connecting external monitor (di= dn't test yet with Glib2 2.49) and a longer suspend (a few minutes). Kernel: 4.7.1 Glib2: 2.49.5.11.gb82682e-1 Problem: Screen blanked once after 2 hours but turned back on after switchi= ng to console and back to X. After 10 minutes it blanked for good. Kernel: 4.7.2 Glib2: 2.49.5.11.gb82682e-1 Problem: Ran for 1h 30m without any issue. Blanked after suspending for 15 minutes and resuming. So maybe Glib2 related problem?
(In reply to Tom from c= omment #7) > Kernel: 4.7.1 > Glib2: 2.49.5.11.gb82682e-1 > Problem: Screen blanked once after 2 hours but turned back on after > switching to console and back to X. After 10 minutes it blanked for go= od. >=20 > Kernel: 4.7.2 > Glib2: 2.49.5.11.gb82682e-1 > Problem: Ran for 1h 30m without any issue. Blanked after suspending fo= r 15 > minutes and resuming. Please attach the corresponding Xorg log file.
Created at=
tachment 125978 [details]
Xorg.log: Screen blanked during boot.
Tom, does your blanking in X also happen with the modesetting = driver instead of the amdgpu driver?
(In reply to Michel D=C3=A4nzer from comment #10) > Tom, does your blanking in X also happen with th= e modesetting driver instead > of the amdgpu driver? I'm not sure how to do this. I tried setting it as a driver in Xorg.conf and the screen blanked as usual. Although Xorg.log listed only modesetting driv= er the amdgpu module was loaded. Blacklisting the module prevents X from start= ing. I was also unable to replicate the success with 4.7.2 kernel and 2.49 glib2. Now it blanks within a few minutes. It seems I was just lucky that day.
(In reply to Tom from = comment #11) > (In reply to Michel D=C3=A4nzer from comment #10) > > Tom, does your blanking in X also happen with the modesetting dri= ver instead > > of the amdgpu driver? >=20 > I'm not sure how to do this. I tried setting it as a driver in Xorg.co= nf and > the screen blanked as usual. Although Xorg.log listed only modesetting > driver the amdgpu module was loaded. Blacklisting the module prevents = X from > starting. >=20 > I was also unable to replicate the success with 4.7.2 kernel and 2.49 = glib2. > Now it blanks within a few minutes. It seems I was just lucky that day= . Don't worry about the kernel module. That should be loaded regardless of w= hat X driver you use. Just make sure modesetting is used for X.
(In reply to Alex Deucher from comment #12) > Don't worry about the kernel module. That shoul= d be loaded regardless of > what X driver you use. Just make sure modesetting is used for X. Yeah, modesetting was used. I'll attach the log.
Created attachment 126013=
[details]
Modesetting driver
| What | Removed | Added |
|---|---|---|
| Attachment #126013 mime type | text/x-log | text/plain |
I did some more testing with kernel 4.8rc5 and it seems it is = not related to X after all. Cold boot to console has exactly the same issues as cold boot to= X (screen blanks). The last message I see on the screen is =E2=80=9Cfb: switc= hing to amdgpudrmfb from EFI VGA=E2=80=9D then it turns off and on again but it is = blank. So far console didn't blank after successful start like X does unless I suspen= ded it.
This affects me as well. HP Pavillion A10-8700P - Carrizo - R6 Linux Manjaro Daniella 16.06 w. kernel 4.4 I can't wait to see this resolved. I can observe that the performance is qu= ite impressive with this AMDGPU driver (before the black screen happens...) compared to the proprietary catalyst display driver.
I did some more testing with AMDGPU-PRO driver (from AUR). It = seems to work without those issues but I get only a mesh up of previous session screen af= ter reboot or pink and white lines after cold boot.
This bug did not affect 4.6.x and earlier, it started with: commit 70eced9b2e05f38274ebe8ad91c472bb684fa82a That commit enables new features on the Carrizo, - adev->cg_flags =3D 0; + adev->cg_flags =3D AMD_CG_SUPPORT_GFX_MGCG | + AMD_CG_SUPPORT_GFX_MGLS | + AMD_CG_SUPPORT_GFX_RLC_LS | + AMD_CG_SUPPORT_GFX_CP_LS | + AMD_CG_SUPPORT_GFX_CGTS | + AMD_CG_SUPPORT_GFX_MGLS | + AMD_CG_SUPPORT_GFX_CGTS_LS | + AMD_CG_SUPPORT_GFX_CGCG | + AMD_CG_SUPPORT_GFX_CGLS; So it should be relatively easy to isolate the problem by stepping through those features one by one to isolate which of those flags is triggering the problem. I'm available to test semi-official patches until the problem is properly fixed. In the meantime I've reverted the patch on my 4.7.6 kernel and have= run for over two days without encountering the problem.
| What | Removed | Added |
|---|---|---|
| CC | tom.stdenis@amd.com |
Tom, looks like there are issues with clock gating on Carrizo.=