From: "Tomáš Janoušek" <tomi@nomi.cz>
To: wwguy <wey-yi.w.guy@intel.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: memory corruption with WPA enterprise
Date: Sun, 20 Nov 2011 21:40:07 +0100 [thread overview]
Message-ID: <20111120204007.GA7273@nomi.cz> (raw)
In-Reply-To: <1321763314.22510.4.camel@wwguy-ubuntu>
Hi,
On Sat, Nov 19, 2011 at 08:28:34PM -0800, wwguy wrote:
> On Sat, 2011-11-19 at 19:20 -0800, Tomáš Janoušek wrote:
> > Anyway, did you have time to try to reproduce it with the .config I sent?
> > (It may take hours, sometimes. :-/)
>
> Yes, I will try your configuration when I get back to the office Monday
Okay, thank you. I managed to test 2.6.38.8 and 2.6.39.4 today and the issue
is reproducible on both. Shall I test further in the past?
I also got a reply from the Ubuntu bugreport where someone claims he doesn't
experience the issue on current 32-bit Ubuntu 11.10, even though he did
experience it in older versions. I have no idea why that may be so, as they
have the same firmware as I have, and the kernel is 3.0 with almost no
modifications to the iwlagn driver.
I hope that you'll be able to reproduce the issue and fix it. Sadly, I still
haven't got a better reproducer. What I was doing today was running make clean
&& make -j4 in a while loop, having an active Skype videocall and browsing the
web while waiting for it to crash. Sometimes it took a few minutes, sometimes
more than an hour.
Regards,
--
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/
next prev parent reply other threads:[~2011-11-20 20:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 17:15 Tomáš Janoušek
2011-10-31 16:03 ` Stanislaw Gruszka
2011-11-09 15:54 ` Tomáš Janoušek
2011-11-09 15:59 ` wwguy
2011-11-09 16:51 ` Stanislaw Gruszka
2011-11-10 9:18 ` Tomáš Janoušek
2011-11-10 11:47 ` Stanislaw Gruszka
2011-11-10 12:53 ` Tomáš Janoušek
2011-11-10 16:07 ` Stanislaw Gruszka
2011-11-10 15:24 ` Guy, Wey-Yi
2011-11-10 16:42 ` Tomáš Janoušek
2011-11-10 17:02 ` Larry Finger
2011-11-10 16:30 ` Tomáš Janoušek
2011-11-11 5:47 ` Stanislaw Gruszka
2011-11-11 15:01 ` Tomáš Janoušek
2011-11-14 14:07 ` Stanislaw Gruszka
2011-11-19 18:11 ` Tomáš Janoušek
2011-11-20 2:13 ` wwguy
2011-11-20 3:20 ` Tomáš Janoušek
2011-11-20 4:28 ` wwguy
2011-11-20 20:40 ` Tomáš Janoušek [this message]
2012-02-10 18:09 ` Tomáš Janoušek
2012-02-13 9:25 ` Stanislaw Gruszka
2012-02-13 13:09 ` Stanislaw Gruszka
2012-02-13 13:29 ` Tomáš Janoušek
2012-02-14 9:20 ` Stanislaw Gruszka
2012-03-05 14:01 ` Tomáš Janoušek
2012-03-05 14:57 ` Stanislaw Gruszka
2012-03-05 15:00 ` Tomáš Janoušek
2012-03-05 15:11 ` Stanislaw Gruszka
2012-03-05 15:18 ` Tomáš Janoušek
2011-11-21 13:05 ` Stanislaw Gruszka
2011-11-21 13:09 ` Tomáš Janoušek
2011-11-21 13:40 ` Stanislaw Gruszka
2011-11-21 14:32 ` Tomáš Janoušek
2011-11-10 19:31 ` Adrian Chadd
2011-11-11 5:44 ` Stanislaw Gruszka
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=20111120204007.GA7273@nomi.cz \
--to=tomi@nomi.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.com \
--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
all inboxes | Powered by JetHome®