From: Greg KH <gregkh@linuxfoundation.org>
To: "Janne Huttunen (Nokia)" <janne.huttunen@nokia.com>
Cc: "minyard@acm.org" <minyard@acm.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: IPMI related kernel panics since v4.19.286
Date: Mon, 19 Jun 2023 14:23:47 +0200 [thread overview]
Message-ID: <2023061927-fox-constrict-1918@gregkh> (raw)
In-Reply-To: <7ae67dbec16b93f0e6356337e52bf21921b0897c.camel@nokia.com>
On Mon, Jun 19, 2023 at 11:11:16AM +0000, Janne Huttunen (Nokia) wrote:
>
> We recently updated an internal test server from kernel v4.19.273
> to v4.19.286 and since then it has already multiple times triggered
> a kernel panic due to a hard lockup. The lockups look e.g. like
> this:
Does this also happen on newer 5.4 and 6.4-rc7 releases?
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-19 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 11:11 IPMI related kernel panics since v4.19.286 Janne Huttunen (Nokia)
2023-06-19 12:23 ` Greg KH [this message]
2023-06-19 13:32 ` Corey Minyard
2023-06-19 12:52 ` Corey Minyard
2023-06-20 9:56 ` Janne Huttunen (Nokia)
2023-06-20 11:54 ` Corey Minyard
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=2023061927-fox-constrict-1918@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=janne.huttunen@nokia.com \
--cc=minyard@acm.org \
--cc=stable@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).