From: Johannes Berg <johannes@sipsolutions.net>
To: Wolfgang Breyha <wbreyha@gmx.net>
Cc: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi havoc on some APs (rekeying?)
Date: Tue, 13 Dec 2011 16:38:08 +0100 [thread overview]
Message-ID: <1323790688.3355.24.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4EE64522.5090107@gmx.net> (sfid-20111212_191739_160874_7027323F)
On Mon, 2011-12-12 at 19:17 +0100, Wolfgang Breyha wrote:
> On 2011-12-12 18:48, Johannes Berg wrote:
> > A colleague pointed out that due to the PCI address space hold we might
> > be seeing larger addresses -- could you try booting the 32 bit kernel
> > with "mem=3G" on the command line (edit it in grub maybe?) and see if
> > you can still reproduce it then?
>
> mem=3G changes nothing except the amount of memory;-) Exactly the same
> issues occur.
Hm, unfortunately, I can't reproduce this problem, even with 2 minute
GTK rekey intervals. Could you run this program on your machine while
you reproduce it?
http://johannes.sipsolutions.net/files/mc.c.txt
(just save as "mc.c" and compile with gcc mc.c -o mc)
The program will allocate 2GiB memory (edit to suit, should be OK on
your machine), fill them with 0x94 and then continually scan them for
corruption. Identifying what kind of corruption happened will hopefully
allow me to figure out where it's coming from.
It prints out the wrong data & resets the memory so new corruption later
is also identified.
Thanks!
johannes
next prev parent reply other threads:[~2011-12-13 15:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 14:50 iwlwifi havoc on some APs (rekeying?) Wolfgang Breyha
2011-12-09 16:02 ` Guy, Wey-Yi
2011-12-09 18:05 ` Wolfgang Breyha
2011-12-09 17:23 ` Guy, Wey-Yi
2011-12-09 18:26 ` Johannes Berg
2011-12-09 17:44 ` Guy, Wey-Yi
2011-12-10 13:02 ` Wolfgang Breyha
2011-12-12 9:04 ` Johannes Berg
2011-12-12 10:09 ` Wolfgang Breyha
2011-12-12 10:12 ` Johannes Berg
2011-12-12 11:21 ` Wolfgang Breyha
2011-12-12 17:48 ` Johannes Berg
2011-12-12 18:17 ` Wolfgang Breyha
2011-12-13 15:38 ` Johannes Berg [this message]
2011-12-14 14:22 ` Wolfgang Breyha
2011-12-14 22:10 ` Johannes Berg
2011-12-14 22:51 ` Daniel Halperin
2011-12-14 22:55 ` Johannes Berg
2011-12-14 23:07 ` Wolfgang Breyha
2011-12-15 0:46 ` Wolfgang Breyha
2011-12-15 13:01 ` Johannes Berg
2011-12-15 19:47 ` Wolfgang Breyha
2011-12-12 19:39 ` Wolfgang Breyha
2012-02-18 13:09 ` Johannes Berg
2012-02-24 7:25 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1323790688.3355.24.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wbreyha@gmx.net \
--cc=wey-yi.w.guy@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).