| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 24 Aug 2008 18:08:33 +0300 From: Jari Aalto <jari.aalto@...te.net> To: linux-kernel@...r.kernel.org Subject: Re: 2.6.25 DMA: Out of SW-IOMMU space - Asus M2N32 AMD 8GB memory Krzysztof Halasa <khc@...waw.pl> writes: > Jari Aalto <jari.aalto@...te.net> writes: > >>>>From Debian stock kernel: >> >> $ grep -Ei 'iommu|agp' /boot/config-2.6.25-2-amd64 >> CONFIG_GART_IOMMU=y >> CONFIG_CALGARY_IOMMU=y >> CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y >> CONFIG_IOMMU_HELPER=y >> CONFIG_AGP=y >> CONFIG_AGP_AMD64=y >> CONFIG_AGP_INTEL=m >> CONFIG_AGP_SIS=m >> CONFIG_AGP_VIA=m > > Should be fine. SWIOTLB is there for a backup, most (?) Intel machines > don't have IOMMU (even the newest desktop boards). > >> Are these the correct boot options, without swiotlb? >> >> iommu=noagp,noaperture,off >> >> Or just: >> >> iommu=off > > Do you have problems without "iommu=XXX"? Initially when the PC was installed (and had no IOMMU) options, that cause the whole harddisk to corrupt and I had to reinstall everything. It might have been a little older kernel (2.6.23?), but I don't recall it exactly. According to messages in syslog I tried to track down similar incidents and found the iommu articles. But the information was like trial and error. Would you suggest that "immu=off" would be best option? Thanks, Jari -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists