From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id 9F4871FF16E
	for <inbox@lore.proxmox.com>; Mon, 14 Apr 2025 16:57:21 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 88FB53657A;
	Mon, 14 Apr 2025 16:57:19 +0200 (CEST)
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Date: Mon, 14 Apr 2025 16:57:05 +0200
Message-Id: <20250414145705.1262110-1-s.ivanov@proxmox.com>
X-Mailer: git-send-email 2.39.5
MIME-Version: 1.0
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.064 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: [pve-devel] [PATCH pve-kernel] cherry-pick additional fix for AMD
 Epyc genua systems
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>

reports in our community forum say, that some systems still run into a
boot-loop with the latest proxmox-kernel-6.14 (6.14.0-2):
https://forum.proxmox.com/threads/164497/post-762978
Pulling in this patch here (or preventing the module from being loaded) fixes
the issue for them.

As our test-system boots fine with this patch and without it (based on
my tests for including the 2 patches, that are also cherry-picked for
kernel.org stable 6.14.2) I think adding this additionally should not
pose much potential for regression.

Fixes: 4a6063d2f956 ("cherry-pick fixes for AMD Epyc genua systems")
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
 ...ine-ae4dma-Remove-deprecated-PCI-IDs.patch | 31 +++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 patches/kernel/0016-dmaengine-ae4dma-Remove-deprecated-PCI-IDs.patch

diff --git a/patches/kernel/0016-dmaengine-ae4dma-Remove-deprecated-PCI-IDs.patch b/patches/kernel/0016-dmaengine-ae4dma-Remove-deprecated-PCI-IDs.patch
new file mode 100644
index 000000000000..43557b79d6bf
--- /dev/null
+++ b/patches/kernel/0016-dmaengine-ae4dma-Remove-deprecated-PCI-IDs.patch
@@ -0,0 +1,31 @@
+From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
+From: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
+Date: Mon, 3 Feb 2025 21:55:09 +0530
+Subject: [PATCH] dmaengine: ae4dma: Remove deprecated PCI IDs
+
+Two previously used PCI IDs are deprecated and should not be used for
+AE4DMA. Hence, remove as they are unsupported for AE4DMA.
+
+Fixes: 90a30e268d9b ("dmaengine: ae4dma: Add AMD ae4dma controller driver")
+Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
+Link: https://lore.kernel.org/r/20250203162511.911946-2-Basavaraj.Natikar@amd.com
+Signed-off-by: Vinod Koul <vkoul@kernel.org>
+(cherry picked from commit b87c29c007e80f4737a056b3c5c21b5b5106b7f7)
+Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
+---
+ drivers/dma/amd/ae4dma/ae4dma-pci.c | 2 --
+ 1 file changed, 2 deletions(-)
+
+diff --git a/drivers/dma/amd/ae4dma/ae4dma-pci.c b/drivers/dma/amd/ae4dma/ae4dma-pci.c
+index 587c5a10c1a8b2dbb925c31af86b1d0b23438b45..2c63907db22825e260653c6e9654e2b9eaa10d43 100644
+--- a/drivers/dma/amd/ae4dma/ae4dma-pci.c
++++ b/drivers/dma/amd/ae4dma/ae4dma-pci.c
+@@ -137,8 +137,6 @@ static void ae4_pci_remove(struct pci_dev *pdev)
+ }
+ 
+ static const struct pci_device_id ae4_pci_table[] = {
+-	{ PCI_VDEVICE(AMD, 0x14C8), },
+-	{ PCI_VDEVICE(AMD, 0x14DC), },
+ 	{ PCI_VDEVICE(AMD, 0x149B), },
+ 	/* Last entry must be zero */
+ 	{ 0, }
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel