Bug 96527 - [radeon] sumo2 locks up and fails to train displayport during boot (panel turns off)
Summary: [radeon] sumo2 locks up and fails to train displayport during boot (panel tur...
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.7 (2012.06)
Hardware: x86-64 (AMD64) Linux (All)
: highest blocker
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-14 16:56 UTC by Kostiantyn P
Modified: 2019-11-19 07:56 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg output (74.04 KB, text/plain)
2016-06-14 16:56 UTC, Kostiantyn P
no flags Details
Xorg.0.log (42.47 KB, text/x-log)
2016-06-14 16:59 UTC, Kostiantyn P
no flags Details
journalctl output (151.53 KB, application/octet-stream)
2016-06-14 17:03 UTC, Kostiantyn P
no flags Details
journalctl.out.noaccel (157.80 KB, application/octet-stream)
2016-06-14 19:31 UTC, Kostiantyn P
no flags Details
Xorg.0.log.noaccel (38.65 KB, text/plain)
2016-06-14 19:31 UTC, Kostiantyn P
no flags Details

Description Kostiantyn P 2016-06-14 16:56:14 UTC
Created attachment 124526 [details]
dmesg output

Problem: Laptop panel turns off during boot, which makes the laptop unusable. 

Expected Results: Laptop panel is ON when I boot without "nomodeset", and I can use graphical UI.

Environment: 
Ubuntu 16.04 (clean install) with the latest (v4.7-rc3) manually installed kernel. 
X.Org X Server 1.18.3


Hardware:
HP ProBook 4535
[AMD/ATI] Sumo [Radeon HD 6380G]
[AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] (rev ff)


Overview:
I used "nomodeset" kernel parameter to install Ubuntu, because without it I face the same bug - Laptop panel turns off during boot. UI works with this kernel parameter but it's not usable as it's very slow(!!!). When "nomodeset" is removed the system boots but the screen turns off during the boot.

Guys from #radeon channel on "irc.freenode.net" said:
<chithead> radeon 0000:00:01.0 is the sumo2 and it locks up
<chithead> radeon 0000:01:00.0 is the caicos but there seems to be no problem with it
<airlied> the problem is the sumo crashing and failing to train displayport
<airlied> as it's the travis bridge it's trying to modeset which is the panel
<airlied> fixing the travis bridge is the first problem
Comment 1 Kostiantyn P 2016-06-14 16:59:23 UTC
Created attachment 124527 [details]
Xorg.0.log
Comment 2 Kostiantyn P 2016-06-14 17:03:31 UTC
Created attachment 124528 [details]
journalctl output
Comment 3 Alex Deucher 2016-06-14 17:10:16 UTC
It looks like a GPU hang.  I think the displayport failure is just a side effect of that.  Does it work if you disable acceleration in X?  To disable acceleration, add an /etc/X11/xorg.conf file with the following content:

Section "Device"
        Identifier              "Device0"
        Driver                  "radeon"
        Option                  "NoAccel" "true"
EndSection
Comment 4 Kostiantyn P 2016-06-14 17:19:10 UTC
Now it works, but I see the same slow UI performance as with "nomodeset". I definitely would like to have UI working faster.
Comment 5 Kostiantyn P 2016-06-14 19:31:22 UTC
Created attachment 124532 [details]
journalctl.out.noaccel
Comment 6 Kostiantyn P 2016-06-14 19:31:45 UTC
Created attachment 124533 [details]
Xorg.0.log.noaccel
Comment 7 Kostiantyn P 2016-06-14 19:35:21 UTC
Attached new logs from the system with /etc/xorg.conf as you suggested.
Will it be fixed? If it will, then when and how can I help?
Life sucks without hardware acceleration ... .
Thank you.
Comment 8 Martin Peres 2019-11-19 07:56:52 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/xorg/driver/xf86-video-ati/issues/161.


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.