radeon: black screen after upgrade from 14.04 to 16.04 on RS780

Bug #1651910 reported by Chi-Thanh Christopher Nguyen
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux
Unknown
Medium
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black after GRUB (backlight is on) when booting with the new 4.4 kernel (linux-image-4.4.0-57-generic). Monitor connected via DVI.

WORKAROUND: Boot with the old 3.14 kernel.

---
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=dbcee44e-5c4b-4630-a837-f819f42e91eb
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: BIOSTAR Group A780L
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic root=UUID=da4d032c-4aef-42d0-bcf6-1cf98904be02 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-32-generic N/A
 linux-backports-modules-4.8.0-32-generic N/A
 linux-firmware 1.157.6
RfKill:

Tags: xenial
Uname: Linux 4.8.0-32-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-09-24 (89 days ago)
UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare
_MarkForUpload: True
dmi.bios.date: 07/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: A780L
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd07/20/2010:svnBIOSTARGroup:pnA780L:pvr:rvnBIOSTARGroup:rnA780L:rvr:cvnBIOSTARGroup:ct3:cvr:
dmi.product.name: A780L
dmi.sys.vendor: BIOSTAR Group

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : Dependencies.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : JournalErrors.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : ProcEnviron.txt

apport information

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1651910

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: trusty
Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote :

apport-collect will give me the same output as ubuntu-bug, namely that I am not running an Ubuntu kernel and refuse to do anything else.
The official 16.04 kernel will only produce a black screen.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote :
Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote :
Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote :

I also tried kernel 4.8 which seems to be the latest packaged for 16.04, with the same result.

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : AlsaInfo.txt

apport information

description: updated
Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : CRDA.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : JournalErrors.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : Lspci.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : Lsusb.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : ProcEnviron.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : ProcModules.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : UdevDb.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote : WifiSyslog.txt

apport information

Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote :

I was able to run apport-collect via ssh when booted into the Ubuntu kernel.

Revision history for this message
In , Chi-Thanh Christopher Nguyen (chithanh) wrote :

Hardware: BIOSTAR A780L

When booting with 3.15 or newer kernels, a monitor connected to the DVI port of the BIOSTAR A780L will stay blank.
Kernel 3.14 and older work fine.

I tried forcing the output to on with video=HDMI-A-1:e but this made no difference.

Revision history for this message
In , Chi-Thanh Christopher Nguyen (chithanh) wrote :

Created attachment 128629
dmesg from kernel 3.14 with drm.debug=15 (working)

Revision history for this message
In , Chi-Thanh Christopher Nguyen (chithanh) wrote :

Created attachment 128630
dmesg from kernel 4.9 with drm.debug=15 (not working)

Revision history for this message
In , Chi-Thanh Christopher Nguyen (chithanh) wrote :

https://bugzilla.kernel.org/show_bug.cgi?id=91861 seems to be related, however this issue still happens with kernel 4.9

Revision history for this message
penalvch (penalvch) wrote :

Chi-Thanh Christopher Nguyen, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

tags: added: latest-bios-080014 regression-release
removed: trusty
description: updated
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Chi-Thanh Christopher Nguyen (chithanh) wrote :

Kernel 4.9 is still affected.

It appears that this is a regression introduced between kernel 3.15-rc1 and 3.15-rc2.

tags: added: kernel-bug-exists-upstream-3.15-rc2 kernel-bug-exists-upstream-4.9.0
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Chi-Thanh Christopher Nguyen, the next step is to fully commit bisect from kernel 3.15-rc1 to 3.15-rc2 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

It is most helpful that after the fix commit (not kernel version) has been identified, you then mark this report Status Confirmed.

Thank you for your help.

tags: added: kernel-bug-exists-upstream-4.9 needs-bisect
removed: kernel-bug-exists-upstream-3.15-rc2 kernel-bug-exists-upstream-4.9.0
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
In , penalvch (penalvch) wrote :
Revision history for this message
In , Martin-peres-n (martin-peres-n) wrote :

-- 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/766.

Changed in linux:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.