Ubuntu
xorg package

Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

Bug #1581270 reported by Brian Foster on 2016-05-13

This bug affects 11 people

Affects		Status	Importance	Assigned to	Milestone
	xorg (Ubuntu)	Won't Fix	High	Unassigned

Bug Description

dmesg shows issues with being able to use the discrete graphics card (relevant dmesg lines attached).

Grub does pass "radeon.modeset=1" but it doesn't seem to make a difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to the kernel, then it does not error (except for the VCE error -110, which is probably harmless).

Running `DRI_PRIME=1 glxgears`:
- with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black window with a visible top bar.
- with just "radeon.modeset=1", error (attached as 'glxgears').

Results are similar on Ubuntu GNOME 16.04, except with "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of screen tearing.

Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

[ 22.916285] [drm] ring test on 0 succeeded in 2 usecs
[ 22.916289] [drm] ring test on 1 succeeded in 1 usecs
[ 22.916292] [drm] ring test on 2 succeeded in 1 usecs
[ 22.916299] [drm] ring test on 3 succeeded in 3 usecs
[ 22.916304] [drm] ring test on 4 succeeded in 3 usecs
[ 23.092271] [drm] ring test on 5 succeeded in 2 usecs
[ 23.092276] [drm] UVD initialized successfully.
[ 23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
[ 23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
[ 23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
[ 23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
[ 23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
[ 33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35).
[ 33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-35).

lsb_release -rd:
Description: Ubuntu 16.04 LTS
Release: 16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu May 12 20:43:03 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0e6]
Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] [144d:c0e6]
InstallationDate: Installed on 2016-05-13 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P05ADH.017.140421.SH
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP680Z5E-X01US
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 870Z5E/880Z5E/680Z5E
dmi.product.version: P05ADH
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu May 12 20:35:57 2016
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 4845
vendor AUO
xserver.version: 2:1.18.3-1ubuntu2

See original description

Tags:

Revision history for this message

Brian Foster (bdfoster89-w) wrote on 2016-05-13:

dmesg | grep drm Edit (5.3 KiB, text/plain)
BootLog.txt Edit (4.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (92.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.4 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (1.2 MiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (297 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (15.0 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (3.2 KiB, text/plain; charset="utf-8")
LightdmGreeterLog.txt Edit (16.1 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (16.0 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (11.1 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (7.5 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (112 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (4.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (6.0 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (221.1 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (612 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (42.6 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (42.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (7.4 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (11.6 KiB, text/plain; charset="utf-8")
xserver.devices.txt Edit (535 bytes, text/plain; charset="utf-8")

Revision history for this message

Brian Foster (bdfoster89-w) wrote on 2016-05-13:

syslog Edit (188.1 KiB, text/plain)

Revision history for this message

Brian Foster (bdfoster89-w) wrote on 2016-05-13:

glxgears Edit (1.7 KiB, text/plain)

Brian Foster (bdfoster89-w) on 2016-05-13

description:

updated

Revision history for this message

Brian Foster (bdfoster89-w) wrote on 2016-05-13:

glxgears-2 Edit (6.1 KiB, text/plain)

# /etc/default/grub
...
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.modeset=1 radeon.drm=1 radeon.runpm=0"
...

Result of `DRI_PRIME=1 glxgears -info` attached. Visible and smooth animation runs (no black window).

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-05-29:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status:	New → Confirmed

Alberto Salvia Novella (es20490446e) on 2016-06-01

Changed in xorg (Ubuntu):
importance:	Undecided → High

Revision history for this message

Levente Ábrók (lev258) wrote on 2016-06-05:

Would like to join in on this bug.
I have a laptop with Intel Haswell and AMD Radeon HD 8850M / R9 M265X. I can't change to the dedicated GPU no matter how I try. My error messages in dmesg are basically the same as mentioned above.
Also, when I stop lightdm I get the title error: [drm:si_resume [radeon]] *ERROR* si startup failed on resume.
Using DIS on vgaswitcheroo file just gives me a black screen. I am on Ubuntu 16.04.
Tried with the Grub parameters mentioned and without them. Still have the issue.

Revision history for this message

Levente Ábrók (lev258) wrote on 2016-06-05:

dmesg.txt Edit (2.1 KiB, text/plain)

Don't know if it helps, but I ran DRI_PRIME=1 glxinfo|grep "OpenGL renderer". Seems like the only way to get some reaction from the dedicated one other than black screen.
Attached dmesg output about this.

Revision history for this message

Levente Ábrók (lev258) wrote on 2016-06-09:

Some news.
I updated the kernel to 4.4.13. Now I don't have error messages is dmesg.
Added radeon.dpm=1 radeon.modeset=1 to /etc/default/grub file (not sure if everything is needed).
sudo update-grub and reboot
Although I still cannot switch between the cards with DDIS, but I can run specific programs with the dedicated AMD, using DRI_PRIME=1 programpathname. That is already quite good, because I don't need the dedicated for browsing the web or so.

Revision history for this message

Brian Foster (bdfoster89-w) wrote on 2016-06-09: Re: [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

Download full text (6.2 KiB)

Same result for 4.4.10
On Jun 9, 2016 3:56 PM, "Levente Ábrók" <email address hidden> wrote:

Same result for 4.4.10
On Jun 9, 2016 3:56 PM, "Levente Ábrók" <lev258@freemail.hu> wrote:

> Some news.
> I updated the kernel to 4.4.13. Now I don't have error messages is dmesg.
> Added radeon.dpm=1 radeon.modeset=1 to /etc/default/grub file (not sure if
> everything is needed).
> sudo update-grub and reboot
> Although I still cannot switch between the cards with DDIS, but I can run
> specific programs with the dedicated AMD, using DRI_PRIME=1
> programpathname. That is already quite good, because I don't need the
> dedicated for browsing the web or so.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1581270
>
> Title:
>   Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
>   resume
>
> Status in xorg package in Ubuntu:
>   Confirmed
>
> Bug description:
>   dmesg shows issues with being able to use the discrete graphics card
>   (relevant dmesg lines attached).
>
>   Grub does pass "radeon.modeset=1" but it doesn't seem to make a
>   difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
>   the kernel, then it does not error (except for the VCE error -110,
>   which is probably harmless).
>
>   Running `DRI_PRIME=1 glxgears`:
>   - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a
> black window with a visible top bar.
>   - with just "radeon.modeset=1", error (attached as 'glxgears').
>
>   Results are similar on Ubuntu GNOME 16.04, except with
>   "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
>   screen tearing.
>
>   Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
>   attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:
>
>   [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
>   [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
>   [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
>   [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
>   [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
>   [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
>   [   23.092276] [drm] UVD initialized successfully.
>   [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
>   [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
>   [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
>   [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
>   [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
>   [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence
> wait failed (-35).
>   [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon:
> failed testing IB on ring 5 (-35).
>
>   lsb_release -rd:
>   Description:  Ubuntu 16.04 LTS
>   Release:      16.04
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
>   Uname: Linux 4.4.0-22-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Thu May 12 20:43:03 2016
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>    Intel Corporation 3rd Gen Core processor Graphics Controller
> [8086:0166] (rev 09) (prog-if 00 [VGA controller])
>      Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics
> Controller [144d:c0e6]
>      Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD
> 8670A/8670M/8750M] [144d:c0e6]
>   InstallationDate: Installed on 2016-05-13 (0 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed
> root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash
> radeon.modeset=1 vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/21/2014
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: P05ADH.017.140421.SH
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: NP680Z5E-X01US
>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.board.version: SEC_SW_REVISION_1234567890ABCD
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.chassis.version: N/A
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:
> bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
>   dmi.product.name: 870Z5E/880Z5E/680Z5E
>   dmi.product.version: P05ADH
>   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.67-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160325-1ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>   xserver.bootTime: Thu May 12 20:35:57 2016
>   xserver.configfile: default
>   xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>    product id                                4845
>    vendor                                     AUO
>   xserver.version: 2:1.18.3-1ubuntu2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+subscriptions
>

Revision history for this message

Claudio Pacchierotti (cpacchierotti) wrote on 2016-06-10:

#10

Using 4.4.0-24-generic from 16.04, I still have the issue.

$ DRI_PRIME=1 glxgears

gives black screen

and

$ DRI_PRIME=1 glxinfo|grep "OpenGL renderer"
OpenGL renderer string: Gallium 0.4 on AMD OLAND (DRM 2.43.0, LLVM 3.8.0)

I have a Radeon R7 M265.

Revision history for this message

Tenten36 (tenten) wrote on 2016-07-27:

#11

The problem still exists with kernel 4.6 and 4.7 from the mainline build.

$ DRI_PRIME=1 glxgears

gives black screen

Revision history for this message

Levente Ábrók (lev258) wrote on 2016-07-28:

#12

"Tenten36 (tenten) wrote on 2016-07-27:

The problem still exists with kernel 4.6 and 4.7 from the mainline build.

$ DRI_PRIME=1 glxgears

gives black screen"

That seems like a regression or the newest kernels weren't patched. Currently using 4.4.14 and it still works.

Revision history for this message

George Velimachitis (gvelim) wrote on 2016-09-08:

#13

I confirm the above findings on latest Linux Mint available kernel 4.4.0.36 however I also noticed

sudo DRI_PRIME=1 glxgears works

whereas

DRI_PRIME=1 glxgears gives a blank screen.

Revision history for this message

George Velimachitis (gvelim) wrote on 2016-09-11:

#14

I have managed to get a solution for this issue by following the below steps

Scenario 1:

1. Set intel to UXA mode and activate radeon DRI3 using the below xorg.conf settings
2. Restart mdm by login out and loggin in again (I have experience very slow rendering login page - Linux mint)
3. Issue command: DRI_PRIME=1 glxinfo|grep "OpenGL"( you will see the Radeon renderer active)
4. Issue command: DRI_PRIME=1 cairo_dock& (cairo starts without problems)

PS: grub kernel were left its distro's default settings.

Section "Device"
Identifier "Radeon"
Driver "intel"
  Option "AccelMethod" "UXA"
  Option "SwapbuffersWait" "false"
  Option "VSync" "false"
  Option "DRI" "3"
EndSection

Section "Device"
Identifier "Radeon"
Driver "radeon"
  Option "SwapbuffersWait" "false"
  Option "TearFree" "false"
  Option "DRI" "3"
EndSection

Scenario 2:
=======================
1. Set intel to SNA mode and activate radeon DRI3
2. Restart mdm by login out and loggin in again (screen rendering is fast)
3. Issue command: DRI_PRIME=1 glxinfo|grep "OpenGL"( I can only see the Intel tenderer)
4. Issue command: DRI_PRIME=1 cairo_dock& (cairo starts without problems)

I hope this helps

Revision history for this message

George Velimachitis (gvelim) wrote on 2016-09-11:

#15

Minor correction...

Both Scenarios allow the discreet/radeon card to render as expected however there is a different problem which is visible when you run for example..

DRI_PRIME=1 chromium_browser &

The window doesn't render unless you resize it couple of times and then the application becomes visible and user responsive. Also right clicking within the browser window gives empty rectangular.
The chrome://flags have both H/W acceleration and rasterisation to true

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-05-24:

#16

Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end of standard support in April 2021:

https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 16.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm

Changed in xorg (Ubuntu):
status:	Confirmed → Won't Fix

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntuxorg package

Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
xorg package

Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume