From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To: Kyle Sanderson <kyle.leet@gmail.com>
Cc: Linux-Kernal <linux-kernel@vger.kernel.org>,
<qat-linux@intel.com>, "Greg KH" <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: Linux 6.1.52 regression: Intel QAT kernel panic (memory corruption)
Date: Fri, 15 Sep 2023 06:55:05 +0100 [thread overview]
Message-ID: <ZQPxuZ2tifa9bQKJ@gcabiddu-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CACsaVZ+LkHwTKO4XE_FFM62SbF3gGD4DZyse-9Y1UbJUgrhvfA@mail.gmail.com>
On Thu, Sep 14, 2023 at 10:27:22PM -0700, Kyle Sanderson wrote:
> Hello Intel QAT Maintainers,
>
> It looks like QAT has regressed again. The present symptom is just
> straight up memory corruption. I was running Canonical 6.1.0-1017-oem
> and it doesn't happen, with 6.1.0-1020-oem and 6.1.0-1021-oem it does.
> I don't know what these map to upstream, however with NixOS installed
> the same corruption failure occurs on 6.1.52. The stack traces give
> illegal instructions and all kinds of badness across all modules when
> the device is simply present on the system, resulting in a hung
> system, or a multitude of processes crashing and the system failing to
> start. Disabling the device in the system BIOS results in a working
> system, and no extreme corruption. kmem_cache_alloc_node is the common
> fixture in the traces (I don't have a serial line), but I suspect
> that's not where the problem is. The corruption this time happens
> without block crypto being involved, and simply booting the installer
> from a USB stick.
This is probably be related to [1].
Versions from 6.1.39 to 6.1.52 are affected. Fixed in v6.1.53.
[1] https://www.spinics.net/lists/stable/msg678947.html
Regards,
--
Giovanni
next prev parent reply other threads:[~2023-09-15 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 5:27 Kyle Sanderson
2023-09-15 5:55 ` Giovanni Cabiddu [this message]
2023-10-05 3:55 ` Kyle Sanderson
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=ZQPxuZ2tifa9bQKJ@gcabiddu-mobl1.ger.corp.intel.com \
--to=giovanni.cabiddu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kyle.leet@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=torvalds@linux-foundation.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®