All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@linux.ibm.com>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, linux-next@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, netdev@vger.kernel.org
Subject: Re: [powerpc] Fingerprint systemd service fails to start (next-20220624)
Date: Tue, 28 Jun 2022 12:41:35 +0530	[thread overview]
Message-ID: <FAA64E21-B3FE-442A-BA6B-D865006CBE3E@linux.ibm.com> (raw)
In-Reply-To: <20220627163640.74890-1-kuniyu@amazon.com>

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


>> I have attached dmesg log for reference. Let me know if any additional
>> Information is required.
> 
> * Could you provide
> * dmesg and /var/log/messages on a successful case? (without the commit)
> * Unit file
> * repro steps

I have attached the relevant log files. The attached tarball contains
dmesg, /var/log/messages and strace o/p for fprintd service collected
for working case and failure case.

> * Is it reproducible after login? (e.g. systemctl restart)
> * If so, please provide
> * the result of strace -t -ff
> 
Yes, the problem can be recreated after login. I have collected the strace
logs.

> * Does it happen on only powerpc? How about x86 or arm64?
> 
I have attempted this only on powerpc. Don’t have access to arm or x86
setup to attempt it.

Thank you for quick response.

- Sachin


[-- Attachment #2: fprintd-issue.tar --]
[-- Type: application/x-tar, Size: 403905 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Sachin Sant <sachinp@linux.ibm.com>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, davem@davemloft.net
Subject: Re: [powerpc] Fingerprint systemd service fails to start (next-20220624)
Date: Tue, 28 Jun 2022 12:41:35 +0530	[thread overview]
Message-ID: <FAA64E21-B3FE-442A-BA6B-D865006CBE3E@linux.ibm.com> (raw)
In-Reply-To: <20220627163640.74890-1-kuniyu@amazon.com>

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


>> I have attached dmesg log for reference. Let me know if any additional
>> Information is required.
> 
> * Could you provide
> * dmesg and /var/log/messages on a successful case? (without the commit)
> * Unit file
> * repro steps

I have attached the relevant log files. The attached tarball contains
dmesg, /var/log/messages and strace o/p for fprintd service collected
for working case and failure case.

> * Is it reproducible after login? (e.g. systemctl restart)
> * If so, please provide
> * the result of strace -t -ff
> 
Yes, the problem can be recreated after login. I have collected the strace
logs.

> * Does it happen on only powerpc? How about x86 or arm64?
> 
I have attempted this only on powerpc. Don’t have access to arm or x86
setup to attempt it.

Thank you for quick response.

- Sachin


[-- Attachment #2: fprintd-issue.tar --]
[-- Type: application/x-tar, Size: 403905 bytes --]

  reply	other threads:[~2022-06-28  7:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  4:58 [powerpc] Fingerprint systemd service fails to start (next-20220624) Sachin Sant
2022-06-27  4:58 ` Sachin Sant
2022-06-27 16:36 ` Kuniyuki Iwashima
2022-06-27 16:36   ` Kuniyuki Iwashima
2022-06-28  7:11   ` Sachin Sant [this message]
2022-06-28  7:11     ` Sachin Sant
2022-06-29 17:47     ` Kuniyuki Iwashima
2022-06-29 17:47       ` Kuniyuki Iwashima
2022-06-30 10:37       ` Sachin Sant
2022-06-30 10:37         ` Sachin Sant
2022-06-30 16:51         ` Kuniyuki Iwashima
2022-06-30 16:51           ` Kuniyuki Iwashima

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=FAA64E21-B3FE-442A-BA6B-D865006CBE3E@linux.ibm.com \
    --to=sachinp@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=kuniyu@amazon.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=netdev@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 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.