Re: iwlagn: memory corruption with WPA enterprise

[Stanislaw Gruszka <sgruszka@redhat.com>]

On Fri, Feb 10, 2012 at 07:09:29PM +0100, Tomáš Janoušek wrote:
> On Sun, Nov 20, 2011 at 09:40:07PM +0100, Tomáš Janoušek wrote:
> > > Yes, I will try your configuration when I get back  to the office Monday
> 
> Did you have any luck?
I think I tried to reproduce that problem and failed, but honestly I do
not remember right now ...

> I just found out something which is almost completely
> insane.
> 
> For the last few months, I've happily used a 64-bit kernel and have had no
> problems whatsoever. About a week ago, I started using virtual machines in
> KVM. And today I found that I have exactly the same problem, but only _inside_
> the virtual machine. I can't reliably scp a file from the internet to my
> virtual machine. It works fine when I scp to the host, it works fine when I'm
> on a WPA-PSK network. And it happens even if I tell kvm to emulate e1000, not
> only with virtio-net. How strange is that?
>
> And while this is happening, the host is running just fine. The host has a
> 64-bit kernel with a 32-bit userspace, so if something was wrong with the
> 32-bit mode of my processor, it would've appeared on the host as well, no?
> 
> It's also worth mentioning that if I build openssl with "no-asm 386", scp
> works just fine. So it doesn't look like a memory corruption after all. It
> seems as if certain CPU instructions didn't work properly if running on a
> 32-bit kernel with a WiFi adapter doing something. But how can it be
> that those same CPU instructions work on a 64-bit host with 32-bit userspace?
> At the same time! That's just completely insane, and I can't think of an
> explanation. Shall I get a new CPU perhaps? :-)

Currently there are discussion about compilator problems that
can result a corruption
http://lwn.net/Articles/478657/
Perhaps this problem is something similar.

Also, if you look at lspci -vt, does it show that corruption happen
only  when PCI bridge is used (however that would not explain why it
only happens with WPA enterprise).

Stanislaw