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: Thu, 15 Dec 2011 01:46:55 +0100 [thread overview]
Message-ID: <4EE9437F.1060500@gmx.net> (raw)
In-Reply-To: <1323903308.3599.8.camel@jlt3.sipsolutions.net>
On 14/12/11 23:55, Johannes Berg wrote:
> I wish I could reproduce it, maybe it would be possible to bisect?
I was able to build and test the following releases of compat-wireless:
compat-wireless-2011-10-12
compat-wireless-2011-09-27
compat-wireless-2011-08-27
compat-wireless-2011-08-26
All are affected in the same way. 2011-10-12 gave me a hard system
freeze without output to messages. Most likely the "worst case scenario"
of the issue.
compat-wireless-2011-08-23 and some older releases I tried do not build
on F16 3.1.4.
IIRC 2011-03-25 was the release I used with F14.
Greetings, Wolfgang
next prev parent reply other threads:[~2011-12-15 0:46 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
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 [this message]
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=4EE9437F.1060500@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.