Bug#1112627: linux-image-6.16.3+deb14-amd64: Intel audio no longer works: DMAR: [DMA Write NO_PASID] Request device [00:1b.0] ... non-zero reserved fields in PTE
Control: tags -1 + moreinfo
Hi Francesco,
On Sat, Oct 18, 2025 at 01:12:05PM +0200, Francesco Poli wrote:
> On Fri, 17 Oct 2025 15:44:21 +0200 Salvatore Bonaccorso wrote:
>
> > Control: tags -1 + moreinfo
> >
> > Hi Francesco,
>
> Hello Salvatore,
>
> >
> > On Sat, Oct 11, 2025 at 06:50:06PM +0200, Francesco Poli wrote:
> [...]
> > > $ git checkout v6.13-rc6
> > > $ make CC=gcc-14 my_defconfig
> > > $ make CC=gcc-14 -j 4 bindeb-pkg
> > > ---------> v6.13-rc6 is good (which is unexpected!)
> > >
> > >
> > >
> > > What should we deduce from this unexpected result?
> [...]
> > > What do you suggest to do, next?
> >
> > The suspsect is that you see difference as you end in the self
> > compiled kernel without enabled IOMMU. (Background; The Debian config
> > has CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y, ntoably this option
> > does not exist in upstream, so you end with
> > CONFIG_INTEL_IOMMU_DEFAULT_ON not set only and see the difference.
> > (if you want to look up what I'm talking, this is
> > features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch
> > in the source).
> >
> > before we might suggest you need to use the workaround to disable
> > iommu, can you please now test the *selfcompiled* v6.13-rc6 with IOMMU
> > enabled, by booting it with the kernel command line argument
> > intel_iommu=on. I expect you will see then the problem in same way.
>
> Yes, I can confirm.
>
> $ cat /proc/cmdline
> BOOT_IMAGE=/boot/vmlinuz-6.13.0-rc6 root=UUID=a5d36947-d90d-4818-9184-7cda88ade7fd ro quiet
>
> This is good.
>
>
> $ cat /proc/cmdline
> BOOT_IMAGE=/boot/vmlinuz-6.13.0-rc6 root=UUID=a5d36947-d90d-4818-9184-7cda88ade7fd ro intel_iommu=on quiet
>
> This is bad: no audio output or input and the usual flood of
> error messages in /var/log/kern.log
>
> kernel: DMAR: DRHD: handling fault status reg 3
> kernel: DMAR: [DMA Write NO_PASID] Request device [00:1b.0] fault addr 0xffa01000 [fault reason 0x0c] non-zero reserved fields in PTE
>
>
>
> Please let me know how to proceed.
> Thanks for your kind assistance!
So we talked about your issue on the last team meeting, and have not
much good steps forwward but the following.
With intel_iommu=off check the full boot log if there are some hints
about swiotlb issues.
https://docs.kernel.org/core-api/swiotlb.html
But then here we would have expected to see for instance an overflow
warning (for which then could try playing around increasing the size).
The second thing we were suggsting: In the boot log the BIOS version
shown is from 2014. Double check if there is an update available. If
so please upgrade to the latest available one, which might have fixed
underlying issue.
Regards,
Salvatore
Reply to: