Skip to content
Snippets Groups Projects

GuC firmware: fetch failed with error -2

    • Closed Issue created by Thomas @uhthomas

    Hi!

    The diagnostic messages asked me to open a bug report, so here I am.

    I'm using an Intel Arc A380 GPU with Talos Linux. I've tried upgrading to Linux 6.2 to use Intel Arc and am struggling a bit to get it working correctly. It looks like the i915 firmware isn't happy to load correctly and all graphics output is suspending from the line vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none.

    These are the changes I made to try and upgrade to Linux 6.2.

    https://github.com/uhthomas/pkgs/compare/fb853ff...e0396a5

    I also found mesa/mesa#7701 (closed)

    10.0.0.104: kern:    info: [2023-04-02T18:26:23.423385158Z]: i915 0000:06:00.0: enabling device (0000 -> 0002)
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:23.493013158Z]: i915 0000:06:00.0: BAR 0: releasing [mem 0xd8000000-0xd8ffffff 64bit]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:23.582741158Z]: i915 0000:06:00.0: BAR 2: releasing [mem 0x3ffe0000000-0x3ffefffffff 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:23.683912158Z]: pcieport 0000:05:01.0: BAR 9: releasing [mem 0x3ffe0000000-0x3ffff7fffff 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:05:01.0
10.0.0.104: kern:    info: [2023-04-02T18:26:23.789237158Z]: pcieport 0000:04:00.0: BAR 9: releasing [mem 0x3ffe0000000-0x3ffff7fffff 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:04:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:23.894576158Z]: pcieport 0000:04:00.0: BAR 9: no space for [mem size 0x200000000 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:04:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:23.991567158Z]: pcieport 0000:04:00.0: BAR 9: failed to assign [mem size 0x200000000 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:04:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:24.092741158Z]: pcieport 0000:05:01.0: BAR 9: no space for [mem size 0x200000000 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:05:01.0
10.0.0.104: kern:    info: [2023-04-02T18:26:24.189736158Z]: pcieport 0000:05:01.0: BAR 9: failed to assign [mem size 0x200000000 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:05:01.0
10.0.0.104: kern:    info: [2023-04-02T18:26:24.290895158Z]: i915 0000:06:00.0: BAR 2: no space for [mem size 0x200000000 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:24.383739158Z]: i915 0000:06:00.0: BAR 2: failed to assign [mem size 0x200000000 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:24.480731158Z]: i915 0000:06:00.0: BAR 0: assigned [mem 0xd8000000-0xd8ffffff 64bit]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:24.569428158Z]: pcieport 0000:00:03.0: PCI bridge to [bus 04-07]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:00:03.0
10.0.0.104: kern:    info: [2023-04-02T18:26:24.637285158Z]: pcieport 0000:00:03.0:   bridge window [mem 0xd8000000-0xdaffffff]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:00:03.0
10.0.0.104: kern:    info: [2023-04-02T18:26:24.735017158Z]: pcieport 0000:00:03.0:   bridge window [mem 0x3ffe0000000-0x3ffffffffff 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:00:03.0
10.0.0.104: kern:    info: [2023-04-02T18:26:24.839289158Z]: pcieport 0000:04:00.0: PCI bridge to [bus 05-07]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:04:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:24.907136158Z]: pcieport 0000:04:00.0:   bridge window [mem 0xd8000000-0xdaffffff]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:04:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:24.993722158Z]: pcieport 0000:04:00.0:   bridge window [mem 0x3ffe0000000-0x3ffff7fffff 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:04:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:25.098007158Z]: pcieport 0000:05:01.0: PCI bridge to [bus 06]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:05:01.0
10.0.0.104: kern:    info: [2023-04-02T18:26:25.162725158Z]: pcieport 0000:05:01.0:   bridge window [mem 0xd8000000-0xd9ffffff]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:05:01.0
10.0.0.104: kern:    info: [2023-04-02T18:26:25.249307158Z]: pcieport 0000:05:01.0:   bridge window [mem 0x3ffe0000000-0x3ffff7fffff 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:05:01.0
10.0.0.104: kern:    info: [2023-04-02T18:26:25.353584158Z]: i915 0000:06:00.0: [drm] Failed to resize BAR2 to 8192M (-ENOSPC)
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:25.439121158Z]: i915 0000:06:00.0: BAR 2: assigned [mem 0x3ffe0000000-0x3ffefffffff 64bit pref]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:25.539265158Z]: i915 0000:06:00.0: [drm] Local memory IO size: 0x0000000010000000
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:25.624779158Z]: i915 0000:06:00.0: [drm] Local memory available: 0x000000017c800000
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:25.712410158Z]: i915 0000:06:00.0: [drm] Using a reduced BAR size of 256MiB. Consider enabling 'Resizable BAR' or similar, if available in the BIOS.
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:25.882651158Z]: i915 0000:06:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:     err: [2023-04-02T18:26:25.993677158Z]: i915 0000:06:00.0: GuC firmware i915/dg2_guc_70.bin: fetch failed with error -2
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:  notice: [2023-04-02T18:26:26.093711158Z]: i915 0000:06:00.0: Please file a bug on drm/i915; see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details.
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:26.254080158Z]: i915 0000:06:00.0: [drm] GuC firmware(s) can be downloaded from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:     err: [2023-04-02T18:26:26.527557158Z]: i915 0000:06:00.0: [drm] *ERROR* render: timed out waiting for forcewake ack to clear.
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:  notice: [2023-04-02T18:26:26.634858158Z]: i915 0000:06:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x222/0x240 [i915]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:     err: [2023-04-02T18:26:26.872087158Z]: i915 0000:06:00.0: [drm] *ERROR* gt: timed out waiting for forcewake ack to clear.
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:  notice: [2023-04-02T18:26:26.975227158Z]: i915 0000:06:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x222/0x240 [i915]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:     err: [2023-04-02T18:26:27.212462158Z]: i915 0000:06:00.0: [drm] *ERROR* vdbox0: timed out waiting for forcewake ack to clear.
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:  notice: [2023-04-02T18:26:27.319764158Z]: i915 0000:06:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x222/0x240 [i915]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:     err: [2023-04-02T18:26:27.556994158Z]: i915 0000:06:00.0: [drm] *ERROR* vdbox2: timed out waiting for forcewake ack to clear.
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:  notice: [2023-04-02T18:26:27.664292158Z]: i915 0000:06:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x222/0x240 [i915]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:     err: [2023-04-02T18:26:27.901563158Z]: i915 0000:06:00.0: [drm] *ERROR* vebox0: timed out waiting for forcewake ack to clear.
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:  notice: [2023-04-02T18:26:28.008859158Z]: i915 0000:06:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x222/0x240 [i915]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:     err: [2023-04-02T18:26:28.246092158Z]: i915 0000:06:00.0: [drm] *ERROR* vebox1: timed out waiting for forcewake ack to clear.
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:  notice: [2023-04-02T18:26:28.353396158Z]: i915 0000:06:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x222/0x240 [i915]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:28.491614158Z]: i915 0000:06:00.0: [drm] GuC firmware i915/dg2_guc_70.bin version 0.0.0
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:     err: [2023-04-02T18:26:28.583414158Z]: i915 0000:06:00.0: GuC initialization failed -2
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:     err: [2023-04-02T18:26:28.650150158Z]: i915 0000:06:00.0: Enabling uc failed (-5)
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:     err: [2023-04-02T18:26:28.711683158Z]: i915 0000:06:00.0: Failed to initialize GPU, declaring it wedged!
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern: warning: [2023-04-02T18:26:28.797679158Z]: i915 0000:06:00.0: Direct firmware load for i915/dg2_dmc_ver2_08.bin failed with error -2
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:  notice: [2023-04-02T18:26:28.908121158Z]: i915 0000:06:00.0: [drm] Failed to load DMC firmware i915/dg2_dmc_ver2_08.bin. Disabling runtime power management.
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:  notice: [2023-04-02T18:26:29.044572158Z]: i915 0000:06:00.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:  notice: [2023-04-02T18:26:29.201341158Z]: i915 0000:06:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by intel_gt_init+0xb3/0x330 [i915]
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:29.366523158Z]: [drm] Initialized i915 1.6.0 20201103 for 0000:06:00.0 on minor 0
10.0.0.104: kern:    info: [2023-04-02T18:26:29.453443158Z]: i915 0000:06:00.0: [drm] Cannot find any crtc or sizes
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
10.0.0.104: kern:    info: [2023-04-02T18:26:29.527610158Z]: i915 0000:06:00.0: [drm] Cannot find any crtc or sizes
 SUBSYSTEM=pci
 DEVICE=+pci:0000:06:00.0
    Edited
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    • Thomas changed the description

      changed the description

    • Suresh added feature: firmware/guc platform: DG2 labels

      added feature: firmware/guc platform: DG2 labels

    • Suresh
      Suresh @suresh_kurmi ·
      Reporter

      Cc : @jewins

    • John Harrison
      John Harrison @johnharr ·
      Developer

      The fetch error -2 is because the firmware file is missing from the system:

      i915 0000:06:00.0: GuC firmware i915/dg2_guc_70.bin: fetch failed with error -2
i915 0000:06:00.0: [drm] GuC firmware(s) can be downloaded from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915

      Whatever linux distro you are using should have updated packages that include the new firmware files. If you are using your own kernel build that is in advance of the distro release, then you will need to manually download the firmware files from the above repo and install in /lib/firmware/i915. Also, remember to update your initramfs file if the i915 module is being loaded at boot or statically compiled into the kernel.

      Edited by John Harrison
    • John Harrison
      John Harrison @johnharr ·
      Developer

      Note that there are further errors about the hardware not responding:

      i915 0000:06:00.0: [drm] *ERROR* vebox1: timed out waiting for forcewake ack to clear.

      These are unrelated to not finding the GuC firmware. Are you using the very latest kernel version? If not then try updating. If you are on the latest version and still hitting these errors, please file as a separate bug report.

      Edited by John Harrison
    • Septem9er mentioned in issue #8417 (closed)

      mentioned in issue #8417 (closed)

    • Daniele Ceraolo Spurio closed

      closed

    • Daniele Ceraolo Spurio
      Daniele Ceraolo Spurio @dceraolo ·
      Developer

      Closing, fetch failure believed to be not a bug and no response from reporter. Note that #8417 (closed) confirms that installing the firmware removes the GuC error and has a potential fix for the forcewake problem in the comments.

    Please register or sign in to reply