From: Joerg Vehlow <lkml@jv-coder.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Tom Rix <trix@redhat.com>, Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
herbert@gondor.apana.org.au, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] xfrm : lock input tasklet skb queue
Date: Mon, 28 Oct 2019 11:44:57 +0100 [thread overview]
Message-ID: <5b45c8f6-1aa2-2e1e-9019-a140988bba80@jv-coder.de> (raw)
In-Reply-To: <20191025102203.zmkqvvg5tofaqfw6@linutronix.de>
Am 25.10.2019 um 12:22 schrieb Sebastian Andrzej Siewior:
> On 2019-10-25 12:14:59 [+0200], Joerg Vehlow wrote:
>> Here is one of the oops logs I still have:
>>
>> [ 139.717273] CPU: 2 PID: 11987 Comm: netstress Not tainted
>> 4.19.59-rt24-preemt-rt #1
> could you retry with the latest v5.2-RT, please? qemu should boot fine…
>
> Sebastian
I was unable to reproduce it with 5.2.21-rt13. Do you know if something
changed in network scheduling code or could it be just less likely?
next prev parent reply other threads:[~2019-10-28 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 0:22 [PATCH v2 1/1] xfrm : lock input tasklet skb queue Tom Rix
2019-10-24 10:31 ` Steffen Klassert
2019-10-25 9:37 ` Joerg Vehlow
2019-10-25 9:47 ` Sebastian Andrzej Siewior
2019-10-25 10:14 ` Joerg Vehlow
2019-10-25 10:22 ` Sebastian Andrzej Siewior
2019-10-25 14:26 ` Tom Rix
2019-10-25 19:25 ` Sebastian Andrzej Siewior
2019-10-28 10:44 ` Joerg Vehlow [this message]
2019-10-28 15:15 ` Sebastian Andrzej Siewior
2019-10-29 7:33 ` Joerg Vehlow
2019-11-18 10:46 ` Sebastian Andrzej Siewior
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=5b45c8f6-1aa2-2e1e-9019-a140988bba80@jv-coder.de \
--to=lkml@jv-coder.de \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=steffen.klassert@secunet.com \
--cc=tglx@linutronix.de \
--cc=trix@redhat.com \
/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.