linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: "Tomáš Janoušek" <tomi@nomi.cz>
Cc: linux-kernel@vger.kernel.org, Wey-Yi Guy <wey-yi.w.guy@intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: iwlagn: memory corruption with WPA enterprise
Date: Thu, 10 Nov 2011 17:07:04 +0100	[thread overview]
Message-ID: <20111110160703.GA2775@redhat.com> (raw)
In-Reply-To: <20111110125347.GA29415@nomi.cz>

On Thu, Nov 10, 2011 at 01:53:47PM +0100, Tomáš Janoušek wrote:
> > If "dmesg | grep corrupt" will show "Setting corrupt debug order to 1"
> > patches are in use. Anyway I need to test the patches locally, to see
> > if they work as expected, perhaps exception is generated but call-trace
> > is not printed.
> 
> It does say that, yes.

I tested patches. They generate call-trace and make kernel panic when I
wrote at random address from user address space. However to make kernel
panic, we should keep as much as possible free memory, otherwise bad code
corrupt not-protected data. In other words, when you run memory intensive
application, corruption may happen on valid data.  So to catch the bug,
you should just use network, and perhaps stress up cpu i.e: by this bash
command:

while true; do : ; done 

Please also configure CONFIG_DEBUG_SET_MODULE_RONX=y, it protect modules
text/read-only memory against corruption.

> > Is this happen only with "Intel Corporation Centrino Advanced-N 6205" or
> > with some other adapters?
> 
> I don't have any other iwlwifi adapters, so I wouldn't know. The people in
> that Ubuntu bugreport have exactly that card as well, but in another notebook.
> And they claim it works in newer Ubuntu, but I am running latest kernels with
> latest uCode, so I'm out of ideas what else could be wrong.

That's good hint for Intel folks. Would be ideal if any developer could
reproduce that. I do not have this exact adapter model.

> > > Perhaps it would be cheaper to just get another card in that case.
> > > :-)
> >
> > That will left issue unresolved :-(
> 
> Yeah, but considering how few people report this, I'm starting to feel that it
> might in fact be a hardware issue.

It's possible, but I don think so. In my practice, majority of corruption
problems was caused by software. All true hardware corruptions I meet, was on
development boards, many months before they went into production.

> (We've got a lot of Lenovos here, mostly T520 and T420s, most of them running
> Fedora, and nobody has reported memory corruption problems.

Are there any others with 6205? If not that would confirm issue is
related with that model.

> Perhaps I should try to connect to this WPA Enterprise using Windows and see
> if anything goes wrong. However, I have no clue as to what shall I do to
> reproduce the issue in Windows.)

You may first try some older kernel as Wey suggested, i.e. 2.6.38.

Thanks
Stanislaw

  reply	other threads:[~2011-11-10 16:06 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29 17:15 iwlagn: memory corruption with WPA enterprise 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 [this message]
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
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=20111110160703.GA2775@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomi@nomi.cz \
    --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).