dri-devel June 2015

dri-devel@lists.freedesktop.org

188 participants
1140 discussions

[Bug 87856] Driver load fails with no error on ppc64 host
by bugzilla-daemon＠freedesktop.org 30 Apr '16

30 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=87856 Bug ID: 87856 Summary: Driver load fails with no error on ppc64 host Product: Mesa Version: 10.2 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: freedesktopbugs(a)63bit.net Created attachment 111507 --> https://bugs.freedesktop.org/attachment.cgi?id=111507&action=edit Xorg log, dmesg | fgrep radeon, and glxinfo with LIBGL_DEBUG set I have a PowerPC G5 (ppc64 with 64-bit userland) with working KMS using a (ostensibly x86) Radeon HD4650. KMS is enabled and the kernel and Xorg parts of KMS/DRI2 appear to be attaching correctly. After X starts, running LIBGL_DEBUG=verbose glxinfo outputs the following: libGL: OpenDriver: trying /usr/lib64/dri/tls/r600_dri.so libGL: OpenDriver: trying /usr/lib64/dri/r600_dri.so libGL: driver does not expose __driDriverGetExtensions_r600(): /usr/lib64/dri/r600_dri.so: undefined symbol: __driDriverGetExtensions_r600 libGL: Can't open configuration file /root/.drirc: No such file or directory. libGL: Can't open configuration file /root/.drirc: No such file or directory. libGL error: failed to load driver: r600 libGL: OpenDriver: trying /usr/lib64/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib64/dri/swrast_dri.so libGL: driver does not expose __driDriverGetExtensions_swrast(): /usr/lib64/dri/swrast_dri.so: undefined symbol: __driDriverGetExtensions_swrast libGL: Can't open configuration file /root/.drirc: No such file or directory. libGL: Can't open configuration file /root/.drirc: No such file or directory. libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig Error: couldn't find RGB GLX visual or fbconfig I am under the impression that the undefined symbol should not be causing problems after reading this bug: https://bugs.freedesktop.org/show_bug.cgi?id=72198 Nonetheless, glxgears will not run, and in general it appears mesa acceleration is not occurring. Mesa was compiled with support for llvm and the r600 generator. I am attaching various logs. I would be glad to test patches or hacks :) -- You are receiving this mail because: You are the assignee for the bug.

1 16

[PATCH v8 00/11] Add DRM for stih4xx platforms
by Benjamin Gaignard 22 Apr '16

22 Apr '16

This series of patches add the support of DRM/KMS drivers for STMicroelectronics chipsets stih416 and stih407. version 8: - Allow driver to be build as kernel module. - Use Universal Plane instead of legacy code. patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v8 version 7: - rebased on top of drm-next (2014-07-24) patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v7 version 6: - rebased on top of new component framework API. patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v6 version 5: - Rework sti_drm_drv probes functions to support deferred probe. This allow hdmi to delayed framebuffer creation until I2C is available. - Add ops functions in sti_layer structure to simpify GDP and VID code. - Add NOTES file to describe how the DRM concepts are mapped on hardware. patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v5 version 4: - Remove depency between TVout it subdevices HDMI and HDA - Rework and simplify VTG and VTAC code - Fix numbers of typo and indentation - Remove debug (will be push in separate patches) - Fix remarks done in previous patcheset patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v4 version 3: - Correctly split code between probe and bind funtions - Squash some commits - remove HQ-VDP device code to have a smaller patcheset, we will introduce it later. patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v3 version 2: - Use componentized device instead of register sub-devices in master driver probe function - Fix Makefile and Kconfig to only allow built-in compilation patches could be found here: git://git.linaro.org/people/benjamin.gaignard/kernel.git on branch: drm_kms_for_next-v2 version 1: - First path submission Hardware is split in two main blocks: Compositor and TVout. Each of them includes specific hardware IPs and the display timing are controlled by a specific Video Timing Generator hardware IP (VTG). Compositor is made of the follow hardware IPs: - GDP (Generic Display Pipeline) which is an entry point for graphic (RGB) buffers - VDP (Video Diplay Pipeline) which is an entry point for video (YUV) buffers - HQVDP (High Quality Video Display Processor) that supports scaling, deinterlacing and some miscellaneous image quality improvements. It fetches the Video decoded buffers from memory, processes them and pushes them to the Compositor through a HW dedicated bus. - Mixer is responsible of mixing all the entries depending of their respective z-order and layout TVout is divided in 3 parts: - HDMI to generate HDMI signals, depending of chipset version HDMI phy can change. - HDA to generate signals for HD analog TV - VIP to control/switch data path coming from Compositor On stih416 compositor and Tvout are on different dies so a Video Trafic Advance inter-die Communication mechanism (VTAC) is needed. +---------------------------------------------+ +----------------------------------------+ | +-------------------------------+ +----+ | | +----+ +--------------------------+ | | | | | | | | | | | +---------+ +----+ | | | | +----+ +------+ | | | | | | | | | VIP |---->|HDMI| | | | | |GPD +------------->| | | | | | | | | | | | +----+ | | | | +----+ |Mixer |--|-->| | | | | |---|->| switcher| | | | | | | | | | | | | | | | | +----+ | | | | | | | | | | | | | | | |---->|HDA | | | | | +------+ | |VTAC|========>|VTAC| | +---------+ +----+ | | | | | | | | | | | | | | | | Compositor | | | | | | | | TVout | | | +-------------------------------+ | | | | | | +--------------------------+ | | ^ | | | | | | ^ | | | | | | | | | | | | +--------------+ | | | | | | +-------------+ | | | VTG (master) |----->| | | | | |----->| VTG (slave) | | | +--------------+ +----+ | | +----+ +-------------+ | |Digital die | | Analog Die| +---------------------------------------------+ +----------------------------------------+ On stih407 Compositor and Tvout are on the same die +-----------------------------------------------------------------+ | +-------------------------------+ +--------------------------+ | | | | | +---------+ +----+ | | | | +----+ +------+ | | | VIP |---->|HDMI| | | | | |GPD +------------->| | | | | | +----+ | | | | +----+ |Mixer |--|--|->| switcher| | | | | +----+ +-----+ | | | | | | +----+ | | | | |VDP +-->+HQVDP+--->| | | | | |---->|HDA | | | | | +----+ +-----+ +------+ | | +---------+ +----+ | | | | | | | | | | Compositor | | TVout | | | +-------------------------------+ +--------------------------+ | | ^ ^ | | | | | | +--------------+ | | | VTG | | | +--------------+ | |Digital die | +-----------------------------------------------------------------+ In addition of the drivers for the IPs listed before a thin I2C driver (hdmiddc) is used by HDMI driver to retrieve EDID for monitor. To unify interfaces of GDP and VDP we create a "layer" interface called by compositor to control both GPD and VDP. Hardware have memory contraints (alignment, contiguous) so we use CMA drm helpers functions to allocate frame buffer. File naming convention is: - sti_* for IPs drivers - sti_drm_* for drm functions implementation. Benjamin Gaignard (11): drm: sti: add bindings for DRM driver drm: sti: add VTG driver drm: sti: add VTAC drivers drm: sti: add HDMI driver drm: sti: add HDA driver drm: sti: add TVOut driver drm: sti: add GDP layer drm: sti: add VID layer drm: sti: add Mixer drm: sti: add Compositor drm: sti: Add DRM driver itself .../devicetree/bindings/gpu/st,stih4xx.txt | 189 +++++ drivers/gpu/drm/Kconfig | 2 + drivers/gpu/drm/Makefile | 1 + drivers/gpu/drm/sti/Kconfig | 14 + drivers/gpu/drm/sti/Makefile | 21 + drivers/gpu/drm/sti/NOTES | 58 ++ drivers/gpu/drm/sti/sti_compositor.c | 279 +++++++ drivers/gpu/drm/sti/sti_compositor.h | 90 +++ drivers/gpu/drm/sti/sti_drm_crtc.c | 423 +++++++++++ drivers/gpu/drm/sti/sti_drm_crtc.h | 22 + drivers/gpu/drm/sti/sti_drm_drv.c | 241 ++++++ drivers/gpu/drm/sti/sti_drm_drv.h | 29 + drivers/gpu/drm/sti/sti_drm_plane.c | 195 +++++ drivers/gpu/drm/sti/sti_drm_plane.h | 18 + drivers/gpu/drm/sti/sti_gdp.c | 549 ++++++++++++++ drivers/gpu/drm/sti/sti_gdp.h | 16 + drivers/gpu/drm/sti/sti_hda.c | 794 ++++++++++++++++++++ drivers/gpu/drm/sti/sti_hdmi.c | 810 +++++++++++++++++++++ drivers/gpu/drm/sti/sti_hdmi.h | 88 +++ drivers/gpu/drm/sti/sti_hdmi_tx3g0c55phy.c | 336 +++++++++ drivers/gpu/drm/sti/sti_hdmi_tx3g0c55phy.h | 14 + drivers/gpu/drm/sti/sti_hdmi_tx3g4c28phy.c | 211 ++++++ drivers/gpu/drm/sti/sti_hdmi_tx3g4c28phy.h | 14 + drivers/gpu/drm/sti/sti_layer.c | 197 +++++ drivers/gpu/drm/sti/sti_layer.h | 123 ++++ drivers/gpu/drm/sti/sti_mixer.c | 249 +++++++ drivers/gpu/drm/sti/sti_mixer.h | 54 ++ drivers/gpu/drm/sti/sti_tvout.c | 648 +++++++++++++++++ drivers/gpu/drm/sti/sti_vid.c | 138 ++++ drivers/gpu/drm/sti/sti_vid.h | 12 + drivers/gpu/drm/sti/sti_vtac.c | 215 ++++++ drivers/gpu/drm/sti/sti_vtg.c | 366 ++++++++++ drivers/gpu/drm/sti/sti_vtg.h | 28 + 33 files changed, 6444 insertions(+) create mode 100644 Documentation/devicetree/bindings/gpu/st,stih4xx.txt create mode 100644 drivers/gpu/drm/sti/Kconfig create mode 100644 drivers/gpu/drm/sti/Makefile create mode 100644 drivers/gpu/drm/sti/NOTES create mode 100644 drivers/gpu/drm/sti/sti_compositor.c create mode 100644 drivers/gpu/drm/sti/sti_compositor.h create mode 100644 drivers/gpu/drm/sti/sti_drm_crtc.c create mode 100644 drivers/gpu/drm/sti/sti_drm_crtc.h create mode 100644 drivers/gpu/drm/sti/sti_drm_drv.c create mode 100644 drivers/gpu/drm/sti/sti_drm_drv.h create mode 100644 drivers/gpu/drm/sti/sti_drm_plane.c create mode 100644 drivers/gpu/drm/sti/sti_drm_plane.h create mode 100644 drivers/gpu/drm/sti/sti_gdp.c create mode 100644 drivers/gpu/drm/sti/sti_gdp.h create mode 100644 drivers/gpu/drm/sti/sti_hda.c create mode 100644 drivers/gpu/drm/sti/sti_hdmi.c create mode 100644 drivers/gpu/drm/sti/sti_hdmi.h create mode 100644 drivers/gpu/drm/sti/sti_hdmi_tx3g0c55phy.c create mode 100644 drivers/gpu/drm/sti/sti_hdmi_tx3g0c55phy.h create mode 100644 drivers/gpu/drm/sti/sti_hdmi_tx3g4c28phy.c create mode 100644 drivers/gpu/drm/sti/sti_hdmi_tx3g4c28phy.h create mode 100644 drivers/gpu/drm/sti/sti_layer.c create mode 100644 drivers/gpu/drm/sti/sti_layer.h create mode 100644 drivers/gpu/drm/sti/sti_mixer.c create mode 100644 drivers/gpu/drm/sti/sti_mixer.h create mode 100644 drivers/gpu/drm/sti/sti_tvout.c create mode 100644 drivers/gpu/drm/sti/sti_vid.c create mode 100644 drivers/gpu/drm/sti/sti_vid.h create mode 100644 drivers/gpu/drm/sti/sti_vtac.c create mode 100644 drivers/gpu/drm/sti/sti_vtg.c create mode 100644 drivers/gpu/drm/sti/sti_vtg.h -- 1.9.1

3 15

[Bug 44647] New: [wine regression] Call of Duty 4: Intro videos renders garbage
by bugzilla-daemon＠freedesktop.org 20 Apr '16

20 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=44647 Bug #: 44647 Summary: [wine regression] Call of Duty 4: Intro videos renders garbage Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sa(a)whiz.se Created attachment 55392 --> https://bugs.freedesktop.org/attachment.cgi?id=55392 Screenshot of broken video Intro videos in the game Call of Duty 4 (running with Wine) no longer renders correctly, bisecting leads to this: e8139ebf583acf37150a8b341bcbef6b924a7792 is the first bad commit commit e8139ebf583acf37150a8b341bcbef6b924a7792 Author: Mathias Fröhlich <Mathias.Froehlich(a)gmx.net> Date: Tue Jul 26 07:05:10 2011 +0200 r600g: Replace needless flush in texture upload. Replace pipe->flush() with pipe->texture_barrier() in the texture upload path for the staging texture. This should be enough to get data out of the gpu caches ready to be read for texture fetch. :040000 040000 b3f16d1a114f54d753ba7845b697888307f6246e faab26149053fdb2fb65d81bb2a777a77e130de2 M src Adding the flush back fixes the problem. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 90655] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
by bugzilla-daemon＠freedesktop.org 19 Apr '16

19 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=90655 Bug ID: 90655 Summary: [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM Product: DRI Version: XOrg git Hardware: PowerPC OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: mathieu.malaterre(a)gmail.com On my old Mac Mini G4 (PowerPC) I am seeing this dmesg output: [ 12.058859] [drm] Initialized drm 1.1.0 20060810 [ 13.051939] [drm] radeon kernel modesetting enabled. [ 13.055867] checking generic (9c008000 5a000) vs hw (98000000 8000000) [ 13.055875] fb: switching to radeondrmfb from OFfb ATY,RockHo [ 13.059702] Console: switching to colour dummy device 80x25 [ 13.060655] radeon 0000:00:10.0: enabling device (0006 -> 0007) [ 13.061195] [drm] initializing kernel modesetting (RV280 0x1002:0x5962 0x1002:0x5962). [ 13.061227] [drm] register mmio base: 0x90000000 [ 13.061236] [drm] register mmio size: 65536 [ 13.061318] radeon 0000:00:10.0: Invalid ROM contents [ 13.061341] radeon 0000:00:10.0: Invalid ROM contents [ 13.061356] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM [ 13.061379] [drm] Using device-tree clock info [ 13.061417] agpgart-uninorth 0000:00:0b.0: putting AGP V2 device into 4x mode [ 13.061433] radeon 0000:00:10.0: putting AGP V2 device into 4x mode [ 13.061484] radeon 0000:00:10.0: GTT: 256M 0x00000000 - 0x0FFFFFFF It would be nice to either remove this error report as I believe it is erroneous. Using debian/jessie with: $ apt-cache policy libdrm-radeon1 libdrm-radeon1: Installé : 2.4.58-2 Candidat : 2.4.58-2 Table de version : *** 2.4.58-2 0 500 http://ftp.fr.debian.org/debian/ jessie/main powerpc Packages 100 /var/lib/dpkg/status -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 89891] Outlast segfault on new game
by bugzilla-daemon＠freedesktop.org 19 Apr '16

19 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=89891 Bug ID: 89891 Summary: Outlast segfault on new game Product: Mesa Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: sa(a)whiz.se QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 114851 --> https://bugs.freedesktop.org/attachment.cgi?id=114851&action=edit backtrace with git version lsThe game Outlast (from the latest Humble Indie Bundle) segfaults when a new game is launched. With Mesa 10.4.2 I get a segfault in ir_assignment::ir_assignment. With current git I get a "radeon: mmap failed, errno: 12" and a segfault in __memcpy_ssse3. Another problem is that the game takes ages to start, about 90 seconds from start to menu. Most of this time is spent compiling more than 18000 shaders, so maybe that's just a problem with the game. System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: REDWOOD -- Model: XFX Radeon HD 5670 1GB -- Display connector: DVI -- xf86-video-ati: 7.5.0 -- xserver: 1.16.4 -- mesa: 10.4.2 -- drm: 2.4.58 -- kernel: 3.19 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 69623] New: Pink Pony misrenders - - shader requires 126 registers
by bugzilla-daemon＠freedesktop.org 19 Apr '16

19 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=69623 Priority: medium Bug ID: 69623 Assignee: dri-devel(a)lists.freedesktop.org Summary: Pink Pony misrenders - - shader requires 126 registers Severity: normal Classification: Unclassified OS: Linux (All) Reporter: sa(a)whiz.se Hardware: x86 (IA32) Status: NEW Version: 9.2 Component: Drivers/Gallium/r600 Product: Mesa Created attachment 86224 --> https://bugs.freedesktop.org/attachment.cgi?id=86224&action=edit Screenshot of bug The game Pink Pony (http://code.google.com/p/pink-pony/) does not render correctly with the r600g driver and Mesa 9.2, see attached screenshot. The following error is printed in the terminal: EE ../../../../../../src/gallium/drivers/r600/r600_shader.c:1580 r600_shader_from_tgsi - GPR limit exceeded - shader requires 126 registers EE ../../../../../../src/gallium/drivers/r600/r600_shader.c:158 r600_pipe_shader_create - translation from TGSI failed ! EE ../../../../../../src/gallium/drivers/r600/r600_state_common.c:754 r600_shader_select - Failed to build shader variant (type=0) -12 I'm not sure if this is the same problem as bug 68527. System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: REDWOOD -- Model: XFX Radeon HD 5670 1GB -- Display connector: DVI -- xf86-video-ati: 7.2.0 -- xserver: 1.12.4 -- mesa: 9.2 -- drm: 2.4.46 -- kernel: 3.11 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 90869] Rendering bug in The Witcher
by bugzilla-daemon＠freedesktop.org 19 Apr '16

19 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=90869 Bug ID: 90869 Summary: Rendering bug in The Witcher Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: sa(a)whiz.se QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 116318 --> https://bugs.freedesktop.org/attachment.cgi?id=116318&action=edit Screenshot of bug Hi, I'm trying to run the game The Witcher (in Wine) it has rendering errors when drawing the rain. This bug is present in both git master (78395dbf9ff429d98523f8b4a340f7188d8b4db0) and in 10.5.5. I made an apitrace of the game and it renders without problem on i965. Running the trace on r600 results in this warning: 101172: glDebugOutputCallback: Medium severity API unknown issue 1, FBO incomplete: driver marked FBO as incomplete [-1] This is on a Redwood, Radeon HD 5670 1GB. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[PATCH] drm: panel: simple-panel: remove useless drm_mode_set_name
by Boris Brezillon 18 Apr '16

18 Apr '16

drm_display_mode_from_videomode() is already calling drm_mode_set_name() on the provided mode. Signed-off-by: Boris Brezillon <boris.brezillon(a)free-electrons.com> --- drivers/gpu/drm/panel/panel-simple.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c index 30904a9..d14b904 100644 --- a/drivers/gpu/drm/panel/panel-simple.c +++ b/drivers/gpu/drm/panel/panel-simple.c @@ -112,7 +112,6 @@ static int panel_simple_get_fixed_modes(struct panel_simple *panel) } drm_display_mode_from_videomode(&vm, mode); - drm_mode_set_name(mode); drm_mode_probed_add(connector, mode); num++; -- 1.9.1

2 2

[PATCH] drm: panel: simple-panel: set appropriate mode type
by Boris Brezillon 18 Apr '16

18 Apr '16

All modes exposed by simple panels should be tagged as driver defined modes. Moreover, if a panel supports only one mode, this mode is obviously the preferred one. Doing this also fix a problem occurring when a 'video=' parameter is passed on the kernel cmdline. In some cases the user provided mode is preferred over the simple panel ones, which might result in unpredictable behavior. Signed-off-by: Boris Brezillon <boris.brezillon(a)free-electrons.com> --- drivers/gpu/drm/panel/panel-simple.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c index d14b904..95ae390 100644 --- a/drivers/gpu/drm/panel/panel-simple.c +++ b/drivers/gpu/drm/panel/panel-simple.c @@ -111,6 +111,10 @@ static int panel_simple_get_fixed_modes(struct panel_simple *panel) continue; } + mode->type |= DRM_MODE_TYPE_DRIVER; + if (panel->desc->num_modes == 1) + mode->type |= DRM_MODE_TYPE_PREFERRED; + drm_display_mode_from_videomode(&vm, mode); drm_mode_probed_add(connector, mode); @@ -127,6 +131,10 @@ static int panel_simple_get_fixed_modes(struct panel_simple *panel) continue; } + mode->type |= DRM_MODE_TYPE_DRIVER; + if (panel->desc->num_modes == 1) + mode->type |= DRM_MODE_TYPE_PREFERRED; + drm_mode_set_name(mode); drm_mode_probed_add(connector, mode); -- 1.9.1

3 5

[Bug 89661] New: Kernel panic when trying use amdkfd driver on Kaveri
by bugzilla-daemon＠bugzilla.kernel.org 13 Apr '16

13 Apr '16

https://bugzilla.kernel.org/show_bug.cgi?id=89661 Bug ID: 89661 Summary: Kernel panic when trying use amdkfd driver on Kaveri Product: Drivers Version: 2.5 Kernel Version: 3.18.0 + drm-next branch Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: linux(a)bernd-steinhauser.de Regression: No The kernel I tried to use was 3.18.0 and I merged the drm-next branch from git://people.freedesktop.org/~airlied/linux which includes the HSA driver amdkfd. CONFIG_HSA_AMD=y is set. When trying to boot the kernel, I get a kernel panic, as shown in the uploaded picture. CPU is a A10-7800 Kaveri, Motherboard is ASRock FM2A88X Extreme6+. -- You are receiving this mail because: You are watching the assignee of the bug.

1 18

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2015