Bug 92722

Summary: radeon 0000:01:00.0: VCE init error (-22) on Kernel >= 4.2
Product: DRI Reporter: lbl <lblmr>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: andis.lazdins, dev, Rondom, sengupta01.saurav
Version: unspecified   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Ouput from dmesg
none
Sample Xorg configuration for radeon
none
Xorg log for radeon none

Description lbl 2015-10-29 07:06:22 UTC 
Hey guys, 

When I run any 4.2 kernel, I get this VCE init error

Oct 28 21:44:46 hosty kernel: [drm] PCIE gen 3 link speeds already enabled
Oct 28 21:44:46 hosty kernel: [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000).
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: WB enabled
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff88021d960c00
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff88021d960c04
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff88021d960c08
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff88021d960c0c
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff88021d960c10
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: VCE init error (-22).
Oct 28 21:44:46 hosty kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Oct 28 21:44:46 hosty kernel: [drm] Driver supports precise vblank timestamp query.
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: radeon: MSI limited to 32-bit
Oct 28 21:44:46 hosty kernel: radeon 0000:01:00.0: radeon: using MSI.
Oct 28 21:44:46 hosty kernel: [drm] radeon: irq initialized.


More info here: https://bugzilla.redhat.com/show_bug.cgi?id=1262649#c4
Comment 1 Lara Maia 2015-12-24 06:29:04 UTC 
Created attachment 120674 [details]
Ouput from dmesg
Comment 2 Saurav 2016-04-01 10:53:30 UTC 
Created attachment 122659 [details]
Sample Xorg configuration for radeon

Sample Xorg configuration for using the radeon driver, adapted from the one used by Ubuntu for fglrx.
Comment 3 Saurav 2016-04-01 10:54:51 UTC 
Created attachment 122660 [details]
Xorg log for radeon

Xorg log when trying to use the radeon driver.
Comment 4 Saurav 2016-04-01 10:55:19 UTC 
I have attached a sample Xorg configuration for using the radeon driver, basically the Ubuntu fglrx configuration (fglrx works on Ubuntu 15.10) with "fglrx" replaced by "radeon".

The radeon driver basically seems unable to find a screen to its liking, 
> (EE) RADEON(0): No modes.
> (EE) Screen(s) found, but none have a usable configuration.
and then gives up altogether:-
> (EE) no screens found(EE)

This happens irrespective of whether the module parameter radeon.runpm = 0 or not. Trying to use vga_switcheroo with echo DDIS > /sys/kernel/debug/vgaswitcheroo/switch results in a reversion to the login screen with a message saying that client 0 refused to switch, or in a totally black screen (but the system keeps working and can be powered off normally by pressing the power button), after logging out, depending on the display manager being used (the former typically happens with GDM).
Comment 5 Michel Dänzer 2016-04-04 07:54:38 UTC 
(In reply to Saurav from comment #4)
> The radeon driver basically seems unable to find a screen to its liking, 
> > (EE) RADEON(0): No modes.
> > (EE) Screen(s) found, but none have a usable configuration.
> and then gives up altogether:-
> > (EE) no screens found(EE)

That doesn't look related to this bug report. Please file your own report, including the corresponding dmesg output.
Comment 6 Saurav 2016-04-04 10:15:22 UTC 
(In reply to Michel Dänzer from comment #5)
> (In reply to Saurav from comment #4)
> > The radeon driver basically seems unable to find a screen to its liking, 
> > > (EE) RADEON(0): No modes.
> > > (EE) Screen(s) found, but none have a usable configuration.
> > and then gives up altogether:-
> > > (EE) no screens found(EE)
> 
> That doesn't look related to this bug report. Please file your own report,
> including the corresponding dmesg output.

Reported in bug #94811.
Comment 7 Martin Peres 2019-11-19 09:09:09 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/drm/amd/issues/655.

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.