Bug 108030 - Does not work discrete graphics CERAR (6370M)
Summary: Does not work discrete graphics CERAR (6370M)
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: 18.1
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-23 12:42 UTC by Илья Индиго
Modified: 2019-09-18 19:26 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg (61.42 KB, text/x-log)
2018-09-24 14:45 UTC, Илья Индиго
Details
xorg.log (42.22 KB, text/x-log)
2018-09-24 14:45 UTC, Илья Индиго
Details
xsessions-errors (18.57 KB, text/plain)
2018-09-24 14:46 UTC, Илья Индиго
Details

Description Илья Индиго 2018-09-23 12:42:39 UTC
Only integrated graphics Intel works.
When running graphics applications with DRI_PRIME=1, this application or segfault or show a black screen (sometimes playing a sound).
Sometimes, with some probability, this leads to crash Xorg.

In the logs there is nothing suspicious or any errors, only segfault.
I attached some logs, if this is not enough, then tell me which file or output of which command I have to attach.

I want to either with DRI_PRIME=1 worked discrete graphics or worked all the time only discrete graphics.
Is this possible on the open drivers with the latest software?

Notebook: HP Pavilion dv6 with hybrid graphics (Intel 3000HD/Radeon HD 6370M CEDAR)
OS: openSUSE Tumbleweed (4.18.8-1-default, LLVM 6.0.1, Mesa 18.1.7)

sudo cat /sys/kernel/debug/vgaswitcheroo/switch
0:DIS: :DynOff:0000:01:00.0
1:IGD:+:Pwr:0000:00:02.0
2:DIS-Audio: :DynOff:0000:01:00.1

glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile
OpenGL version string: 2.1 Mesa 18.1.7
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.1.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:

DRI_PRIME=1 glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: AMD CEDAR (DRM 2.50.0 / 4.18.8-1-default, LLVM 6.0.1)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.1.7
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.1 Mesa 18.1.7
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.1.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

dmesg | grep -i radeon
[ 8604.934090] radeon 0000:01:00.0: WB enabled
[ 8604.934094] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0x00000000615bbe52
[ 8604.934095] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0x000000001a943f21
[ 8604.934469] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0x000000006515891a
Comment 1 Alex Deucher 2018-09-24 13:23:38 UTC
Please attach your xorg log (if using X) and dmesg output.
Comment 2 Илья Индиго 2018-09-24 14:45:03 UTC
Created attachment 141711 [details]
dmesg
Comment 3 Илья Индиго 2018-09-24 14:45:43 UTC
Created attachment 141712 [details]
xorg.log
Comment 4 Илья Индиго 2018-09-24 14:46:16 UTC
Created attachment 141713 [details]
xsessions-errors
Comment 5 GitLab Migration User 2019-09-18 19:26:19 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/mesa/mesa/issues/645.


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.