From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 219495] [TPM2] tpm_tis driver crashs during the boot time.
Date: Wed, 13 Nov 2024 18:07:55 +0000 [thread overview]
Message-ID: <bug-219495-215701-hn5UMTf3cb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219495-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219495
--- Comment #8 from jarkko@kernel.org ---
(In reply to Stefan Berger from comment #7)
> The attached parsed contents (comment 1 attachment) of
> /sys/kernel/security/tpm0/binary_bios_measurements are 476kb. I cannot say
> how much this file would be in its binary version but I would think it would
> only be like 10% of it, so like 45kb since the parsed contents also display
> whole certificate chains. I don't see why 45kb should be an issue.
>
> Can you attach the plain binary file?
>
> > When the TPM2 ACPI table sets the Minimum Log Length size more then 4MB, a
> > call trace occurs during the boot time. The reason is the kmalloc limits
> the
> > maximum size to 4MB for x86 arch.
>
> 4MB would be excessive and I think would hint at a buggy BIOS. We should
> never allocate that much memory for the BIOS log.
Yeah, possibly! I'll look at the data collected so far with time as soon as I
get answer to my question-triplet :-) Just don't want to play assumptions,
that's all.
So here the interesting part is still that apparently it could be still parsed
(see my question #2).
Thanks for taking a note on this bug!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-11-13 18:07 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 2:42 [Bug 219495] New: [TPM2] tpm_tis driver crashs during the boot time bugzilla-daemon
2024-11-13 5:50 ` [Bug 219495] " bugzilla-daemon
2024-11-13 6:50 ` bugzilla-daemon
2024-11-13 7:05 ` bugzilla-daemon
2024-11-13 7:06 ` bugzilla-daemon
2024-11-13 12:43 ` bugzilla-daemon
2024-11-13 12:47 ` bugzilla-daemon
2024-11-13 13:05 ` bugzilla-daemon
2024-11-13 18:07 ` bugzilla-daemon [this message]
2024-11-14 4:48 ` bugzilla-daemon
2024-11-14 4:48 ` bugzilla-daemon
2024-11-18 14:33 ` bugzilla-daemon
2024-11-18 18:57 ` bugzilla-daemon
2024-11-20 7:38 ` bugzilla-daemon
2024-11-20 9:15 ` bugzilla-daemon
2024-12-02 13:48 ` bugzilla-daemon
2024-12-03 6:22 ` bugzilla-daemon
2024-12-03 6:23 ` bugzilla-daemon
2024-12-09 12:56 ` bugzilla-daemon
2024-12-09 14:10 ` bugzilla-daemon
2024-12-11 9:07 ` bugzilla-daemon
2024-12-12 11:38 ` bugzilla-daemon
2024-12-12 11:39 ` bugzilla-daemon
2024-12-12 13:22 ` bugzilla-daemon
2024-12-13 6:22 ` bugzilla-daemon
2024-12-13 6:31 ` bugzilla-daemon
2024-12-13 6:31 ` bugzilla-daemon
2024-12-14 3:28 ` bugzilla-daemon
2024-12-20 1:42 ` bugzilla-daemon
2024-12-20 1:45 ` bugzilla-daemon
2024-12-20 4:09 ` bugzilla-daemon
2024-12-20 14:06 ` bugzilla-daemon
2024-12-20 14:35 ` bugzilla-daemon
2024-12-20 17:50 ` bugzilla-daemon
2024-12-20 18:30 ` bugzilla-daemon
2024-12-20 18:46 ` bugzilla-daemon
2024-12-20 19:14 ` bugzilla-daemon
2024-12-20 19:16 ` bugzilla-daemon
2024-12-20 19:17 ` bugzilla-daemon
2024-12-20 20:16 ` bugzilla-daemon
2024-12-20 20:33 ` bugzilla-daemon
2024-12-20 20:34 ` bugzilla-daemon
2024-12-20 22:48 ` bugzilla-daemon
2024-12-21 0:21 ` bugzilla-daemon
2024-12-21 11:35 ` bugzilla-daemon
2024-12-21 12:46 ` bugzilla-daemon
2024-12-21 14:11 ` bugzilla-daemon
2024-12-21 14:12 ` bugzilla-daemon
2024-12-22 8:34 ` bugzilla-daemon
2024-12-22 15:27 ` bugzilla-daemon
2024-12-22 22:41 ` bugzilla-daemon
2024-12-22 22:55 ` bugzilla-daemon
2024-12-23 7:31 ` bugzilla-daemon
2024-12-23 8:38 ` bugzilla-daemon
2024-12-23 8:40 ` bugzilla-daemon
2024-12-23 8:42 ` bugzilla-daemon
2024-12-23 8:43 ` bugzilla-daemon
2024-12-23 8:43 ` bugzilla-daemon
2024-12-23 8:43 ` bugzilla-daemon
2024-12-23 8:44 ` bugzilla-daemon
2024-12-23 11:05 ` bugzilla-daemon
2024-12-23 11:07 ` bugzilla-daemon
2024-12-23 18:32 ` bugzilla-daemon
2024-12-23 18:34 ` bugzilla-daemon
2024-12-23 18:34 ` bugzilla-daemon
2024-12-24 1:43 ` bugzilla-daemon
2025-01-16 10:53 ` bugzilla-daemon
2025-01-16 11:15 ` bugzilla-daemon
2025-01-16 13:06 ` bugzilla-daemon
2025-01-17 4:14 ` bugzilla-daemon
2025-01-17 4:15 ` bugzilla-daemon
2025-01-17 4:19 ` bugzilla-daemon
2025-01-17 10:02 ` bugzilla-daemon
2025-01-20 4:24 ` bugzilla-daemon
2025-01-20 4:27 ` bugzilla-daemon
2025-01-20 4:29 ` bugzilla-daemon
2025-01-23 14:28 ` bugzilla-daemon
2025-12-22 7:24 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-219495-215701-hn5UMTf3cb@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).