From: John Ogness <john.ogness@linutronix.de>
To: lkp@lists.01.org
Subject: Re: [printk] b031a684bf: INFO:rcu_tasks_detected_stalls_on_tasks
Date: Thu, 28 Jan 2021 00:35:06 +0106 [thread overview]
Message-ID: <878s8eari5.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <87bldaaxcc.fsf@jogness.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]
On 2021-01-27, John Ogness <john.ogness@linutronix.de> wrote:
> I was finally able to trigger this by using my workstation
Well, I don't know how reliably I can trigger this. I think my time will
be better spent getting lkp to trigger, since that shows to be reliable.
It took me an hour to trigger this one and I have the feeling I got
lucky with it.
[ 1854.183816] INFO: rcu_tasks detected stalls on tasks:
[ 1854.184502] 0000000036ce200f: .. nvcsw: 0/0 holdout: 1 idle_cpu: -1/1
[ 1854.185234] task:dd state:R running task stack: 0 pid:19891 ppid: 668 flags:0x00000000
[ 1854.185273] Call Trace:
[ 1854.185275] __schedule+0xfa9/0x1056
[ 1854.185283] ? firmware_map_remove+0x172/0x172
[ 1854.185300] ? ksys_write+0x147/0x180
[ 1854.185304] schedule+0x170/0x1e3
[ 1854.185307] exit_to_user_mode_prepare+0x27/0xac
[ 1854.185312] syscall_exit_to_user_mode+0x41/0x4f
[ 1854.185316] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 1854.185321] RIP: 0033:0x7f99bf52fc00
[ 1854.185324] RSP: 002b:00007ffd75722bf8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
[ 1854.185328] RAX: 0000000000000001 RBX: 00007f99bfa1b690 RCX: 00007f99bf52fc00
[ 1854.185331] RDX: 0000000000000001 RSI: 0000560056ce3010 RDI: 0000000000000001
[ 1854.185335] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
[ 1854.185338] R10: 00007ffd757229c0 R11: 0000000000000246 R12: 0000560056ce3010
[ 1854.185341] R13: 0000000000000001 R14: 0000560056ce3010 R15: 0000560056ce3010
To generate syscalls and interrupts, "dd" was doing:
dd if=/dev/zero bs=1 count=100000000 | nc 10.0.2.2 12345
I'm not even sure how to go about debugging this. The only printk load I
can really see are the:
"tasks-torture:torture_onoff task: online 0 failed: errno -5"
error messages. But they are only occurring at a rate of 40-50 per
second. They are coming from the pr_alert() in kernel/torture.c:174, so
it should still be hitting spinlocks (either from the console driver or
@console_owner_lock).
I will re-focus on reproducing this with lkp.
John Ogness
WARNING: multiple messages have this Message-ID (diff)
From: John Ogness <john.ogness@linutronix.de>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Petr Mladek <pmladek@suse.com>
Cc: kernel test robot <oliver.sang@intel.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com, zhengjun.xing@linux.intel.com
Subject: Re: [printk] b031a684bf: INFO:rcu_tasks_detected_stalls_on_tasks
Date: Thu, 28 Jan 2021 00:35:06 +0106 [thread overview]
Message-ID: <878s8eari5.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <87bldaaxcc.fsf@jogness.linutronix.de>
On 2021-01-27, John Ogness <john.ogness@linutronix.de> wrote:
> I was finally able to trigger this by using my workstation
Well, I don't know how reliably I can trigger this. I think my time will
be better spent getting lkp to trigger, since that shows to be reliable.
It took me an hour to trigger this one and I have the feeling I got
lucky with it.
[ 1854.183816] INFO: rcu_tasks detected stalls on tasks:
[ 1854.184502] 0000000036ce200f: .. nvcsw: 0/0 holdout: 1 idle_cpu: -1/1
[ 1854.185234] task:dd state:R running task stack: 0 pid:19891 ppid: 668 flags:0x00000000
[ 1854.185273] Call Trace:
[ 1854.185275] __schedule+0xfa9/0x1056
[ 1854.185283] ? firmware_map_remove+0x172/0x172
[ 1854.185300] ? ksys_write+0x147/0x180
[ 1854.185304] schedule+0x170/0x1e3
[ 1854.185307] exit_to_user_mode_prepare+0x27/0xac
[ 1854.185312] syscall_exit_to_user_mode+0x41/0x4f
[ 1854.185316] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 1854.185321] RIP: 0033:0x7f99bf52fc00
[ 1854.185324] RSP: 002b:00007ffd75722bf8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
[ 1854.185328] RAX: 0000000000000001 RBX: 00007f99bfa1b690 RCX: 00007f99bf52fc00
[ 1854.185331] RDX: 0000000000000001 RSI: 0000560056ce3010 RDI: 0000000000000001
[ 1854.185335] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
[ 1854.185338] R10: 00007ffd757229c0 R11: 0000000000000246 R12: 0000560056ce3010
[ 1854.185341] R13: 0000000000000001 R14: 0000560056ce3010 R15: 0000560056ce3010
To generate syscalls and interrupts, "dd" was doing:
dd if=/dev/zero bs=1 count=100000000 | nc 10.0.2.2 12345
I'm not even sure how to go about debugging this. The only printk load I
can really see are the:
"tasks-torture:torture_onoff task: online 0 failed: errno -5"
error messages. But they are only occurring at a rate of 40-50 per
second. They are coming from the pr_alert() in kernel/torture.c:174, so
it should still be hitting spinlocks (either from the console driver or
@console_owner_lock).
I will re-focus on reproducing this with lkp.
John Ogness
next prev parent reply other threads:[~2021-01-27 23:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 8:13 [printk] b031a684bf: INFO:rcu_tasks_detected_stalls_on_tasks kernel test robot
2021-01-22 8:13 ` kernel test robot
2021-01-22 16:21 ` Petr Mladek
2021-01-22 16:21 ` Petr Mladek
2021-01-26 4:52 ` Sergey Senozhatsky
2021-01-26 4:52 ` Sergey Senozhatsky
2021-01-27 21:22 ` John Ogness
2021-01-27 21:22 ` John Ogness
2021-01-27 23:29 ` John Ogness [this message]
2021-01-27 23:29 ` John Ogness
2021-01-28 8:30 ` Sergey Senozhatsky
2021-01-28 8:30 ` Sergey Senozhatsky
2021-01-28 11:26 ` John Ogness
2021-01-28 11:26 ` John Ogness
2021-01-28 14:51 ` Petr Mladek
2021-01-28 14:51 ` Petr Mladek
2021-01-28 15:42 ` John Ogness
2021-01-28 15:42 ` John Ogness
2021-01-28 16:36 ` Petr Mladek
2021-01-28 16:36 ` Petr Mladek
2021-01-28 17:36 ` John Ogness
2021-01-28 17:36 ` John Ogness
2021-01-28 21:38 ` John Ogness
2021-01-28 21:38 ` John Ogness
2021-01-23 2:44 ` Sergey Senozhatsky
2021-01-23 2:44 ` Sergey Senozhatsky
2021-02-02 17:13 ` John Ogness
2021-02-02 17:13 ` John Ogness
2021-02-04 21:32 ` John Ogness
2021-02-04 21:32 ` John Ogness
2021-02-05 9:32 ` Petr Mladek
2021-02-05 9:32 ` Petr Mladek
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=878s8eari5.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=lkp@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.