Bug 106796 - xserver fails to start: [DRI2] no driver mapping found for PCI device 0x8086 / 0x0be1
Summary: xserver fails to start: [DRI2] no driver mapping found for PCI device 0x8086 ...
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Acceleration/glamor (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
Keywords: bisected, regression
Depends on:
Reported: 2018-06-03 17:13 UTC by Stephan Hilb
Modified: 2018-12-13 18:25 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

failing log (20.18 KB, text/x-log)
2018-06-03 17:13 UTC, Stephan Hilb
no flags Details
working log (25.11 KB, text/x-log)
2018-06-03 17:23 UTC, Stephan Hilb
no flags Details

Description Stephan Hilb 2018-06-03 17:13:10 UTC
Created attachment 139989 [details]
failing log

Since updating to xorg-server 1.20, the xserver failed to start (see log).
Seems it tries to do glamor acceleration and fails to find a DRI2 driver mapping, while previously it didn't even initialize glamor.

Bisecting shows as first bad commit

commit 59de50d6ef3331ee03eb82d4acba45aa75c70d42 (refs/bisect/bad)
Author: Eric Anholt <eric@anholt.net>
Date:   Tue May 16 11:37:20 2017 -0700

    glamor_egl: Avoid flink names in glamor_egl_create_textured_pixmap().
    Using flink is banned on render nodes, and they needlessly expose our
    screen pixmap contents to any authenticated client.  This also
    incidentally drops the dependency on EGL_MESA_drm_image.
    Reviewed-by: Adam Jackson <ajax@redhat.com>
    Signed-off-by: Eric Anholt <eric@anholt.net>

$ sudo lspci -vvv -d 8086:0be1
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Acer Incorporated [ALI] Atom Processor D2xxx/N2xxx Integrated Graphics Controller
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 28
	Region 0: Memory at c6000000 (32-bit, non-prefetchable) [size=1M]
	Region 1: I/O ports at 50d0 [size=8]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [d0] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [b0] Vendor Specific Information: Len=07 <?>
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee02004  Data: 4024
	Kernel driver in use: gma500
	Kernel modules: gma500_gfx

Let me know if I can provide anything else.
Comment 1 Stephan Hilb 2018-06-03 17:23:07 UTC
Created attachment 139990 [details]
working log
Comment 2 alvarito512 2018-07-01 04:38:03 UTC
Seems like since 1.20, xorg changed behavieur to enable Glamor on any ""Intel"" GPU, even if their are not using intel driver. And since GMA500 doesn't support DRI2, it crashes.
As a workaround, you can manually disable glamor with the xorg config option:
    Option "AccelMethod" "none"
Comment 3 Stephan Hilb 2018-07-02 19:40:07 UTC
Thanks for the workaround, it works for me.
I'm still leaving this open since we should probably detect unsupported (intel?) drivers before doing glamor.
Comment 4 GitLab Migration User 2018-12-13 18:25:55 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/xorg/xserver/issues/102.

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.