Kernel: enable CONFIG_INTEL_MEI_GSC_PROXY (missing mei_gsc_proxy, i915 "GSC proxy" error on Meteor Lake/Arrow Lake)

Open Beginner friendly
  • Is something wrong?
#63,325 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
linux, shell
Domain
operating-systems

Research direction

The change belongs in the kernel package templates for linux6.18 and linux7.3 in void-packages, where the kernel config is set. Find where CONFIG_INTEL_MEI_GSC_PROXY is currently unset for each version and check the surrounding MEI options. Done means the option is enabled in both configs, the package builds, and modinfo mei_gsc_proxy finds the module on a rebuilt kernel.

Written by the indexing model from the issue text.

Description

bug needs-testing
Is this a new report?

Yes

System Info

Void 6.18.60_1 x86_64 GenuineIntel notuptodate rrrmFF

Package(s) Affected

linux6.18, linux7.3

Does a report exist for this bug with the project's home (upstream) and/or another distro?

No response

Expected behaviour

The mei_gsc_proxy module should be shipped with the kernel and be loadable (as on Fedora/Debian/Arch kernels), so that i915/xe can initialize the GSC proxy, and the boot-time error i915 ...: can't init GSC proxy due to missing mei component (older kernels: *ERROR* GT1: GSC proxy handler failed to init) no longer appears in dmesg.

Actual behaviour

Void kernels (linux6.18-6.18.60_1, linux7.3-7.3.1_1) are built without
CONFIG_INTEL_MEI_GSC_PROXY:

$ grep MEI_GSC /boot/config-$(uname -r)
# CONFIG_INTEL_MEI_GSC_PROXY is not set
$ modinfo mei_gsc_proxy
modinfo: ERROR: Module mei_gsc_proxy not found.

As a result, on systems with a Meteor Lake / Arrow Lake-H iGPU, i915 logs an
error on every boot:

i915 0000:00:02.0: [drm] GT1: can't init GSC proxy due to missing mei component

(older kernels: "ERROR GT1: GSC proxy handler failed to init")

lsmod | grep mei shows only mei and mei_me; the mei_gsc_proxy component
never binds, so the GSC firmware inside the iGPU cannot communicate with the
CSME. On DG2 this breaks HuC authentication; on MTL/ARL the practical impact
is smaller (HuC still authenticates), but the error is logged on every boot
and ME-dependent GSC features (some PXP/protected-content paths) are
unavailable.

Steps to reproduce
  1. Boot a current Void kernel (tested: linux6.18-6.18.60_1 andlinux7.3-7.3.1_1) on a system with a Meteor Lake / Arrow Lake-H iGPU.
  2. dmesg | grep -i gsc — the proxy error is present on every boot.
  3. modinfo mei_gsc_proxy → ERROR: Module mei_gsc_proxy not found.
  4. grep MEI_GSC /boot/config-$(uname -r) → # CONFIG_INTEL_MEI_GSC_PROXY is not set
Dominant language
Shell
Stars
3.5k
Forks
2.8k
Avg merge
1d 21h
Merged PRs (30d)
302

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from void-linux/void-packages

All issues in void-linux/void-packages

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.