AMDGPU driver throws "VMC Page fault"

412 views
Skip to first unread message

shahul hameed

unread,
Jun 22, 2018, 12:32:34 AM6/22/18
to Android-x86
Hi All,

I am trying to install AMDGPU modues in linux 4.16 with Android Nougat and I am facing following error when amdgpu.ko is loaded.

[  175.079776] [drm] amdgpu kernel modesetting enabled.
[  175.079778] [drm] [amdgpu_init: 924]
[  175.080363] [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x1002:0x0123 0xC1).
[  175.080384] [drm] register mmio base: 0xE0700000
[  175.080385] [drm] register mmio size: 524288
[  175.100606] [drm] probing gen 2 caps for device 1022:15db = 700d03/e
[  175.100610] [drm] probing mlw for device 1022:15db = 700d03
[  175.100760] [drm] VCN decode is enabled in VM mode
[  175.100761] [drm] VCN encode is enabled in VM mode
[  175.126667] [drm] BIOS signature incorrect 20 7
[  175.126675] resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000c3fff window]
[  175.126681] caller pci_map_rom+0x73/0xbf mapping multiple BARs
[  175.126729] ATOM BIOS: 113-RAVEN-032
[  175.126773] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
[  175.126784] amdgpu 0000:02:00.0: VRAM: 256M 0x000000F400000000 - 0x000000F40FFFFFFF (256M used)
[  175.126785] amdgpu 0000:02:00.0: GTT: 1024M 0x000000F500000000 - 0x000000F53FFFFFFF
[  175.126791] [drm] Detected VRAM RAM=256M, BAR=256M
[  175.126792] [drm] RAM width 64bits UNKNOWN
[  175.126931] [TTM] Zone  kernel: Available graphics memory: 3908708 kiB
[  175.126933] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[  175.126934] [TTM] Initializing pool allocator
[  175.126938] [TTM] Initializing DMA pool allocator
[  175.126982] [drm] amdgpu: 256M of VRAM memory ready
[  175.126983] [drm] amdgpu: 3072M of GTT memory ready.
[  175.127001] [drm] GART: num cpu pages 262144, num gpu pages 262144
[  175.127346] [drm] PCIE GART of 1024M enabled (table at 0x000000F400800000).
[  175.144578] [drm] use_doorbell being set to: [true]
[  175.150530] [drm] Found VCN firmware Version: 1.45 Family ID: 18
[  175.231103] [drm] Display Core initialized with v3.1.27!
[  175.256820] [drm] SADs count is: 0, don't need to read it
[  175.257490] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[  175.257491] [drm] Driver supports precise vblank timestamp query.
[  175.258862] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:217 vmid:0 pas_id:0)
[  175.258864] amdgpu 0000:02:00.0:   at page 0x0000000000000000 from 27
[  175.258865] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000BB2
[  175.258874] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:217 vmid:0 pas_id:0)
[  175.258875] amdgpu 0000:02:00.0:   at page 0x0000000000001000 from 27
[  175.258877] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000BB2

Please help me in which area the problem could be.
Is it in kernel itself or in libdrm, mesa, llvm or hwcomposer?

Regards,
Shahul

shahul hameed

unread,
Jun 22, 2018, 12:46:38 AM6/22/18
to Android-x86
Hi Maurossi,

Can you help me with this? I am stuck with this from long time.

Regards,
Shahul

Mauro Rossi

unread,
Jun 22, 2018, 4:22:07 AM6/22/18
to Android-x86
Not sure it's related, but you may have a look at this: https://bugzilla.redhat.com/show_bug.cgi?id=1562946

So you could try with kernel-4.17 [1] or kernel-4.18rc1 [2]

With latest kernels it is better to use latest Raven firmwares, you could use this device/common/firmware repo [3]



shahul hameed

unread,
Jun 22, 2018, 7:15:05 AM6/22/18
to Android-x86
Hi Mauro Rossi,

The following error when I try to compile both of your kernels.
 AR      firmware/built-in.a
  CC      arch/x86/pci/i386.o
  CC      arch/x86/oprofile/../../../drivers/oprofile/oprof.o
  CC      arch/x86/pci/init.o
  CC      arch/x86/kernel/SSEPlus_float_REF.o
arch/x86/kernel/SSEPlus_float_REF.c:1:0: error: -mpreferred-stack-boundary=3 is not between 4 and 12
 #include <linux/kernel.h>
 ^
make[2]: *** [arch/x86/kernel/SSEPlus_float_REF.o] Error 1
make[1]: *** [arch/x86/kernel] Error 2

Tried in Ubuntu host having kernel version 4.4 and 4.15 the error is same for both.
Do I need some additional packages for compiling kernel from your site?

Regards,
Shahul

Mauro Rossi

unread,
Jun 22, 2018, 7:28:52 AM6/22/18
to Android-x86
No errors on my side when compiling with provided android-x86*defconfig files
and using Android Build System toolchain.

Mauro

Mauro Rossi

unread,
Jun 22, 2018, 7:36:56 AM6/22/18
to Android-x86
Would you like to try kernel 4.18rc1 images, to see if problem is solved?

https://drive.google.com/drive/mobile/folders/0B_OFHiIqgpSFMlk4bkhaMnAwbDA

Those images have HWCOMP=1 enabled, if you want to try drm_gralloc you need (just in those experimental iso) to edit boot cmdline and remove 'HWCOMP=1' manually.

Please provide also feedback with hwc enabled.
Thanks
Mauro

shahul hameed

unread,
Jun 22, 2018, 7:39:24 AM6/22/18
to Android-x86
When you say Android Build System toolchain, can you elaborate what it is?
I am just using gcc4.8 which is with my Ubuntu14.04 machine.

-Shahul

Mauro Rossi

unread,
Jun 22, 2018, 9:51:23 AM6/22/18
to Android-x86


Il giorno venerdì 22 giugno 2018 13:39:24 UTC+2, shahul hameed ha scritto:
When you say Android Build System toolchain, can you elaborate what it is?

The build instructions on android-x86 website:

cd android-x86
. build/envsetup.sh
lunch android_x86_64-userdebug
make -j4 kernel

Please just check yourself if you need to enable CONFIG_DRM_AMD_DC_DCN1_0 in android-x86_64_defconfig file

If you built the kernel with linux x86_64_defconfig, the result is unpredictable.
Mauro

shahul hameed

unread,
Jun 22, 2018, 10:47:29 AM6/22/18
to Android-x86
Hi,

I think system is not mounting with this image on my board.
See attachment.
Not getting shell also.

Regards,
Shahul
IMG-5383.JPG

shahul hameed

unread,
Jun 22, 2018, 11:29:22 AM6/22/18
to Android-x86
HI Maurossi,

Able to compile it with android build system after solving couple of compilation errors in wireless drivers.
With 4.18rc1 also no shell coming up and hanging after detecting sda and sda1 as shown in the attachment.

Do I need to change some BIOS or GRUB settings or any changes in kernel config file?

CONFIG_DRM_AMD_DC_DCN1_0 this I think we need not worry at this stage as the problem is with system mounting and console getting into live.

Regards,
Shyam
IMG-5384.JPG

Mauro Rossi

unread,
Jun 22, 2018, 11:55:59 AM6/22/18
to Android-x86
On Raven APU (AMD CPU) have you tried with x86 32 bit image?
Mauro

Nebudte Zvedy

unread,
Jun 23, 2018, 12:05:18 AM6/23/18
to Android-x86
Raven Ridge is problem even on Linux 2400G is now working, 2200G dont, you need pretty new kernels..

  Oreo has only 4.9 kernel.
Reply all
Reply to author
Forward
0 new messages