Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #93331
| From | Tj <tj.iam.tj@proton.me> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#1141183: src:linux: I/O errors on SATA devices related to IOMMU |
| Date | 2026-07-13 00:10 +0200 |
| Message-ID | <Ngax3-4ndE-19@gated-at.bofh.it> (permalink) |
| References | <NbNfH-1X6L-17@gated-at.bofh.it> <NbOY9-1YaS-7@gated-at.bofh.it> <Ng7Sx-4lHx-17@gated-at.bofh.it> <NbNfH-1X6L-17@gated-at.bofh.it> <Ng7Sx-4lHx-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
> Also regarding you questions on IRC last week: I hope you don't forget > that Debian does some changes to the default IOMMU configuration. So > applying the same config to an upstream kernel will need explicit > setting the wanted iommu state. Yes, we're testing with the related Debian config (now without any Debian patches though) # CONFIG_INTEL_IOMMU_DEFAULT_ON is not set CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y # CONFIG_INTEL_IOMMU_DEFAULT_OFF is not set and intel_iommu=on Originally we suspected an interaction with the Debian IOMMU intgpu patches but were able to rule them out.
Back to linux.debian.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Bug#1141183: src:linux: I/O errors on SATA devices related to IOMMU Tj <tj.iam.tj@proton.me> - 2026-07-01 00:20 +0200
Bug#1141183: src:linux: I/O errors on SATA devices related to IOMMU Bastian Blank <waldi@debian.org> - 2026-07-12 21:20 +0200
Bug#1141183: src:linux: I/O errors on SATA devices related to IOMMU Tj <tj.iam.tj@proton.me> - 2026-07-13 00:10 +0200
csiph-web