From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Eneko Lacunza via pve-user <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] PVE 7.2 - Avago MegaRAID broken?
Date: Thu, 19 May 2022 18:31:38 +0200 [thread overview]
Message-ID: <20220519183138.1647bed6@rosa.proxmox.com> (raw)
In-Reply-To: <mailman.94.1652972304.356.pve-user@lists.proxmox.com>
Hi,
On Thu, 19 May 2022 16:57:44 +0200
Eneko Lacunza via pve-user <pve-user@lists.proxmox.com> wrote:
> Hi all,
>
> Today we installed PVE 7.1 (ISO) in a relatively old machine.
any more details on what kind of machine this is
(CPU generation, if it's an older HP/Dell/Supermicro server or
consumerhardware)?
> Kernel will print lots of messages like
>
> "DMAR: DRHD: handling fault status reg 3"
> "DMAR: [DMA Read NO_PASID] Request device [02:00.0] fault ???? 4b311000
> [fault reason 0x06] PTE Readaccess is not set.
could you please try (in that order, and until one the suggestions fixes
the issue):
* adding `iommu=pt` to the kernel cmdline
* adding `intel_iommu=off` to the kernel cmdline
we have updated the known-issues section of the release-notes to suggest
this already after a few similar reports with older hardware/unusual
setups in our community forum:
https://pve.proxmox.com/wiki/Roadmap#7.2-known-issues
see
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_edit_kernel_cmdline
for instruction on how to edit the cmdline.
> This is worked-around now, but I'm starting to worry about latest 5.15
> kernel in PVE... :-)
>
I think we have similar reports with each new kernel-series - mostly with
older systems, which need to install a small workaround (usually module
parameter or kernel cmdline switch).
Our tests on many machines in our testlab (covering the past 10 years of
hardware more or less well) all did not show any general issues - but
it's sadly always a hit and miss.
Please let us know if the changes help
Kind regards,
stoiko
parent reply other threads:[~2022-05-19 16:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.94.1652972304.356.pve-user@lists.proxmox.com>]
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=20220519183138.1647bed6@rosa.proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pve-user@lists.proxmox.com \
/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