Re: iwlagn: memory corruption with WPA enterprise

On Mon, Nov 21, 2011 at 02:09:16PM +0100, Tomáš Janoušek wrote:

On Mon, Nov 21, 2011 at 02:05:28PM +0100, Stanislaw Gruszka wrote:

quoted

The farther we get the problem is more and more strange.

Device that write to wrong address, would generate:

DMAR:[DMA Write] Request device [00:02.0] fault addr 6df084000
DMAR:[fault reason 05] PTE Write access is not set

And that's exactly what happens if I don't disable firewire-ohci, because of
that stupid Ricoh multifunction blah blah issue.

So maybe problem is caused by Ricoh, not by iwlagn. But if so 
why blacklisting iwlagn help? Wired. Did you disable firewire in
BIOS, or just blacklist module?

quoted

Try "dmesg | grep DMAR" to see if DMA remapping is really is
in use. 

Well, this message is not printed, but as I said, loading firewire-ohci
triggers DMAR faults, so it should be in use anyway.

So IOMMU is in use and it does not prevent corruption, crap.

Ok maybe let's try to find some better reproducer first.
I wrote simple program that fill memory with some pattern, and
then check every one second if pattern is still there.
It can be used like:
./checkmem 100M 30M
where first argument is size of memory it will alloc and check,
second specify number of internal loops to make cpu busy (bigger
value will cause more cpu power consumption). Many instances of
the program can be running at once.

Tomáš, please try to reproduce with that program, I'm attaching
it. When corruption will be detected, checkmem will print invalid
values, maybe would be possible to find out what contents is
written to memory.

Stanislaw