Bug 103111 - Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
Summary: Tonga PRO [Radeon R9 285/380] [1002:6939] blank screen
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-05 15:55 UTC by Steve Falco
Modified: 2019-11-19 08:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg file showing a successful boot (105.36 KB, text/plain)
2017-10-05 15:55 UTC, Steve Falco
no flags Details
good xorg log (33.56 KB, text/x-log)
2017-10-05 15:55 UTC, Steve Falco
no flags Details
bad xorg log (3.72 KB, text/x-log)
2017-10-05 15:55 UTC, Steve Falco
no flags Details
bad dmesg log (141.73 KB, text/plain)
2017-10-05 15:56 UTC, Steve Falco
no flags Details
second bad xorg log (2.61 KB, text/x-log)
2017-10-05 15:56 UTC, Steve Falco
no flags Details
dmesg from agd5f 4.13.0 kernel (251.96 KB, text/plain)
2017-10-06 20:12 UTC, Steve Falco
no flags Details
xorg log from agd5f 4.13.0 kernel (34.39 KB, text/x-log)
2017-10-06 20:13 UTC, Steve Falco
no flags Details
dmesg with increased log buffer parameter (613.10 KB, text/plain)
2017-10-06 20:59 UTC, Steve Falco
no flags Details
xorg log corresponding to the increased log buffer size (37.84 KB, text/x-log)
2017-10-06 21:00 UTC, Steve Falco
no flags Details

Description Steve Falco 2017-10-05 15:55:03 UTC
Created attachment 134681 [details]
dmesg file showing a successful boot
Comment 1 Steve Falco 2017-10-05 15:55:34 UTC
Created attachment 134682 [details]
good xorg log
Comment 2 Steve Falco 2017-10-05 15:55:57 UTC
Created attachment 134683 [details]
bad xorg log
Comment 3 Steve Falco 2017-10-05 15:56:18 UTC
Created attachment 134684 [details]
bad dmesg log
Comment 4 Steve Falco 2017-10-05 15:56:39 UTC
Created attachment 134685 [details]
second bad xorg log
Comment 5 Steve Falco 2017-10-05 15:58:41 UTC
I have a Radeon R9 285/380 video card in a machine that is running Fedora 26.  When I run with Fedora kernel version 4.11.11 the video card works properly, using the amdgpu kernel driver.

However, once I upgrade to a newer kernel in the 4.12 or 4.13 series, my display goes blank during boot and stays that way for a long time.  The monitor appears to be getting sync, because it doesn't go to sleep, however there is nothing visible on the screen.

Eventually, error messages are displayed and the system never boots fully.

I've attached logs showing both a good and a bad startup.  For some reason, in the "bad case", I got two xorg log files, so I've attached both.

Please let me know if there is more information that I can collect to help in debug.
Comment 6 Steve Falco 2017-10-06 20:12:23 UTC
Created attachment 134713 [details]
dmesg from agd5f 4.13.0 kernel
Comment 7 Steve Falco 2017-10-06 20:13:05 UTC
Created attachment 134714 [details]
xorg log from agd5f 4.13.0 kernel
Comment 8 Steve Falco 2017-10-06 20:16:05 UTC
As per the mailing list suggestions, I've built a kernel from the amd-staging-drm-next branch of the agd5f kernel tree.

While it gives me a usable gui, I also get "corrupted mapping in tail page" errors.  Please see the dmesg attachment at https://bugs.freedesktop.org/attachment.cgi?id=134713 for the details.
Comment 9 Steve Falco 2017-10-06 20:59:36 UTC
Created attachment 134717 [details]
dmesg with increased log buffer parameter

Previous log file was truncated.  This one is better.
Comment 10 Steve Falco 2017-10-06 21:00:20 UTC
Created attachment 134718 [details]
xorg log corresponding to the increased log buffer size
Comment 11 Steve Falco 2017-10-06 21:03:04 UTC
I re-ran the tests with increased log buffer size, since the previous run was truncated.

The first error message that I see is [   56.199374] BUG: Bad page state in process Xorg  pfn:817601, followed by [   56.199396] page dumped because: nonzero compound_mapcount.
Comment 12 Martin Peres 2019-11-19 08:24:42 UTC
-- 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/243.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.