From: "Tomáš Janoušek" <tomi@nomi.cz>
To: Stanislaw Gruszka <sgruszka@redhat.com>
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: Fri, 11 Nov 2011 16:01:05 +0100 [thread overview]
Message-ID: <20111111150105.GA25437@nomi.cz> (raw)
In-Reply-To: <20111111054731.GA2292@redhat.com>
Hello,
On Fri, Nov 11, 2011 at 06:47:31AM +0100, Stanislaw Gruszka wrote:
> On Thu, Nov 10, 2011 at 05:30:51PM +0100, Tomáš Janoušek wrote:
> > I think all those T520 and T420s models have exactly the same wireless card. I
> > don't see why they wouldn't have. :-)
>
> Well, laptops models have common mainboards, but peripheral components
> might not be identical. Especially wireless card might vary from unit
> to unit. For example:
>
> T520 with iwl6300:
> http://smolt.fedoraproject.org/client/show/pub_0cbc8731-47d3-4ecf-8add-aa832b34edcd
> T520 with iwl1000:
> http://smolt.fedoraproject.org/client/show/pub_02f601d6-7a93-4c0e-bc01-a4a95db36086
> T520 with iwl6205:
> http://smolt.fedoraproject.org/client/show/pub_0232252f-75a9-4050-a69b-c8e95e00eaf2
These links don't work, but my colleagues indeed do have iwl6205. They are,
however, running 64-bit kernels, so I tried doing the same and I haven't been
able to reproduce the issue for the past few hours. So it seems like it
happens on 32-bit kernels only. This looks like a good workaround (better than
getting a different wireless card), so I can run 64-bit during working days
and experiment with 32-bit when I have time to debug this.
Could you please elaborate on that thing with enabling IOMMU? The only thing I
know about IOMMU is that it is somehow related to VT-d (passing whole PCI
devices to virtual guests), and that I have to pass intel_iommu=off to kernel
command line, otherwise the machine doesn't even boot. Is that a problem?
Kind regards,
--
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/
next prev parent reply other threads:[~2011-11-11 15:01 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
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 [this message]
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=20111111150105.GA25437@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;
as well as URLs for NNTP newsgroup(s).