2024-04-29, 06:40 PM
Yes my thinking as well, not PS.
I will try to reseat. I did notice a difference between you kernlog and mine. On the last successful boot I see these lines:
So it says it cannot connect, it resets, unexpected reset, resets again then it is successful. In this state it works fully but in your log you just get the successful line at the end once of the sequence.
I have always seen this behavior, it always errors twice then connects successfully on the 3rd try so I was thinking some sort of timing issue.
Have you ever seen this before or did yours always connect successfully the first time?
I will try to reseat. I did notice a difference between you kernlog and mine. On the last successful boot I see these lines:
Code:
[ 4.918698] mei i915.mei-gscfi.768-e2c2afa2-3817-4d19-9d95-06b16b588a5d: cannot connect
[ 4.921583] mei_gsc i915.mei-gscfi.768: FW not ready: resetting: dev_state = 2 pxp = 0
[ 4.921604] mei_gsc i915.mei-gscfi.768: unexpected reset: dev_state = ENABLED fw status = 00000345 84670000 00000000 00000000 E0020002 00000000
[ 4.922336] mei_gsc i915.mei-gsc.768: FW not ready: resetting: dev_state = 2 pxp = 2
[ 4.922357] mei_gsc i915.mei-gsc.768: unexpected reset: dev_state = ENABLED fw status = 00000345 84670000 00000000 00000000 E0020002 00000000
[ 4.964479] snd_hda_intel 0000:04:00.0: bound 0000:03:00.0 (ops i915_audio_component_bind_ops [i915])
[ 5.321272] i915 0000:03:00.0: [drm] GT0: HuC: authenticated for all workloads
[ 5.321288] mei_pxp i915.mei-gsc.768-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:03:00.0 (ops i915_pxp_tee_component_ops [i915])So it says it cannot connect, it resets, unexpected reset, resets again then it is successful. In this state it works fully but in your log you just get the successful line at the end once of the sequence.
I have always seen this behavior, it always errors twice then connects successfully on the 3rd try so I was thinking some sort of timing issue.
Have you ever seen this before or did yours always connect successfully the first time?