linux-kernel - Re: Dual Core Opteron hangs, iommu Entries (x86

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <p73zmcw2uzd.fsf@verdi.suse.de>
Date:	19 Sep 2006 09:09:26 +0200
From:	Andi Kleen <ak@...e.de>
To:	Jon Mason <jdmason@...zu.us>
Cc:	linux-kernel@...r.kernel.org, kautzy@...tzy.com
Subject: Re: Dual Core Opteron hangs, iommu Entries (x86_64)

Jon Mason <jdmason@...zu.us> writes:
> 
> Your problem is that you have more than 4GB of RAM and not enough room
> in your IOMMU aperature to handle all of the pending DMA requests.
> Dmesg suggests you go into your BIOS and increase your AGP aperature
> from 32M to 64M, did you try that?  

The kernel ignores 32MB apertures anyways and creates its own 64MB aperture.

Normally IOMMU overflow should be handled without a hang though, assuming
you don't have a buggy driver. If you don't trust it you can
boot with iommu=panic panic=30 -- then the kernel will always panic
and reboot when this happens. The aperture can be also increased
with iommu=memaper=3 or 4

But it could be a lot of other things. So far you don't seem to have
any evidence that it's the IOMMU except for some likely misguided googling.

The usual way to check for unknown hangs is to just configure
serial console and see if there is some output during the hang.

Also do a memtest86 for at least 12hours.

-Andi

-
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/