From: Steffen Maier <maier@linux.ibm.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
Lai Jiangshan <laijs@linux.alibaba.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"Paul E. McKenney" <paulmck@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
regressions@lists.linux.dev, lkft-triage@lists.linaro.org
Subject: Re: [next] next-20220223 kernel crash
Date: Fri, 25 Feb 2022 13:22:34 +0100 [thread overview]
Message-ID: <65d40e00-d7a4-0210-5253-d5d1744f0343@linux.ibm.com> (raw)
In-Reply-To: <CA+G9fYtzLr+9T9Z1N8QLznW6DqTOU8iSHvgMftdhe2XkEf8F8g@mail.gmail.com>
On 2/24/22 14:28, Naresh Kamboju wrote:
> Linux next-20220223 boot failed due to the kernel crash on all devices.
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> crash log on x86_64 machine [1]:
> [ 5.326681] Please do not flush events WQ.
> [ 5.327480] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> 5.17.0-rc5-next-20220223 #1
Is this related?:
https://lore.kernel.org/all/4e5fe60d-abbb-6e73-b8cc-c3e1a314fbce@samsung.com/T/#u
--
Mit freundlichen Gruessen / Kind regards
Steffen Maier
Linux on IBM Z and LinuxONE
https://www.ibm.com/privacy/us/en/
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Gregor Pillen
Geschaeftsfuehrung: David Faller
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
prev parent reply other threads:[~2022-02-25 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 13:28 Naresh Kamboju
2022-02-25 12:22 ` Steffen Maier [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=65d40e00-d7a4-0210-5253-d5d1744f0343@linux.ibm.com \
--to=maier@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=jiangshanlai@gmail.com \
--cc=laijs@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=paulmck@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
--cc=tj@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
all inboxes | Powered by JetHome®