Package Details: linux-drm-tip-git 5.14.r1029802.5e0ea887acd4-1

Git Clone URL: (read-only, click to copy)
Package Base: linux-drm-tip-git
Description: The Linux kernel with bleeding-edge GPU drivers kernel and modules
Upstream URL:
Keywords: amdgpu drm git intel iris kernel linux
Licenses: GPL2
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: cdown
Maintainer: yurikoles
Last Packager: yurikoles
Votes: 4
Popularity: 0.000000
First Submitted: 2017-03-08 14:47 (UTC)
Last Updated: 2021-07-15 16:38 (UTC)

Pinned Comments

yurikoles commented on 2019-06-07 08:08 (UTC) (edited on 2019-06-07 08:09 (UTC) by yurikoles)

PRs are welcome:

Latest Comments

1 2 3 Next › Last »

rayzorben commented on 2022-07-30 23:29 (UTC)

It's 2022 so I didn't think the previous issue in 2020 would still be around, although it seems related. Build fails for me, and the closest error output is this. Any idea what to do to get past this?

drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c:806:20: error: passing argument 1 of ‘mutex_lock’ from incompatible pointer type [-Werror=incompatible-pointer-types]
  806 |         mutex_lock(&mgr->lock);
      |                    ^~~~~~~~~~
      |                    |
      |                    spinlock_t * {aka struct spinlock *}
./include/linux/mutex.h:199:38: note: expected ‘struct mutex *’ but argument is of type ‘spinlock_t *’ {aka ‘struct spinlock *’}
  199 | extern void mutex_lock(struct mutex *lock);
      |                        ~~~~~~~~~~~~~~^~~~
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c:814:9: error: implicit declaration of function ‘drm_buddy_fini’ [-Werror=implicit-function-declaration]
  814 |         drm_buddy_fini(&mgr->mm);
      |         ^~~~~~~~~~~~~~
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c:815:22: error: passing argument 1 of ‘mutex_unlock’ from incompatible pointer type [-Werror=incompatible-pointer-types]
  815 |         mutex_unlock(&mgr->lock);
      |                      ^~~~~~~~~~
      |                      |
      |                      spinlock_t * {aka struct spinlock *}
./include/linux/mutex.h:218:40: note: expected ‘struct mutex *’ but argument is of type ‘spinlock_t *’ {aka ‘struct spinlock *’}
  218 | extern void mutex_unlock(struct mutex *lock);
      |                          ~~~~~~~~~~~~~~^~~~
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c: In function ‘amdgpu_vram_mgr_first_block’:
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c:57:1: error: control reaches end of non-void function [-Werror=return-type]
   57 | }
      | ^
cc1: some warnings being treated as errors

jghodd commented on 2020-05-30 19:42 (UTC) (edited on 2020-05-30 20:24 (UTC) by jghodd)

@yurikoles the issue is still there. reported at the link you provided - issue 1156 -

Edit: here's a patch to fix it.


--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c  2020-05-30 10:34:11.738183991 -0400
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c  2020-05-30 16:01:12.296946979 -0400
@@ -1354,7 +1354,7 @@

        /* Free the BO*/
-       drm_gem_object_put_unlocked(&mem->bo->tbo.base);
+       drm_gem_object_put(&mem->bo->tbo.base);

jghodd commented on 2020-05-30 14:31 (UTC) (edited on 2020-05-30 14:36 (UTC) by jghodd)

@yurikoles thanks for the link. i worked around the issue by commenting out the AMDGPU option in the config file since what i really needed were the Intel modules anyway. i noticed that torvalds signed off on 5.7-rc7 a few days ago, so i presume that the build error has been fixed. i'll be doing a new build today with AMDGPU restored to config, so i guess i'll see if the problem is gone. cheers.

yurikoles commented on 2020-05-24 20:09 (UTC)

@jghodd sorry for outdated info. The new bug tracker is here:

jghodd commented on 2020-05-21 10:26 (UTC)

@yurikoles i'm unable to create a new bug at - the message " Bugzilla is no longer in use" is displayed prominently across the page. does not have this build error in its archive. the alternative listed at,, does not have this project and its search function turns up nothing. your other project, linux-drm-intel-next-git is also not building with another "cc1: warnings being treated as errors" message.

i have to assume that the developers must be doing builds along the way as source is being merged in. how are they not finding these build errors?

yurikoles commented on 2020-05-20 17:40 (UTC)

Please report this on and

jghodd commented on 2020-05-20 17:37 (UTC)

Getting a build error for the past 2 days. Done multiple build attempts:

drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c: In function ‘amdgpu_amdkfd_gpuvm_free_memory_of_gpu’: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c:1357:2: error: implicit declaration of function ‘drm_gem_object_put_unlocked’; did you mean ‘drm_gem_object_put_locked’? [-Werror=implicit-function-declaration] 1357 | drm_gem_object_put_unlocked(&mem->bo->tbo.base); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ | drm_gem_object_put_locked cc1: some warnings being treated as errors

jghodd commented on 2020-05-18 16:13 (UTC) (edited on 2020-05-19 00:11 (UTC) by jghodd)

The more recent builds no longer boot. It gets past the grub menu to loading initrd, then just hangs. Any ideas?

Edit: apparently, the fix for this issue is in 5.7-rc6 (