[lkml]   [2011]   [Nov]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: iwlagn: memory corruption with WPA enterprise
Hello Stanislaw,

On Mon, Oct 31, 2011 at 05:03:43PM +0100, Stanislaw Gruszka wrote:
> You may try debugging patches I posted a while ago:
> With a bit of luck, kernel should panic and dump call-trace when
> bad code start to write at memory addresses where is not suppose
> to.

Thanks for your suggestions. I did as you told me, applied those 3 patches on
top of 3.1 + net-next (the one from 29 Oct 2011), enabled all those things in
config and passed corrupt_dbg=1 on cmdline, but the problem happens without
anything being written to dmesg.

Am I just lacking a bit of luck, or could it mean something (like that the
error is in hardware, the microcode, or something like that)?

Tomáš Janoušek, a.k.a. Liskni_si,
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2011-11-09 16:57    [W:0.067 / U:0.060 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site