From: Robin Murphy <robin.murphy@arm.com>
To: Jason Adriaanse <jason_a69@yahoo.co.uk>, hch@lst.de
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [regression] Bug 217218 - Trying to boot Linux version 6-2.2 kernel with Marvell SATA controller 88SE9235
Date: Mon, 24 Apr 2023 14:20:50 +0100 [thread overview]
Message-ID: <5f37b0b0-6cb5-b210-a894-d1e91976126e@arm.com> (raw)
In-Reply-To: <fc9f4cef-9426-c9d2-3c2c-3ce12fe5f6c3@yahoo.co.uk>
On 2023-04-22 07:25, Jason Adriaanse wrote:
> Hi Christoph,
>
> Sorry for my late reply, I have been on the road.
>
> So, if I boot with
> intel_iommu=off
> Then the server boots fine..although that is not a solution because I
> need Intel iommu for virtualisation.
>
> Also, I build all my kernels with CONFIG_INTEL_IOMMU=y
>
If you boot 5.15 *without* the "iommu=soft" argument, just
"intel_iommu=on", does that also break?
Robin.
next prev parent reply other threads:[~2023-04-24 13:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a79ea7f5-6a41-a6c9-cfec-ba01aa2a3cfa@leemhuis.info>
2023-03-28 1:22 ` [regression] Bug 217218 - Trying to boot Linux version 6-2.2 kernel with Marvell SATA controller 88SE9235 Christoph Hellwig
2023-03-30 12:18 ` Robin Murphy
2023-03-31 2:20 ` Jason Adriaanse
2023-04-16 6:55 ` Christoph Hellwig
2023-04-22 6:25 ` Jason Adriaanse
2023-04-24 13:20 ` Robin Murphy [this message]
2023-04-24 13:44 ` Jason Adriaanse
2023-04-24 14:07 ` Robin Murphy
2023-04-25 4:17 ` Jason Adriaanse
2023-04-25 11:37 ` Robin Murphy
2023-04-25 13:58 ` Jason Adriaanse
2023-05-22 10:26 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 11:01 ` Robin Murphy
2023-05-22 11:33 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-02 13:07 ` Thorsten Leemhuis
2023-06-06 9:24 ` Christoph Hellwig
2023-06-06 10:26 ` Jason Adriaanse
2023-04-16 6:41 ` Christoph Hellwig
2023-04-17 11:21 ` Robin Murphy
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=5f37b0b0-6cb5-b210-a894-d1e91976126e@arm.com \
--to=robin.murphy@arm.com \
--cc=baolu.lu@linux.intel.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=jason_a69@yahoo.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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).