https://bugzilla.kernel.org/show_bug.cgi?id=219495 --- Comment #5 from jarkko@xxxxxxxxxx --- (In reply to Takashi Iwai from comment #2) > (In reply to jarkko from comment #1) > > (In reply to andy.liang from comment #0) > > > Created attachment 307212 [details] > > > binary_bios_measurements 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. > > > > I'm a bit lost why we need that attachment anyway. I don't have any use for > > it but maybe someone else asked for it. Can you remind me on that? > > https://lore.kernel.org/262eff2e-90c5-45db-81d7-30b1cc217ef4@xxxxxxxxxxxxx Thanks for the attachments I'll check them up later. So, I'd expected binary_bios_measurements not to exist as the allocation files but overlooked the fact that it is still useful to check what kind of data it has :-) So you got this via applying your workaround? It is useful because it looks like somewhat legit data and not corrupted. You parsed it with tpm2_eventlog? Did it complain any errors? Can you attach it as binary complete unparsed? And dmesg is with or without the workaround? Just checking (have not opened it yet). Also apparently the attachment is parsed. What is the size of that file? -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
