16.04 -> External Monitor not working -> radeon VCE init error (-110)

[R. Becke]

Since I've upgraded 15.10 to 16.04 my external monitor is not working anymore. Whether I plug it directly into the DVI port of my laptop ("HP EliteBook 840 G1") or whether I plug it into the DVI or VGA port of my docking station "HP 2013 UltraSlim-Dockingstation" I get the following error in "/var/log/syslog":
...
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.377223] radeon 0000:03:00.0: VCE init error (-110).
May 4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [ 64.811603] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage
May 4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [ 64.811619] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed
...

I tried as well a fresh 16.04 install but this still did not help.
The full log related to plugging in an external monitor is:
...
May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.573716] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.578032] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.578106] acpi PNP0501:00: Still not present
May 4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [ 62.578184] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.267945] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.267950] [drm] PCIE gen 2 link speeds already enabled
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275081] [drm] PCIE GART of 2048M enabled (table at 0x00000000002E8000).
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275187] radeon 0000:03:00.0: WB enabled
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275190] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff880434a83c00
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275191] radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff880434a83c04
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275192] radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff880434a83c08
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275194] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff880434a83c0c
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.275195] radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff880434a83c10
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.276738] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90002835a18
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.377223] radeon 0000:03:00.0: VCE init error (-110).
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612628] [drm] ring test on 0 succeeded in 1 usecs
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612635] [drm] ring test on 1 succeeded in 1 usecs
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612640] [drm] ring test on 2 succeeded in 1 usecs
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612650] [drm] ring test on 3 succeeded in 5 usecs
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.612658] [drm] ring test on 4 succeeded in 5 usecs
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788345] [drm] ring test on 5 succeeded in 2 usecs
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788352] [drm] UVD initialized successfully.
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788388] [drm] ib test on ring 0 succeeded in 0 usecs
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788421] [drm] ib test on ring 1 succeeded in 0 usecs
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788453] [drm] ib test on ring 2 succeeded in 0 usecs
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788483] [drm] ib test on ring 3 succeeded in 0 usecs
May 4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [ 63.788514] [drm] ib test on ring 4 succeeded in 0 usecs
May 4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [ 64.437532] [drm] ib test on ring 5 succeeded
May 4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [ 64.811603] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage
May 4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [ 64.811619] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed
May 4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [ 65.062599] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage
May 4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [ 65.062614] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed
...

I tried as well upgrading to the latest kernel as described here:
https://wiki.ubuntu.com/KernelMainlineBuilds - latest v4.6 kernel[0]
But this did not help either.

Some further details:

# lspci -k | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] (rev ff)

# xrandr --listproviders
Providers: number : 3
Provider 0: id: 0x6d cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 6 associated providers: 2 name:Intel
Provider 1: id: 0x43 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 2 associated providers: 2 name:OLAND @ pci:0000:03:00.0
Provider 2: id: 0x43 cap: 0x6, Sink Output, Source Offload crtcs: 2 outputs: 2 associated providers: 2 name:OLAND @ pci:0000:03:00.0

This bug could be related to: "https://bugzilla.redhat.com/show_bug.cgi?id=1262649" but I could nowhere find any answers when it will be fixed or what is the root cause.
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: raoul-becke--s0-v1 2062 F.... pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=39fdf497-1989-4699-87de-c2404745e296
InstallationDate: Installed on 2016-04-29 (8 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP EliteBook 840 G1
Package: linux (not installed)
ProcFB:
 0 inteldrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=fdc7fbde-63a1-4228-a940-7820605e44b5 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
Tags: xenial
Uname: Linux 4.4.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 01/26/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.35
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.57
dmi.chassis.asset.tag: 5CG4371SBC
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.35:bd01/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3008CD10003:rvnHewlett-Packard:rn198F:rvrKBCVersion15.57:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 840 G1
dmi.product.version: A3008CD10003
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

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

apport-collect 1579481

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.

[R. Becke (subscribe-becke)]

I participated and tried as well the steps described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573648 (16.04 -> AMD APU via VGA gives blank screen) but this did not help.

[R. Becke (subscribe-becke)]

I just upgraded to the latest kernel:
Linux version 4.4.0-22-generic (buildd@lcy01-32) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016

And the error log has changed slightly:
...
May 8 10:58:10 hp-elitebook-840-g1--s0-v2 kernel: [ 643.987867] radeon 0000:03:00.0: VCE init error (-110).
May 8 10:58:10 hp-elitebook-840-g1--s0-v2 kernel: [ 644.683920] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
May 8 10:58:10 hp-elitebook-840-g1--s0-v2 kernel: [ 644.683937] [drm:si_resume [radeon]] *ERROR* si startup failed on resume
...

I've now attached: apport-collect 1579481

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[R. Becke (subscribe-becke)]

apport information

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[penalvch (penalvch)]

R. Becke, 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.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

[R. Becke (subscribe-becke)]

kernel-bug-exists-upstream
kernel-bug-exists-upstream-4.7-rc2-yakkety

Hi Christopher,
Thx for the support. Ufortunately the bug is only fixed partially:

Laptop: Display Port: WORKS: If I connect the external monitor to the Display Port of the Laptop (HP EliteBook 840 G1) it works!

ultraslim docking station 2013: Display Port: NOT WORKING: "[drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage": If I connect the monitor to the ultraslim docking station 2013 it does not work and I get the following syslog output while connecting:
...
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.290678] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.290685] [drm] PCIE gen 2 link speeds already enabled
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.297871] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.297995] radeon 0000:03:00.0: WB enabled
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.297999] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8804348d4c00
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.298001] radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff8804348d4c04
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.298003] radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff8804348d4c08
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.298006] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8804348d4c0c
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.298008] radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff8804348d4c10
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.298818] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90002835a18
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.399323] radeon 0000:03:00.0: failed VCE resume (-110).
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.633111] [drm] ring test on 0 succeeded in 1 usecs
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.633118] [drm] ring test on 1 succeeded in 1 usecs
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.633123] [drm] ring test on 2 succeeded in 1 usecs
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.633133] [drm] ring test on 3 succeeded in 5 usecs
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.633141] [drm] ring test on 4 succeeded in 5 usecs
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.808926] [drm] ring test on 5 succeeded in 2 usecs
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.808933] [drm] UVD initialized successfully.
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.808970] [drm] ib test on ring 0 succeeded in 0 usecs
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2 kernel: [ 1019.809003] [drm] ib test on ring 1 succeeded in 0 usecs
Jun 12 12:18:25 hp-elitebook-840-g1--s0-v2...

[penalvch (penalvch)]

R. Becke, as per the release notes from http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=5405097&swLangOid=8&swEnvOid=4192 an update to your computer's buggy, insecure, and outdated BIOS is available (1.37). When you update to this following https://help.ubuntu.com/community/BIOSUpdate does this improve the situation?

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

[R. Becke (subscribe-becke)]

L71 Ver. 01.35
01/26/2016

Hi Christopher,
Actually my BIOS is very up-to-date (and the problem persists as described above):
admin--s0-v1@hp-elitebook-840-g1--s0-v2:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for admin--s0-v1:
L71 Ver. 01.35
01/26/2016

And this is actually the latest BIOS I can get when updating from within the BIOS itself while connected to the internet. I can only get a later BIOS by using Windows because for Linux only an outdated version is available.

Anyway by looking at the revision history there is nothing relevant mentioned regarding the graphic card issue:

Version:01.37 Rev.A (26 May 2016)
Enhancements
- Fixes an issue where the battery does not recharge properly in the system.

Version:01.36 Rev.A (16 May 2016)
Enhancements
- Provides improved security of UEFI code and variables. HP strongly recommends transitioning promptly to this updated BIOS version which supersedes all previous releases.

NOTE: Due to security changes, after installing this updated BIOS, older versions cannot be reinstalled.
...

[penalvch (penalvch)]

R. Becke, as noted in the previously provided documentation, one would want to update anyways. Having a BIOS version installed that is older than the latest provide by the vendor is the very definition of outdated.

[R. Becke (subscribe-becke)]

Hi Chirstopher,
Actually I don't think the issue is related to the BIOS of my laptop but rather to the firmware of my
"HP 2013 UltraSlim-Dockingstation". Therefore I tried the following firmware upgrade:
http://h20564.www2.hp.com/hpsc/swd/public/detail?swItemId=ob_147496_1#tab-history
BUT I tried in Windows 8.1 and Windows 10 and just could not get it working i.e. the docking station did not produce any video output on the two DVI Ports neither on the VGA Port and the firmware upgrade could not get installed. At least the DVI Port of the Laptop is working which is for now fine for me.

[R. Becke (subscribe-becke)]

PS: Actually I had most of this (Laptop-Diplay-Port & Docking-Station+VGA-Port & partially Docking-Station+Display-Port (partially because of rendering issues on DP-Port)) working in Ubuntu 14.04 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376581) and therefore I don't think this is really related to the BIOS - because at this time I had old BIOS version.

[Aaron Peromsik (aperomsik)]

If we identify which commit from upstream fixed the issue, would it make sense to release an update for Xenial?

Suspect it is this one but haven't tried to build yet:

https://github.com/torvalds/linux/commit/c8213a638f65bf487c10593c216525952cca3690

[Aaron Peromsik (aperomsik)]

Confirmed: typing this on my second screen, connected via VGA, after cherry-picking the commit I linked to in #28. Without that commit the second screen was recognized but remained dark while connected to the VGA port of my Kaveri-based desktop. Same monitor had been fine when connected via DVI.

[penalvch (penalvch)]

Aaron Peromsik, so your hardware and issue may be scoped, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]