Bug 106423 - guc_fw_xfer error with i915.enable_guc=2 kernel mode parameter
Summary: guc_fw_xfer error with i915.enable_guc=2 kernel mode parameter
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged, ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-06 18:17 UTC by ryanboehning
Modified: 2018-05-17 10:02 UTC (History)
1 user (show)

See Also:
i915 platform: CFL
i915 features: firmware/guc


Attachments
full dmesg logs (116.69 KB, text/plain)
2018-05-06 18:17 UTC, ryanboehning
no flags Details
just the drm logs (19.78 KB, text/plain)
2018-05-06 18:19 UTC, ryanboehning
no flags Details

Description ryanboehning 2018-05-06 18:17:23 UTC
Created attachment 139398 [details]
full dmesg logs

CPU: Coffee Lake 8700K
Mobo: ASUS Z370-G STRIX
Distro: Arch
Kernel: 4.16.6-1-ARCH

The GuC firmware loads fine when I use the i915.enable_guc=1 kernel mode setting, but when I try to enable HuC loading with i915.enable_guc=2 I get a guc_fw_xfer error during boot. My system boots but my display output is blank.

Here's the relevant excerpt from the boot logs (full dmesg log attached).

kernel: [drm:intel_uc_fw_upload [i915]] HuC fw load i915/kbl_huc_ver02_00_1810.bin
kernel: [drm:intel_uc_fw_upload [i915]] HuC fw load PENDING
kernel: [drm:huc_ucode_xfer [i915]] HuC DMA transfer wait over with ret 0
kernel: [drm:intel_uc_fw_upload [i915]] HuC fw load SUCCESS
kernel: [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0)
kernel: [drm:intel_uc_fw_upload [i915]] GuC fw load i915/kbl_guc_ver9_39.bin
kernel: [drm:intel_uc_fw_upload [i915]] GuC fw load PENDING
kernel: [drm:guc_fw_xfer [i915]] GuC DMA status 0x10
kernel: [drm:guc_fw_xfer [i915]] GuC status 0x800470ec
kernel: [drm:guc_fw_xfer [i915]] *ERROR* GuC firmware xfer error -110
kernel: [drm:intel_uc_fw_upload [i915]] GuC fw load FAIL
kernel: [drm] GuC: Failed to load firmware i915/kbl_guc_ver9_39.bin (error -110)
kernel: i915 0000:00:02.0: GuC initialization failed -110
kernel: [drm:guc_fw_xfer [i915]] *ERROR* GuC firmware xfer error -110
kernel: [drm:intel_uc_fw_upload [i915]] GuC fw load FAIL
kernel: [drm] GuC: Failed to load firmware i915/kbl_guc_ver9_39.bin (error -110)
kernel: i915 0000:00:02.0: GuC initialization failed -110
kernel: [drm:drm_irq_uninstall [drm]] irq=123
kernel: [drm:intel_power_well_enable [i915]] enabling DDI A/E IO power well
kernel: [drm:intel_power_well_enable [i915]] enabling DDI C IO power well
kernel: [drm:intel_power_well_enable [i915]] enabling DDI D IO power well
kernel: i915 0000:00:02.0: [drm:i915_driver_load [i915]] Device initialization failed (-110)
kernel: i915 0000:00:02.0: Please file a bug at https://bugs.freedesktop.org/enter_bug.cgi?product=DRI against DRM/Intel providing the dmesg log by booting with drm.debug=0xf
kernel: i915: probe of 0000:00:02.0 failed with error -110

I'm using the latest Arch package for linux-firmware (linux-firmware 20180416.b562d2f-1) and the latest Arch kernel.

This is my first bug report so sorry if it's not right.
Comment 1 ryanboehning 2018-05-06 18:19:04 UTC
Created attachment 139399 [details]
just the drm logs
Comment 2 Chris Wilson 2018-05-06 18:25:04 UTC
(In reply to ryanboehning from comment #0)
> kernel: i915 0000:00:02.0: [drm:i915_driver_load [i915]] Device
> initialization failed (-110)
> kernel: i915 0000:00:02.0: Please file a bug at
> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI against DRM/Intel
> providing the dmesg log by booting with drm.debug=0xf

We shouldn't request a bug report if you set unsafe parameters.
Comment 3 ryanboehning 2018-05-06 18:26:37 UTC
How else are you supposed to enable the HuC and GuC?
Comment 4 Chris Wilson 2018-05-06 18:48:03 UTC
Likely dupe of #105653
Comment 5 Jani Saarinen 2018-05-07 07:18:36 UTC
Reported, agree duplicate?
Comment 6 Jani Saarinen 2018-05-08 06:50:33 UTC
Reporter, do you agree this as duplicate?
Comment 7 ryanboehning 2018-05-08 14:03:03 UTC
I'm not sure. There's two dmesg logs with "*ERROR* GuC firmware xfer error -110" in #105653. Aside from that line, the dmesg logs are quite different. It might be the same underlying bug, or it might be two (or three) bugs in the same piece of firmware. If you want to close this as a dup, I'm fine with that as long as my logs are copied to the #105653.
Comment 8 Jani Saarinen 2018-05-17 10:02:54 UTC
Guc not really supported upstream, yet, closing.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.