All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Goldman <kgoldman at us.ibm.com>
To: tpm2@lists.01.org
Subject: [tpm2] Re: abrmd crashing - how to debug?
Date: Thu, 11 Mar 2021 12:05:49 -0500	[thread overview]
Message-ID: <OFCDB9C1B3.108EDCC9-ON00258695.005D4705-85258695.005DEAEA@notes.na.collabserv.com> (raw)
In-Reply-To: SN6PR11MB34370249B77688306C648A67B8929@SN6PR11MB3437.namprd11.prod.outlook.com

[-- Attachment #1: Type: text/plain, Size: 5285 bytes --]

> From: "Roberts, William C" <william.c.roberts(a)intel.com>
>
> Since you're just running it as a process from a shell and not a
> system service, all the logs will be to stderr/stdout.
> Can you enable env variable G_MESSAGES_DEBUG=all when you run tpm2-
> abrmd and send us the output?


With that set, it runs about 5x longer, 554 loops.  I also noticed that it
fails
less often if I put a sleep between commands.  I'd like to run
a command that takes a long time to respond, like create, but
I don't know how.

Here is the end of the trace:

** (tpm2-abrmd:32533): DEBUG: 12:01:25.297: flushsave_context for 0 entries
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297: response_sink_process_response:
writing 0x3e bytes
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297: tpm2_command_finalize
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297:     80 01 00 00 00 3e 00 00 00
00 00 00 00 14 00 00
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297: message_queue_dequeue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297:     00 01 00 0b 03 01 00 00 00
00 00 01 00 20 00 00
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297:     00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297:     00 00 00 00 00 00 00 00 00
00 00 00 00 00
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297: write_all: writing 62 bytes to
ostream
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297: write_all: wrote 62 bytes to
ostream
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297: returning 62
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297: tpm2_response_finalize
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297: response_sink_thread: blocking
on input queue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.297: message_queue_dequeue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: command_source_on_input_ready
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: read_data: reading 10 bytes
from istream
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: read produced EOF
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: read_tpm_buffer_alloc: err_out
freeing buffer
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: command_source_on_input_ready:
removing connection from connection_manager
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: connection_manager_remove:
removing Connection
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: sink_enqueue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: resource_manager_enqueue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: message_queue_enqueue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: on_name_lost:
com.intel.tss2.Tabrmd
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: command_source_on_input_ready:
removing GCancellable
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298: resource_manager_thread:
message_queue_dequeue got obj
** INFO: 12:01:25.298: main_loop_quit
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298:
resource_manager_process_control
** (tpm2-abrmd:32533): DEBUG: 12:01:25.298:
resource_manager_process_control: received CONNECTION_REMOVED message for
connection
** INFO: 12:01:25.298: g_main_loop_run done, cleaning up
** INFO: 12:01:25.298: resource_manager_remove_connection: flushing session
contexts
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: gmain_data_cleanup
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299:
resource_manager_remove_connection: done
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: sink_enqueue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: response_sink_enqueue:
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: command_attrs_finalize
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: message_queue_enqueue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: resource_manager_unblock:
enqueuing ControlMessage
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: message_queue_dequeue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: response_sink_process_control
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: message_queue_enqueue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: response_sink_process_control:
Received CONNECTION_REMOVED message, nothing to do.
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: resource_manager_thread:
message_queue_dequeue got obj
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: handle_map_finalize
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299:
resource_manager_process_control
** (tpm2-abrmd:32533): DEBUG: 12:01:25.299: response_sink_thread: blocking
on input queue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.300: sink_enqueue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.300: message_queue_dequeue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.300: response_sink_enqueue:
** (tpm2-abrmd:32533): DEBUG: 12:01:25.300: message_queue_enqueue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.300: response_sink_process_control
** (tpm2-abrmd:32533): DEBUG: 12:01:25.300: resource_manager_dispose
** (tpm2-abrmd:32533): DEBUG: 12:01:25.300: response_sink_process_control:
Received CHECK_CANCEL control code, terminating.
** (tpm2-abrmd:32533): DEBUG: 12:01:25.300: session_list_dispose:
SessionList with 0 entries
** (tpm2-abrmd:32533): DEBUG: 12:01:25.301: session_list_finalize:
SessionList with 0 entries
** (tpm2-abrmd:32533): DEBUG: 12:01:25.301: message_queue_enqueue
** (tpm2-abrmd:32533): DEBUG: 12:01:25.301: ipc_frontend_disconnect
** (tpm2-abrmd:32533): DEBUG: 12:01:25.301: random_finalize
** INFO: 12:01:25.301: main_loop_quit

and then a command prompt.

[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 7600 bytes --]

             reply	other threads:[~2021-03-11 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 17:05 Kenneth Goldman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-15 11:58 [tpm2] Re: abrmd crashing - how to debug? ericc6727
2022-04-13 10:35 jasonadamses
2021-03-09 22:45 Roberts, William C
2021-03-09 20:16 Kenneth Goldman
2021-03-09 19:50 Tadeusz Struk

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=OFCDB9C1B3.108EDCC9-ON00258695.005D4705-85258695.005DEAEA@notes.na.collabserv.com \
    --to=tpm2@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.