Intel Skylake GuC Submission won't enable
Reported by
nshuyid...@gmail.com,
Feb 26 2018
|
|
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 Steps to reproduce the problem: 1. Add i915.enable_guc_submission=1 and i915.enable_guc_loading=1 to boot argument 2. 3. What is the expected behavior? GuC enabled with submission What went wrong? GuC is not enabled and there were no error logged (with drm.debug=0x2). cat /sys/kernel/debug/dri/0/i915_guc_load_status GuC firmware status: path: i915/skl_guc_ver6.bin fetch: SUCCESS load: FAIL version wanted: 6.1 version found: 6.1 header: offset is 0; size = 128 uCode: offset is 128; size = 128640 RSA: offset is 128768; size = 256 GuC status 0x800071ec: Bootrom status = 0x76 uKernel status = 0x71 MIA Core status = 0x0 Scratch registers: 0: 0x0 1: 0x90040 2: 0x0 3: 0x5f5e100 4: 0x600 5: 0x0 6: 0x0 7: 0x8 8: 0x3 9: 0x6aa00 10: 0x0 11: 0x0 12: 0x0 13: 0x0 14: 0x0 15: 0x0 Did this work before? No Chrome version: Channel: n/a OS Version: 4.4 Flash Version: I am not sure if this is skylake specific. Loading GuC submission work with chromeos-4.14 and upstream 4.4. GuC will load with i915.enable_guc_submission=0 and i915.enable_guc_loading=1 (submission disabled). log: [ 0.825875] [drm:intel_guc_setup] GuC fw status: fetch SUCCESS, load PENDING [ 0.928350] [drm:guc_ucode_xfer_dma] DMA status 0x10, GuC status 0x800071ec [ 0.928354] [drm:guc_ucode_xfer_dma] returning -110 [ 0.928356] [drm] GuC fw load failed: -110; will reset and retry 2 more time(s) [ 1.030686] [drm:guc_ucode_xfer_dma] DMA status 0x10, GuC status 0x800071ec [ 1.030690] [drm:guc_ucode_xfer_dma] returning -110 [ 1.030692] [drm] GuC fw load failed: -110; will reset and retry 1 more time(s) [ 1.133081] [drm:guc_ucode_xfer_dma] DMA status 0x10, GuC status 0x800071ec [ 1.133085] [drm:guc_ucode_xfer_dma] returning -110 [ 1.133113] [drm] GuC firmware load failed: -110 [ 1.133114] [drm] Falling back to execlist mode
,
Mar 5 2018
I found the cause: 89784ca UPSTREAM: drm/i915/execlists: Request the kernel context be pinned high Removing if (i915_gem_context_is_kernel(ctx)) flags |= PIN_HIGH; from execlists_context_pin will fix the issue. But I don't know how this works. After GuC submission loads, there is this issue: https://bugs.freedesktop.org/show_bug.cgi?id=98571 which is fixed. |
|
►
Sign in to add a comment |
|
Comment 1 by dtapu...@chromium.org
, Feb 26 2018