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: Mon, 23 Dec 2024 11:05:03 +0000 [thread overview]
Message-ID: <bug-219495-215701-4ieTTksyyg@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 #60 from jarkko@kernel.org ---
(In reply to andy.liang from comment #54)
> (In reply to jarkko from comment #51)
> > (In reply to jarkko from comment #31)
> > > OK, I somehow managed to miss it as it had different naming convention
> > sorry.
> > >
> > > Anywhow, I see this:
> > >
> > > [ 10.693310][ T1] tpm_tis STM0925:00: 2.0 TPM (device-id 0x3, rev-id
> > 0)
> > > [ 10.848132][ T1] ------------[ cut here ]------------
> > > [ 10.853559][ T1] WARNING: CPU: 59 PID: 1 at mm/page_alloc.c:4727
> > > __alloc_pages_noprof+0x2ca/0x330
> > > [ 10.862827][ T1] Modules linked in:
> > > [ 10.866671][ T1] CPU: 59 UID: 0 PID: 1 Comm: swapper/0 Not tainted
> > > 6.12.0-lp155.2.g52785e2-default #1 openSUSE Tumbleweed (unreleased)
> > > 588cd98293a7c9eba9013378d807364c088c9375
> > > [ 10.882741][ T1] Hardware name: HPE ProLiant DL320 Gen12/ProLiant
> > > DL320 Gen12, BIOS 1.20 10/28/2024
> > > [ 10.892170][ T1] RIP: 0010:__alloc_pages_noprof+0x2ca/0x330
> > > [ 10.898103][ T1] Code: 24 08 e9 4a fe ff ff e8 34 36 fa ff e9 88 fe
> > ff
> > > ff 83 fe 0a 0f 86 b3 fd ff ff 80 3d 01 e7 ce 01 00 75 09 c6 05 f8 e6 ce
> 01
> > > 01 <0f> 0b 45 31 ff e9 e5 fe ff ff f7 c2 00 00 08 00 75 42 89 d9 80 e1
> > > [ 10.917750][ T1] RSP: 0000:ffffb7cf40077980 EFLAGS: 00010246
> > > [ 10.923777][ T1] RAX: 0000000000000000 RBX: 0000000000040cc0 RCX:
> > > 0000000000000000
> > > [ 10.931727][ T1] RDX: 0000000000000000 RSI: 000000000000000c RDI:
> > > 0000000000040cc0
> > > [ 10.939678][ T1] RBP: 000000000000000c R08: ffffffffbb6fdc67 R09:
> > > 0000000000000000
> > > [ 10.947626][ T1] R10: ffffb7cf40077ac8 R11: 0000000000000000 R12:
> > > 0000000000000000
> > > [ 10.955560][ T1] R13: 00000000ffffffff R14: 0000000000000cc0 R15:
> > > ffff9a5c051cc000
> > > [ 10.963507][ T1] FS: 0000000000000000(0000)
> > GS:ffff9a6348780000(0000)
> > > knlGS:0000000000000000
> > > [ 10.972405][ T1] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > > [ 10.978944][ T1] CR2: 0000000000000000 CR3: 0000000184638001 CR4:
> > > 0000000000f70ef0
> > > [ 10.986891][ T1] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> > > 0000000000000000
> > > [ 10.994837][ T1] DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7:
> > > 0000000000000400
> > > [ 11.002770][ T1] PKRU: 55555554
> > > [ 11.006256][ T1] Call Trace:
> > > [ 11.009479][ T1] <TASK>
> > > [ 11.012352][ T1] ? __alloc_pages_noprof+0x2ca/0x330
> > >
> > >
> > > RSI=0x0c, which maps to the parameter 'order' in __alloc_pages_noprof(),
> > > which allocates
> > > 4096*2**0xc = 16777216 = 16 MiB of memory. This means that memory
> consumed
> > > by the log is in the range 8 MiB < N <= 16 MiB.
> >
> > I don't understand why ESI=0x0c while TPM2 table has size 0x800000, which
> > maps to the order 0x0b as 4096 * 2**0x0b = 0x800000.
> >
> > It looks like as if TPM2 table and this transcript are either from
> different
> > machines or different BIOS versions. I'm not sure how to otherwise explain
> > that difference.
> >
> > For 0x0c, the last line in that TPM2 dump screenshot should start: 00000001
> > not 00008000.
>
> Sorry about that. The machine I had in November is different from the one in
> December. I uploaded a new dmesg with Kernel 6.12.6. Thank you.
> https://bugzilla.kernel.org/attachment.cgi?id=307386
OK thanks for responding! I just needed confirmation that I'm not interpreting
the log incorrectly :-)
--
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-12-23 11:05 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
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 [this message]
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-4ieTTksyyg@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).