All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dipen Patel <dipenp@nvidia.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: <linux-rt-users@vger.kernel.org>
Subject: Re: sync system call failure
Date: Mon, 22 Feb 2021 16:02:29 -0800	[thread overview]
Message-ID: <bb5de1c8-c94a-60b6-9773-f342228f6f9e@nvidia.com> (raw)
In-Reply-To: <20210222134115.pjeiszuskg5kk23n@linutronix.de>



On 2/22/21 5:41 AM, Sebastian Andrzej Siewior wrote:
> On 2021-02-21 17:46:25 [-0800], Dipen Patel wrote:
>> Hi,
> Hi,
> 
>> I encountered below crash during the sync system call possibly coming
>> from the stress threads spawned because of the --io options which does
> …
> 
>> Platform:
>> Nvidia Jetson AGX XAVIER, with 32GB eMMC 5.1 and 256 bit 32GB LPDDR4 RAM.
>>
>> Kernel:
>> 4.9.201-rt134
> …
>> Call stack:
>>
>> [ 1813.814464] INFO: task stress blocked for more than 120 seconds.
>> [ 1813.814610]       Not tainted 4.9.201-rt134 #2
> 
> This is not a crash. It is simply an information that a task was blocked
> for quite some time (as it says).
Correct, its not a crash but fact that I have hung task panic enabled, it
reboots the system where it is not the case for the non-rt kernel with same
version, so I am guessing there has to be something in RT that contributed
to this.

> The important information would be:
> - does it recover
Yes, I have to disable hung_task_panic otherwise it will restart the system. The system is responsive so I am assuming there is no deadlock.

>   - does the time in seconds always increase or does it also drop
It varies.

>   - does the message disappear if stress terminates.
Yes
> 
> - does it occur on v5.11-RT.
I have not tried, I do not have other RT kernel versions besides 4.9.xxx.
> 
> Sebastian
> 

      reply	other threads:[~2021-02-23  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  1:46 sync system call failure Dipen Patel
2021-02-22 13:41 ` Sebastian Andrzej Siewior
2021-02-23  0:02   ` Dipen Patel [this message]

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=bb5de1c8-c94a-60b6-9773-f342228f6f9e@nvidia.com \
    --to=dipenp@nvidia.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@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.