linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jouni Malinen <jouni.malinen@atheros.com>,
	wireless <linux-wireless@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	John Linville <linville@tuxdriver.com>
Subject: Re: Regression in 2.6.27-git from commit 43ac2ca3840f64
Date: Tue, 21 Oct 2008 19:34:37 -0700	[thread overview]
Message-ID: <48FE913D.9060205@lwfinger.net> (raw)
In-Reply-To: <1224624636.28639.15.camel@johannes.berg>

Johannes Berg wrote:
> On Tue, 2008-10-21 at 09:01 -0700, Larry Finger wrote:
>> On my x86_64 system, the mainline 2.6.27-git kernel (v2.6.27-6030-g6da0b38)
>> shows the following anomaly with the 'iwlist scan' command:
>>
>>           Cell 03 - Address: 00:14:BF:85:49:FA
>>                     ESSID:"lwfdjf"
>>                     Mode:Master
>>                     Channel:1
>>                     Frequency:2.412 GHz (Channel 1)
>>                     Quality=66/100  Signal level:-62 dBm  Noise level=-68 dBm
>>                     Encryption key:on
>>                     IE: Unknown: 00066C7766646A66
>>                     IE: Unknown: 010882848B962430486C
>>                     IE: Unknown: 030101
>>                     IE: Unknown: 2A0104
>>                     IE: Unknown: 2F0104
>>                     IE: Unknown: 32040C121860
>>                     IE: Unknown: DD09001018020014000000
>>                     IE: WPA Version 1
>>                         Group Cipher : TKIP
>>                         Pairwise Ciphers (1) : TKIP
>>                         Authentication Suites (1) : PSK
>>                     Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
>>                               24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
>>                               12 Mb/s; 48 Mb/s
>>                     Extra:tsf=0000014488aeb18b
>>                     Extra: Last beacon: 448ms ago
>>
>> This problem was bisected to commit 43ac2ca3840f64f699a239535c590fa7ebaaac27,
>> entitled "mac80211: Handle scan result IEs in one block". The same bug is
>> present in the wireless-testing tree.
> 
> I'm probably too tired, what exactly is the problem?

The unknown IE's don't show up before this commit.

Larry

  reply	other threads:[~2008-10-22  2:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21 16:01 Regression in 2.6.27-git from commit 43ac2ca3840f64 Larry Finger
2008-10-21 21:30 ` Johannes Berg
2008-10-22  2:34   ` Larry Finger [this message]
2008-10-22  7:23     ` Johannes Berg
2008-10-21 21:37 ` John W. Linville
2008-10-22  2:45   ` Larry Finger
2008-10-22  7:28 ` Jouni Malinen
2008-10-22 16:47   ` Larry Finger
2008-10-22 17:04     ` Jouni Malinen
2008-10-22 17:06     ` Johannes Berg
2008-10-22 17:37       ` Jean Tourrilhes
2008-10-22 17:46         ` Johannes Berg
2008-10-22 18:00           ` Jean Tourrilhes

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=48FE913D.9060205@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=johannes@sipsolutions.net \
    --cc=jouni.malinen@atheros.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).