Revision 0x00000122 for 06-b7-01 (i9-14900HX) breaks initialisation of mei_me
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- linux
- Domain
- operating-systems
Research direction
No repository files or tests are named. Start by comparing boot behavior for microcode revisions 0x11f and 0x122 on 06-b7-01/i9-14900HX, including the dis_ucode_ldr case, and investigate the mei_me initialization messages. Done means determining whether revision 0x122 causes the regression and documenting a confirmed resolution.
Written by the indexing model from the issue text.
Description
Dear all,
I'm seeing a difference before and after updating the microcode for 06-b7-01. I don't quite know what it means, but I do see a multi-second stall on boot when the MEI initialisation fails. This happens even on the same kernel with and without the dis_ucode_ldr kernel option.
Old behaviour:
[ 0.674435] microcode: Current revision: 0x0000011f
[ 4.934601] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
New behaviour:
[ 0.712298] microcode: Current revision: 0x00000122
[ 0.712375] microcode: Updated early from: 0x0000011f
[ 0.915088] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
[ 0.915704] mei_me 0000:00:14.0: H_RST is not set = 0x1A000840
[ 2.943674] mei_me 0000:00:14.0: wait hw ready failed
[ 2.943822] mei_me 0000:00:14.0: hw_start failed ret = -62 fw status = 803401FD 00000000 00006032 00000000 00000000 00000000
[ 2.944064] mei_me 0000:00:14.0: H_RST is not set = 0x1A000840
[ 4.959607] mei_me 0000:00:14.0: wait hw ready failed
[ 4.959746] mei_me 0000:00:14.0: hw_start failed ret = -62 fw status = 803401FD 00000000 00006032 00000000 00000000 00000000
[ 4.959988] mei_me 0000:00:14.0: H_RST is not set = 0x1A000840
[ 6.975616] mei_me 0000:00:14.0: wait hw ready failed
[ 6.975769] mei_me 0000:00:14.0: hw_start failed ret = -62 fw status = 803401FD 00000000 00006032 00000000 00000000 00000000
[ 6.981211] mei_me 0000:00:14.0: reset: reached maximal consecutive resets: disabling the device
[ 6.986604] mei_me 0000:00:14.0: reset failed ret = -19
[ 6.991920] mei_me 0000:00:14.0: link layer initialization failed.
[ 6.997228] mei_me 0000:00:14.0: init hw failure.
[ 7.002843] mei_me 0000:00:14.0: initialization failed.
- Dominant language
- No language data
- Stars
- 828
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from intel/Intel-Linux-Processor-Microcode-Data-Files
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
intel/Intel-Linux-Processor-Microcode-Data-Files#112 · 36 comments · 22 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
intel/Intel-Linux-Processor-Microcode-Data-Files#109 · 6 comments · 2 reactions ·
-
Microcode not foundOpen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
intel/Intel-Linux-Processor-Microcode-Data-Files#108 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
intel/Intel-Linux-Processor-Microcode-Data-Files#107 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
intel/Intel-Linux-Processor-Microcode-Data-Files#106 · 1 comment · 1 reaction ·
All issues in intel/Intel-Linux-Processor-Microcode-Data-Files
Similar issues
-
area-System.IO bug untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/runtime#136599 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
OS-Simulator-Organization/os-simulator-project#63 ·
Maintainers usually reply within 1 day
-
Windows CLI: get_ps_title() passes bytes to GetConsoleTitleW() instead of characters, overflowing the 260-wchar_t bufferPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ophub/amlogic-s9xxx-armbian#3752 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day