sonic-net / sonic-net/sonic-linux-kernel
[Trixie][202511] EOPNOTSUPP Error Logged during AMD SFH HID Client Init
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 72
- Forks
- 237
- Avg merge
- 7d 19h
- Merged PRs (30d)
- 8
Description
After upgrading SONiC to use Trixie, the kernel logs the following error message on boot: ... amd_sfh_hid_client_init failed err -95
The problem lies within the AMD Sensor Fusion Hub HID driver code in the kernel, and is a result of this change: https://github.com/torvalds/linux/commit/2105e8e00da4673266e217653292fef6acefde03
The reason the above changes causes this issue is because it removes the guard against logging err -95 (-EOPNOTSUPP):
- if (rc != -EOPNOTSUPP)
- dev_err(&pdev->dev, "amd_sfh_hid_client_init failed\n");
return rc;
...
+ if (rc) {
+ amd_sfh_clear_intr(mp2);
+ dev_err(&pdev->dev, "amd_sfh_hid_client_init failed err %d\n", rc);
+ return;
+ }
This has been noticed on some Arista-7060X6 platforms, but likely affects other platforms/vendors as well.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the AMD Sensor Fusion Hub HID driver entry point amd_sfh_hid_client_init and compare the behavior introduced by upstream commit 2105e8e00da4673266e217653292fef6acefde03. Reproduce the boot logs on an affected Arista-7060X6 platform and verify that the unsupported-operation case no longer produces the erroneous EOPNOTSUPP error log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100