All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Breyha <wbreyha@gmx.net>
To: Johannes Berg <johannes@sipsolutions.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: Wed, 14 Dec 2011 15:22:36 +0100	[thread overview]
Message-ID: <4EE8B12C.4090906@gmx.net> (raw)
In-Reply-To: <1323790688.3355.24.camel@jlt3.sipsolutions.net>

Johannes Berg wrote, on 13.12.2011 16:38:
> 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.

Ok, I had only 20 minutes yesterday evening, but the results are not very
pleasant, because there are no results:(

I did the usual steps to reproduce the case on my laptop:

*) stay connected on the "working" AP (no rekeying)
--> *) new here: start "mc"
*) echo "1" >...iwlwifi/debug
*) open multitail, firefox, vlc
*) connect to the other AP (rekeying every 20 seconds currently)
*) start video stream
*) wait for the second "group rekey finished"
*) watch the artifacts, closing applications and listen to crackling sound

Everything happened exactly the same way as always. BUT "mc" didn't show any
corrupted memory regions.

I already tried to remember which applications crashed, but currently I'm not
able to give them a clear category like "all (network-)IO" or "all
audio/video". Allocating memory seems not to be enough to trigger "something".
<brainstorm mode>Maybe mmap'ed regions are affected?</brainstorm mode>

Watching a video is only one way to notice that issue. Simply starting firefox
with a group of tabs open is an other and has a high probability to
immediately crash firefox while fetching the contents.

Watching a video shows the coincidence with the second rekeying event best.

I'll try to give "mc" some more time and start it after/before the others as
soon as my pre-x-mas schedule allows it.

Greetings, Wolfgang
-- 
Wolfgang Breyha <wbreyha@gmx.net> | http://www.blafasel.at/
Vienna University Computer Center | Austria

  reply	other threads:[~2011-12-14 14:22 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
2011-12-14 14:22                         ` Wolfgang Breyha [this message]
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=4EE8B12C.4090906@gmx.net \
    --to=wbreyha@gmx.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.