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. ** Tags added: bios-outdated-1.37 ** Attachment removed: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579481/+attachment/4658523/+files/version.log ** Attachment removed: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579481/+attachment/4658522/+files/lspci-vnvn.log ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579481 Title: 16.04 -> External Monitor not working -> radeon VCE init error (-110) Status in linux package in Ubuntu: Incomplete Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
