linux-image-amd64: In bullseye, IOMMU interfering with Marvel SATA card operation
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Mohamed <msaudi@msaudi.me>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: linux-image-amd64: In bullseye, IOMMU interfering with Marvel
SATA card operation
Message-ID: <164043429145.17334.15005630158198407779.reportbug@Backups.msh>
X-Mailer: reportbug 7.10.3+deb11u1
Date: Sat, 25 Dec 2021 14:11:31 +0200
Package: linux-image-amd64
Version: 5.10.84-1
Severity: important
Tags: d-i
-- System Information:
Debian Release: 11.2
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500,
'stable-security')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages linux-image-amd64 depends on:
ii linux-image-5.10.0-10-amd64 5.10.84-1
linux-image-amd64 recommends no packages.
linux-image-amd64 suggests no packages.
-- no debconf information
I have this SATA controller installed in HP Elite 8300 CMT
01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9230
PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller [1b4b:9230] (rev 11)
It was working fine in all previous debian releases (8,9 and 10), after
upgrading to bullseye it stopped detecting drives connected to it,
complaining about SATA link COMRESET error.
I still have the latest kernel from bullseye installed
(4.19.0-18-amd64). I rebooted the PC to use that kernel
(4.19.0-18-amd64), the card worked as expected.
I tried to use the following kernels from debian repositories but all of
them had the same issue
linux-image-5.16.0-rc5-amd64
linux-image-5.14.0-0.bpo.2-amd64
linux-image-5.10.0-9-amd64
linux-image-5.10.0-8-amd64
After searching online I found this forum post about the same problem
for the exact card
https://forums.debian.net/viewtopic.php?t=150004
The suggested solution was to add the following parameters to the kernel
commandline
iommu=off intel_iommu=off iommu.passthrough=1
The suggested solution works for me.
reportbug wasn't able to send the message. So I am pasting the whole
report. My apologies for the messy message.
Thank you
Reply to: