linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Backlund <tmb@mandriva.org>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Ian Schram <ischram@telenet.be>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwl4965 oops in 2.6.26-rc5 x86_64
Date: Fri, 06 Jun 2008 15:01:56 +0300	[thread overview]
Message-ID: <48492734.9080901@mandriva.org> (raw)
In-Reply-To: <1ba2fa240806060432t73ecb318x89e877241aa6ef55@mail.gmail.com>

Tomas Winkler skrev:
> On Fri, Jun 6, 2008 at 3:44 AM, Ian Schram <ischram@telenet.be> wrote:
>> Isn't this the Oops Joonwoo Park wanted to patch with
>>
>> "[PATCH] iwlwifi: fix oops on wep key insertion" 27/5/2008
>>
>> invalid length of webkey that would/should be handled in mac80211?
>>
>> ian
> 
> Yes, it looks like.

Ummm, what has a wep key to do with me trying to access a WPA2-Personal 
encrypted net ?

> Thomas can you send out your wpa_supplicant config fiele
> 

I could, but since I would have to remove any sensitive info such as the 
psk key, would it be of any use ?

> I will provide a patch that disable hw encryption on long wep keys. It
> get lost in my todo list.
> Tomas
> 

--
Thomas

  reply	other threads:[~2008-06-06 12:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 17:55 iwl4965 oops in 2.6.25-rc5 x86_64 Thomas Backlund
2008-06-05 18:03 ` Tomas Winkler
2008-06-05 18:09   ` Thomas Backlund
2008-06-05 20:10     ` Thomas Backlund
2008-06-05 21:48       ` iwl4965 oops in 2.6.26-rc5 x86_64 Thomas Backlund
2008-06-06  0:44         ` Ian Schram
2008-06-06 11:32           ` Tomas Winkler
2008-06-06 12:01             ` Thomas Backlund [this message]
2008-06-06 12:33               ` Thomas Backlund
2008-06-06 13:59                 ` Tomas Winkler
2008-06-06 14:29                   ` Dan Williams
2008-06-06 14:48                     ` Thomas Backlund
2008-06-06 14:51                   ` Thomas Backlund
2008-06-06 15:12                     ` Tomas Winkler
2008-06-06 15:22                       ` Dan Williams
2008-06-06 15:57                         ` Thomas Backlund
2008-06-06 16:04                           ` Dan Williams
2008-06-06 21:43                       ` Thomas Backlund
2008-06-06 23:59                         ` Tomas Winkler
2008-06-07 13:28                           ` Thomas Backlund
2008-06-08 10:27                             ` Tomas Winkler
2008-06-08 12:21                               ` Thomas Backlund
2008-06-08 15:31                                 ` Tomas Winkler
2008-06-08 20:07                                   ` Thomas Backlund
2008-06-09 15:55                                   ` Dan Williams
2008-06-09 16:43                                     ` Tomas Winkler
2008-06-09 16:54                                       ` Dan Williams
2008-06-10 14:48         ` QUESTIONS to ieee80211_beacon_get AND ieee80211_get_buffered_bc Joe
2008-06-10 14:58           ` Johannes Berg
2008-06-10 14:58           ` Johannes Berg
     [not found]             ` <484E9B84.1070902@gmx.de>
2008-06-10 15:46               ` [english 87%] " Johannes Berg
2008-06-10 15:34           ` [english 95%] " Joe
2008-06-10 15:40             ` 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=48492734.9080901@mandriva.org \
    --to=tmb@mandriva.org \
    --cc=ischram@telenet.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@gmail.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).