From: Haris Okanovic <haris.okanovic@ni.com>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] timers: Don't wake ktimersoftd on every tick
Date: Thu, 12 Apr 2018 10:00:29 -0500 [thread overview]
Message-ID: <c2664fbe-52e7-1044-e9f9-de4875047ee8@ni.com> (raw)
In-Reply-To: <1523332961.4827.1.camel@gmx.de>
Hi Mike,
I haven't tested the patch with wireshark until now. My system also
hangs shortly after it starts. I'm pretty sure I hit workqueues in my
earlier tests via the block driver, but it's clearly not whatever
wireshark is using. I'll look at it and try to post a fix. CCing the
list to avoid this patch until then.
Thanks,
Haris
On 04/09/2018 11:02 PM, Mike Galbraith wrote:
> Hi,
>
> Are these patches dead, or are you planning another submission? I ask
> because I discovered that with them applied, firing up wireshark hangs
> the box 100% repeatably, with wireshark never fully initializing.
>
> Applying them to an otherwise virgin 4.14.20-rt17 to be sure...
>
> crash> bt 6016PID: 6016 TASK: ffff95dd68572180 CPU: 2 COMMAND:
> "dumpcap"
> #0 [ffffb490094f3bc0] __schedule at ffffffffa56d55b9
> #1 [ffffb490094f3c40] schedule at ffffffffa56d5a03
> #2 [ffffb490094f3c58] schedule_timeout at ffffffffa56d8467
> #3 [ffffb490094f3cd8] wait_for_completion at ffffffffa56d6e34
> #4 [ffffb490094f3d18] __wait_rcu_gp at ffffffffa50e59cd
> #5 [ffffb490094f3d58] synchronize_rcu at ffffffffa50ec14e
> #6 [ffffb490094f3d98] packet_set_ring at ffffffffc0c74da0 [af_packet]
> #7 [ffffb490094f3e50] packet_setsockopt at ffffffffc0c75d23 [af_packet]
> #8 [ffffb490094f3ef8] sys_setsockopt at ffffffffa558a5e2
> #9 [ffffb490094f3f30] do_syscall_64 at ffffffffa5001b05
> #10 [ffffb490094f3f50] entry_SYSCALL_64_after_hwframe at ffffffffa5800065
> RIP: 00007f3107a1cfaa RSP: 00007ffc9745c2e8 RFLAGS: 00000246
> RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f3107a1cfaa
> RDX: 0000000000000005 RSI: 0000000000000107 RDI: 0000000000000003
> RBP: 000055ae1d8eb470 R8: 000000000000001c R9: 0000000000000002
> R10: 00007ffc9745c350 R11: 0000000000000246 R12: 00007ffc9745c350
> R13: 0000000000000000 R14: 000055ae1d8eb200 R15: 000055ae1d8eb2d0
> ORIG_RAX: 0000000000000036 CS: 0033 SS: 002b
> crash> dmesg
> ...
> [ 483.808197] BUG: workqueue lockup - pool cpus=2 node=0 flags=0x0 nice=0 stuck for 52s!
> [ 483.808204] Showing busy workqueues and worker pools:
> [ 483.808206] workqueue events: flags=0x0
> [ 483.808208] pwq 4: cpus=2 node=0 flags=0x0 nice=0 active=1/256
> [ 483.808211] pending: check_corruption
> [ 492.695124] sysrq: SysRq : Trigger a crash
>
next prev parent reply other threads:[~2018-04-12 15:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 21:44 [RFC v2] timers: Don't wake ktimersoftd on every tick Haris Okanovic
2016-12-23 17:28 ` Sebastian Andrzej Siewior
2016-12-28 18:06 ` Haris Okanovic
2017-02-03 16:51 ` Sebastian Andrzej Siewior
2017-02-03 18:21 ` [PATCH] " Haris Okanovic
2017-02-10 17:02 ` Sebastian Andrzej Siewior
2017-05-26 17:16 ` [PATCH] Revert "timers: Don't wake ktimersoftd on every tick" Anna-Maria Gleixner
2017-05-26 19:27 ` Haris Okanovic
2017-05-26 19:49 ` Thomas Gleixner
2017-05-26 20:25 ` Haris Okanovic
2017-05-26 20:50 ` Thomas Gleixner
2017-06-02 14:37 ` Haris Okanovic
2017-06-04 14:17 ` Thomas Gleixner
2017-07-17 21:58 ` Haris Okanovic
2017-07-17 22:04 ` [PATCH v2] timers: Don't wake ktimersoftd on every tick Haris Okanovic
2017-07-18 21:33 ` Thomas Gleixner
2017-08-03 21:04 ` Haris Okanovic
2017-08-03 21:06 ` [PATCH v3 1/2] " Haris Okanovic
2017-08-03 21:06 ` [PATCH v3 2/2] timers: Don't search for expired timers while TIMER_SOFTIRQ is scheduled Haris Okanovic
2018-01-05 19:37 ` Haris Okanovic
2018-03-01 15:49 ` Haris Okanovic
2018-03-01 15:54 ` Thomas Gleixner
2018-03-01 16:35 ` Haris Okanovic
2018-03-01 16:47 ` Sebastian Andrzej Siewior
2018-03-01 18:37 ` Haris Okanovic
2018-03-01 19:06 ` Sebastian Andrzej Siewior
2018-03-02 14:52 ` Sebastian Andrzej Siewior
2018-03-02 16:29 ` Haris Okanovic
2018-03-02 16:39 ` Sebastian Andrzej Siewior
2018-03-02 17:19 ` Haris Okanovic
2018-03-06 23:39 ` [PATCH v4 1/2] timers: Don't wake ktimersoftd on every tick Haris Okanovic
2018-03-06 23:39 ` [PATCH v4 2/2] timers: Don't search for expired timers while TIMER_SOFTIRQ is scheduled Haris Okanovic
[not found] ` <1523332961.4827.1.camel@gmx.de>
2018-04-12 15:00 ` Haris Okanovic [this message]
2018-06-19 12:43 ` [PATCH v4 1/2] timers: Don't wake ktimersoftd on every tick Daniel Bristot de Oliveira
2018-06-20 14:24 ` Haris Okanovic
2018-06-28 16:36 ` Haris Okanovic
2018-06-28 16:40 ` [PATCH v5 " Haris Okanovic
2018-06-28 16:40 ` [PATCH v5 2/2] timers: Don't search for expired timers while TIMER_SOFTIRQ is scheduled Haris Okanovic
2018-07-13 12:01 ` [PATCH v5 1/2] timers: Don't wake ktimersoftd on every tick Anna-Maria Gleixner
2018-07-13 14:37 ` Haris Okanovic
2017-05-27 7:47 ` [PATCH] Revert "timers: Don't wake ktimersoftd on every tick" Sebastian Andrzej Siewior
2017-02-03 18:27 ` [RFC v2] timers: Don't wake ktimersoftd on every tick Haris Okanovic
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=c2664fbe-52e7-1044-e9f9-de4875047ee8@ni.com \
--to=haris.okanovic@ni.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--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 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 NNTP newsgroup(s).