Received: by 2002:a05:7412:31a9:b0:e2:908c:2ebd with SMTP id et41csp4517424rdb; Fri, 15 Sep 2023 04:59:32 -0700 (PDT) X-Google-Smtp-Source: AGHT+IE8assevY8Q2NQP7c0NwB/RSimuGQ4Dgz8GY9VAb95c4ghvbW56lzzPVNbopYdZmLHQVGwZ X-Received: by 2002:a05:6a21:6d92:b0:136:ea0e:d23 with SMTP id wl18-20020a056a216d9200b00136ea0e0d23mr1689774pzb.11.1694779172003; Fri, 15 Sep 2023 04:59:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1694779171; cv=none; d=google.com; s=arc-20160816; b=BmDFlz7zu27rUChR+Q4xkYo7daMS1itlYpR8/nNscW/kd1OPF7ZkZc3iti5BCEBE75 QwQnubbG4561LPf0xiYgkj9X2qimcLlOZ0a3fM1eJgXTcCz0biajfrqjb+AaH3Fx6xTt HP01SFvnr2KThmjtLl9nxsr2CDikTnuw1zy56VOsrXyGeug3wDDd4y350n3uMYuMzhA1 WNN1LQBEZPKjCZA7pMQmwn/hfJUg6L3NP9oU4i3c4CEAi/5UNYbKvStGtHT+8DebF48U /0fGzDP+Rk6BpAvvOdRP2+M7vso4zU0K9sgrt7UTvVjJ7l1UKF/5/eaf73XZ7WRQgqBp 4ESg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:mime-version :dkim-signature; bh=7ix/M53sUnRrSKn9dKsE33ijrUivOY5j8IoNGsWwLLY=; fh=Ch2b7ImtZowzvJyG9CnvTO8jn0kD6hiJBJB9Ci7Qggg=; b=bgk45ihZiGGoB50dyiF9pQmmQ6ih7kC4IH8DibfH6h2LUk7iai9JIE8mbdTMEbVQA+ 28KhA7Hcia3s9lmkAt8Yv1pUjINjxMt9RfCmD2/Ag5Feje9DHz2MmB+vkdCc9SLUWnd4 H4ttkz5wFfLSQg7/250p8r751w/qqRD9S4W0/IZNv+TQ2OWecBFCfXunzh+Opc3fYfM4 n8/uDAsm1U5NsE4KDjOz/EQsarik0aux1uQmzD9+IxX4pxrJbWBADScnAeCt4D5jJXTi r6G7hc0ON5Ldk3s3pGZIJs4nrCbev1CdXq5NVoWmC+g2LvIlkLaN5wpmLHwu+kxAPmif Spvw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=TEFi5u5g; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from snail.vger.email (snail.vger.email. [23.128.96.37]) by mx.google.com with ESMTPS id x20-20020aa793b4000000b0068fda436d14si3081502pff.287.2023.09.15.04.59.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 15 Sep 2023 04:59:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=TEFi5u5g; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by snail.vger.email (Postfix) with ESMTP id 7290A813CDB1; Thu, 14 Sep 2023 22:27:44 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at snail.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232062AbjIOF1o (ORCPT + 99 others); Fri, 15 Sep 2023 01:27:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41258 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229554AbjIOF1m (ORCPT ); Fri, 15 Sep 2023 01:27:42 -0400 Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6564A271B; Thu, 14 Sep 2023 22:27:36 -0700 (PDT) Received: by mail-ua1-x92c.google.com with SMTP id a1e0cc1a2514c-791b8525b59so738337241.1; Thu, 14 Sep 2023 22:27:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1694755654; x=1695360454; darn=vger.kernel.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=7ix/M53sUnRrSKn9dKsE33ijrUivOY5j8IoNGsWwLLY=; b=TEFi5u5g8RXU294s7/LF8MX27YPhlC5ysEgWDdnQ6tZeyioMbi0G5n9Oixnqr3v/fK U9k8+9m9BjObcHITlQ2mgDc351z+TJJVhlo4jgrRqA+xz+CnOMVhFtXpKUb/zPJeyPQO 7qd3bxPvcg6lA6d5XdCg5Y0Rm/LO9Ys2kVHWG9fCPLAfbvpGEZs3m64p2Eeyzrtv1xxu E0b0mPc9o6/EdawYvTkRAxRhsIiq9msHgMGchLZma9D/XRWmEevxTVkNSUAUHmuXnq2y 3KP8jJq7F5Syk3Xdsvyxj45B4ioNH0T1ODtVHzH9gE5YoCJp4gp64PVSsxCP0jdDiIEs LQgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694755654; x=1695360454; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=7ix/M53sUnRrSKn9dKsE33ijrUivOY5j8IoNGsWwLLY=; b=Z7QGD+lncPAoHY/+3CVm57Wky0WUrxvonZsJDO4Uy4hcyryzx+Kmd4PCap27yCXRrQ Swtr7CGCq8eTKI36PdzGOwwBWJNvOSfF1XnYZtsoTKWENgeDKIVPgjvd2dZKIKOcnoOF dAV5rWEQIbFcSSX1/Cdne8LOMmyUSGcxx/mHZB8B0NsKHlzUHdphdmOs95CrgZ/aJgDY RWuiPo5oXVQAUtzvEJzCQC+9lfmUktBNyt0PEu/D4r59bHcS984k/jQ4ObHpSqwKed6/ B9UKa6JO0UKwZvuT5HhGIXrJBM601TqfIBJ4V0pe3oF2mAMjGz4fBqkj4P8ODWKaRmd8 8YDQ== X-Gm-Message-State: AOJu0YxDL/bnGAokDHcpsxva94/LKq/hQuHSmjho+NqcsMfKni20P/os ww/vigbDYcJwqbmMkxI7XAejREb1pKUOCriCz+OA+dVvr6E= X-Received: by 2002:a1f:e082:0:b0:495:cace:d59c with SMTP id x124-20020a1fe082000000b00495caced59cmr747710vkg.0.1694755654556; Thu, 14 Sep 2023 22:27:34 -0700 (PDT) MIME-Version: 1.0 From: Kyle Sanderson Date: Thu, 14 Sep 2023 22:27:22 -0700 Message-ID: Subject: Linux 6.1.52 regression: Intel QAT kernel panic (memory corruption) To: Linux-Kernal , qat-linux@intel.com Cc: Greg KH , Linus Torvalds , Linux Crypto Mailing List , Giovanni Cabiddu Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (snail.vger.email [0.0.0.0]); Thu, 14 Sep 2023 22:27:44 -0700 (PDT) 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. I genuinely do not understand how this keeps breaking in these critical contexts completely hosing the machine. I was under the impression it was disabled on this box the entire time since the last run-in with this, but it must have gotten flipped back on when I did a firmware update back in December 2022. Kyle.