FS#79366 - [linux] tpm_crb fails to initialise

Attached to Project: Arch Linux
Opened by Severen Redwood (severen) - Sunday, 13 August 2023, 07:24 GMT
Last edited by Toolybird (Toolybird) - Saturday, 19 August 2023, 21:51 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Levente Polyak (anthraxx)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

Starting with kernel version 6.4.9, the tpm_crb module fails to initialise on my machine, which unfortunately causes my LUKS drives to not unlock. It previously worked without issue on earlier kernel versions. The kernel error message is 'tpm_crb: probe of msft0101:00 failed with error 378'.

Note that I am using the linux-zen package over linux, but I would be surprised if the patches applied for the zen kernels would cause this issue. For that reason and because it is a bit of a pain, I have not tried the vanilla kernel at version 6.4.9 or 6.4.10, although if it would be considered helpful I could.

Additional info:
* Package versions: linux-zen-6.4.9.zen1-1, linux-zen-6.4.10.zen1-1, and linux-zen-6.4.10.zen2-1
* Motherboard: MSI Pro B660M-A

Steps to reproduce:

The issue is likely contingent on your hardware, but provided you have the same or similar hardware, boot with kernel version 6.4.9 or greater and observe that the tpm_crb module fails to initialise.
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 19 August 2023, 21:51 GMT
Reason for closing:  Fixed
Additional comments about closing:  linux 6.4.11.arch2-1
linux-zen 6.4.11.zen2-1
Comment by Toolybird (Toolybird) - Sunday, 13 August 2023, 08:07 GMT
> I have not tried the vanilla kernel

Why not? It's a *must* if you're troubleshooting. Especially when looking at the recent commits to linux-zen...

Either way, it sounds like an upstream kernel regression. General advice for debugging kernel regressions [1]. git bisect is the way. Identifying the offending commit is highly desirable if you have to report it upstream. Please let us know what you find out.

[1] https://wiki.archlinux.org/title/Kernel#Debugging_regressions
Comment by Toolybird (Toolybird) - Friday, 18 August 2023, 23:47 GMT
Dupe  FS#79411  (vanilla kernel - same error)
Comment by Toolybird (Toolybird) - Saturday, 19 August 2023, 01:05 GMT Comment by Yutsing Kuh (Sffred) - Saturday, 19 August 2023, 06:13 GMT
I have exactly the same issue with linux-6.4.11 and linux-6.4.10 works without problem.
Comment by Toolybird (Toolybird) - Saturday, 19 August 2023, 06:42 GMT Comment by loqs (loqs) - Saturday, 19 August 2023, 12:36 GMT Comment by Ronan Pigott (Brocellous) - Saturday, 19 August 2023, 19:12 GMT
I posted already in [1], but just stopping by to say that I applied Mario's patch to 6.4.11-arch1-1 and it fixed my issue.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=217804#c41
Comment by Ronan Pigott (Brocellous) - Saturday, 19 August 2023, 19:14 GMT
Just saw the edit:

Tried linux-6.4.11-arch2-1 from core-testing and it also works.

Loading...