Linux-Renesas-SoC Archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: tty: serial: sh-sci: hrtimer not properly canceled on chan_rx invalidation?
Date: Mon, 6 May 2024 08:56:24 +0200	[thread overview]
Message-ID: <jfthbcagpmtqkxls75liajodkifp7oxufawemjf3yryracpmay@davyrdnjerk7> (raw)
In-Reply-To: <a2b7783a-d548-4a0b-ab2f-a1cd66af632e@de.bosch.com>

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

Hi Dirk,

> In the quite limited log we see "Interrupted shutdown" reported by a user
> space (!) application. Whatever that means, and whatever that means for the
> kernel. But yes, if you think shutdown/reboot is a reasonable path to look
> at, I won't exclude that ;)

Well, if the kernel runs into a NULL-pointer exception during shutdown,
you can surely call that "interrupted". What a brave userspace
application still being able to report that! Maybe there is a bare-metal
watchdog app running on one of the minor cores?

Happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-05-06  6:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240502174257.gfmk7al3qkv7jiyj () ninjato>
2024-05-06  5:27 ` tty: serial: sh-sci: hrtimer not properly canceled on chan_rx invalidation? Dirk Behme
2024-05-06  6:56   ` Wolfram Sang [this message]
2024-04-11 12:41 Dirk Behme
2024-04-11 12:54 ` Biju Das
2024-04-12  6:36 ` Wolfram Sang
2024-04-12  7:50   ` Biju Das
2024-04-16 11:49 ` Wolfram Sang
2024-04-24  9:57   ` Geert Uytterhoeven
2024-04-24 12:12     ` Wolfram Sang
2024-05-02 17:42 ` Wolfram Sang

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=jfthbcagpmtqkxls75liajodkifp7oxufawemjf3yryracpmay@davyrdnjerk7 \
    --to=wsa+renesas@sang-engineering.com \
    --cc=dirk.behme@de.bosch.com \
    --cc=linux-renesas-soc@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 read-only IMAP folder(s) and NNTP newsgroup(s).