惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园_首页
大猫的无限游戏
大猫的无限游戏
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Apple Machine Learning Research
Apple Machine Learning Research
B
Blog
B
Blog RSS Feed
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
P
Proofpoint News Feed
MyScale Blog
MyScale Blog
Engineering at Meta
Engineering at Meta
量子位
H
Hackread – Cybersecurity News, Data Breaches, AI and More
T
Tailwind CSS Blog
Stack Overflow Blog
Stack Overflow Blog
N
Netflix TechBlog - Medium
T
The Blog of Author Tim Ferriss
U
Unit 42
aimingoo的专栏
aimingoo的专栏
博客园 - 叶小钗
博客园 - 【当耐特】
云风的 BLOG
云风的 BLOG
博客园 - Franky
博客园 - 聂微东

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
proxmox-kernel-6.8.12-29 causing array controller errors
invalid@exam · 2026-06-12 · via Proxmox Support Forum

With the new Kernel proxmox-kernel-6.8.12-29 we are getting a lot of errors from our HP Array Controller "Smart HBA H240ar", that gives out these kernel errors:

dmar_fault: 155 callbacks suppressed
DMAR: DRHD: handeling fault status reg 202
DMAR: [DMA Read NO_PASID] Request device [03:00.0] fault addr 0x791dc00 [fault reason 0x06] PTE Read access is not set

This is on our HP ProLiant DL380 Gen9 servers. When we revert back to proxmox-kernel-6.8.12-23 it works. What could be the solution to fix this issue? Is it maybe a problem with the newer kernel and an old firmware (our controller firmware is version 7.00)?

Hi @fes-it-admin

thanks for posting in the forum!

Disclaimer: I haven't done any extensive digging into the root cause of the problem, but as a "quick to try" hunch: Try to disable the shared memory Features of the H240ar in the device configuration.
In another thread [1] this caused problems with passing through to a VM, so maybe it also interferes with the regular operation in some way.

Yours sincerely
Jonas

[1] https://forum.proxmox.com/threads/can’t-passthrough-p840.155980/

Looks like something changed in the IOMMU/VT-d handling between those two kernel versions. The DMAR faults basically mean the IOMMU is blocking DMA requests from your H240ar.

Try adding iommu=pt to your kernel command line in /etc/default/grub (GRUB_CMDLINE_LINUX_DEFAULT), then update-grub and reboot. Passthrough mode tells the IOMMU to not mess with DMA for devices that aren't passed through to VMs, which usually fixes it.

If you don't need IOMMU/passthrough at all, intel_iommu=off would also work but is the bigger hammer.

And yeah, firmware 7.00 on the H240ar is pretty old. Might be worth updating that too when you have a maintenance window, HPE had a bunch of fixes for IOMMU-related stuff on Gen9.

What does your current kernel cmdline look like? cat /proc/cmdline