Re: iwlagn broken in next-20090514 and next-20090515

Re: iwlagn broken in next-20090514 and next-20090515

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]

Add cc's

On Fri, 15 May 2009 12:26:21 +0200 Nico -telmich- Schottelius <nico-linux-next@schottelius.org> wrote:
>
> Kernel is not authenticating it against the AP anymore with
> messages like:
> 
> [16907.701634] wlan0: associate with AP 00:03:52:4e:f3:d1
> [16907.703669] wlan0: RX AssocResp from 00:03:52:4e:f3:d1 (capab=0x421 status=0 aid=5)
> [16907.703672] wlan0: associated
> [16907.729958] wlan0: disassociating by local choice (reason=3)
> [16907.852112] wlan0: direct probe to AP 00:03:52:1b:f8:31 try 1
> [16908.052086] wlan0: direct probe to AP 00:03:52:1b:f8:31 try 2
> [16908.055331] wlan0 direct probe responded
> [16908.055335] wlan0: authenticate with AP 00:03:52:1b:f8:31
> [16908.256065] wlan0: authenticate with AP 00:03:52:1b:f8:31
> [16908.453689] wlan0: authenticate with AP 00:03:52:1b:f8:31
> [16908.656037] wlan0: authentication with AP 00:03:52:1b:f8:31 timed out
> 
> Also wpa_supplicant is not happy:
> 
> + wpa_supplicant -B -Dwext -iwlan0 -c /home/user/nico/ethz/wlan/wpa_supplicant.conf
> ioctl[SIOCSIWENCODEEXT]: No such file or directory
> ioctl[SIOCSIWENCODEEXT]: No such file or directory
> ioctl[SIOCSIWENCODEEXT]: No such file or directory
> ioctl[SIOCSIWENCODEEXT]: No such file or directory
> 
> 
> Config, dmesg attached.
> 
> Last working kernel version: vmlinuz-2.6.30-rc4-next-20090505-04518-g1f9c23a
> 
> Nico

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: dmesg.2.6.30-rc5-next-20090515-05297-g9bbe396 --]
[-- Type: application/octet-stream, Size: 60426 bytes --]

[-- Attachment #3: config.gz --]
[-- Type: application/octet-stream, Size: 22099 bytes --]

Re: iwlagn broken in next-20090514 and next-20090515

[reinette chatre]

On Mon, 2009-05-18 at 00:15 -0700, Stephen Rothwell wrote:
> Add cc's
> 
> On Fri, 15 May 2009 12:26:21 +0200 Nico -telmich- Schottelius <nico-linux-next@schottelius.org> wrote:
> >
> > Kernel is not authenticating it against the AP anymore with
> > messages like:
> > 
> > [16907.701634] wlan0: associate with AP 00:03:52:4e:f3:d1
> > [16907.703669] wlan0: RX AssocResp from 00:03:52:4e:f3:d1 (capab=0x421 status=0 aid=5)
> > [16907.703672] wlan0: associated
> > [16907.729958] wlan0: disassociating by local choice (reason=3)

This is usually printed when your user application (wpa_supplicant,
network manager, etc.) goes down or disassociates.

> > [16907.852112] wlan0: direct probe to AP 00:03:52:1b:f8:31 try 1
> > [16908.052086] wlan0: direct probe to AP 00:03:52:1b:f8:31 try 2
> > [16908.055331] wlan0 direct probe responded
> > [16908.055335] wlan0: authenticate with AP 00:03:52:1b:f8:31
> > [16908.256065] wlan0: authenticate with AP 00:03:52:1b:f8:31
> > [16908.453689] wlan0: authenticate with AP 00:03:52:1b:f8:31
> > [16908.656037] wlan0: authentication with AP 00:03:52:1b:f8:31 timed out

Don't know what is going on here. Could your AP be out of reach or not
responding?

> > 
> > Also wpa_supplicant is not happy:
> > 
> > + wpa_supplicant -B -Dwext -iwlan0 -c /home/user/nico/ethz/wlan/wpa_supplicant.conf
> > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > 

There were some changes recently to this ioctl, but I am not familiar
with details. Johannes will know.

Reinette

Re: iwlagn broken in next-20090514 and next-20090515

[Dan Williams]

On Mon, 2009-05-18 at 09:03 -0700, reinette chatre wrote:
> On Mon, 2009-05-18 at 00:15 -0700, Stephen Rothwell wrote:
> > Add cc's
> > 
> > On Fri, 15 May 2009 12:26:21 +0200 Nico -telmich- Schottelius <nico-linux-next@schottelius.org> wrote:
> > >
> > > Kernel is not authenticating it against the AP anymore with
> > > messages like:
> > > 
> > > [16907.701634] wlan0: associate with AP 00:03:52:4e:f3:d1
> > > [16907.703669] wlan0: RX AssocResp from 00:03:52:4e:f3:d1 (capab=0x421 status=0 aid=5)
> > > [16907.703672] wlan0: associated
> > > [16907.729958] wlan0: disassociating by local choice (reason=3)
> 
> This is usually printed when your user application (wpa_supplicant,
> network manager, etc.) goes down or disassociates.

Yeah, this is normal and indicates that the supplicant called
SIOCGIWMLME, which could either be triggered internally by the
supplicant, or even more likely, because NetworkManager requests that
the supplicant disconnects nicely before switching networks or taking
the connection down.

Dan

> > > [16907.852112] wlan0: direct probe to AP 00:03:52:1b:f8:31 try 1
> > > [16908.052086] wlan0: direct probe to AP 00:03:52:1b:f8:31 try 2
> > > [16908.055331] wlan0 direct probe responded
> > > [16908.055335] wlan0: authenticate with AP 00:03:52:1b:f8:31
> > > [16908.256065] wlan0: authenticate with AP 00:03:52:1b:f8:31
> > > [16908.453689] wlan0: authenticate with AP 00:03:52:1b:f8:31
> > > [16908.656037] wlan0: authentication with AP 00:03:52:1b:f8:31 timed out
> 
> Don't know what is going on here. Could your AP be out of reach or not
> responding?
> 
> > > 
> > > Also wpa_supplicant is not happy:
> > > 
> > > + wpa_supplicant -B -Dwext -iwlan0 -c /home/user/nico/ethz/wlan/wpa_supplicant.conf
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > 
> 
> There were some changes recently to this ioctl, but I am not familiar
> with details. Johannes will know.
> 
> Reinette
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: iwlagn broken in next-20090514 and next-20090515

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 707 bytes --]

On Mon, 2009-05-18 at 09:03 -0700, reinette chatre wrote:

> > > Also wpa_supplicant is not happy:
> > > 
> > > + wpa_supplicant -B -Dwext -iwlan0 -c /home/user/nico/ethz/wlan/wpa_supplicant.conf
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > 
> 
> There were some changes recently to this ioctl, but I am not familiar
> with details. Johannes will know.

Yeah, I'm not sure -- this happens when clearing keys. I'll look into
it, we probably need to accept removing a key that doesn't exist.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: iwlagn broken in next-20090514 and next-20090515

[Dan Williams]

On Mon, 2009-05-18 at 18:24 +0200, Johannes Berg wrote:
> On Mon, 2009-05-18 at 09:03 -0700, reinette chatre wrote:
> 
> > > > Also wpa_supplicant is not happy:
> > > > 
> > > > + wpa_supplicant -B -Dwext -iwlan0 -c /home/user/nico/ethz/wlan/wpa_supplicant.conf
> > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > 
> > 
> > There were some changes recently to this ioctl, but I am not familiar
> > with details. Johannes will know.
> 
> Yeah, I'm not sure -- this happens when clearing keys. I'll look into
> it, we probably need to accept removing a key that doesn't exist.

Why bother (if that's actually the root cause)?  Maybe the supplicant
should be fixed.  Other drivers return ENOENT in this case, so mac80211
certainly isn't out-of-common-spec here now.

Dan

Re: iwlagn broken in next-20090514 and next-20090515

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

On Mon, 2009-05-18 at 13:50 -0400, Dan Williams wrote:

> > > > > Also wpa_supplicant is not happy:
> > > > > 
> > > > > + wpa_supplicant -B -Dwext -iwlan0 -c /home/user/nico/ethz/wlan/wpa_supplicant.conf
> > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > 
> > > 
> > > There were some changes recently to this ioctl, but I am not familiar
> > > with details. Johannes will know.
> > 
> > Yeah, I'm not sure -- this happens when clearing keys. I'll look into
> > it, we probably need to accept removing a key that doesn't exist.
> 
> Why bother (if that's actually the root cause)?  Maybe the supplicant
> should be fixed.  Other drivers return ENOENT in this case, so mac80211
> certainly isn't out-of-common-spec here now.

I just looked at the code in wpa_supplicant, it doesn't care a bit, just
prints the error. Problem is users attribute any other breakage to the
error it prints since our behaviour changed...

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: iwlagn broken in next-20090514 and next-20090515

[Dan Williams]

On Mon, 2009-05-18 at 20:10 +0200, Johannes Berg wrote:
> On Mon, 2009-05-18 at 13:50 -0400, Dan Williams wrote:
> 
> > > > > > Also wpa_supplicant is not happy:
> > > > > > 
> > > > > > + wpa_supplicant -B -Dwext -iwlan0 -c /home/user/nico/ethz/wlan/wpa_supplicant.conf
> > > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > > 
> > > > 
> > > > There were some changes recently to this ioctl, but I am not familiar
> > > > with details. Johannes will know.
> > > 
> > > Yeah, I'm not sure -- this happens when clearing keys. I'll look into
> > > it, we probably need to accept removing a key that doesn't exist.
> > 
> > Why bother (if that's actually the root cause)?  Maybe the supplicant
> > should be fixed.  Other drivers return ENOENT in this case, so mac80211
> > certainly isn't out-of-common-spec here now.
> 
> I just looked at the code in wpa_supplicant, it doesn't care a bit, just
> prints the error. Problem is users attribute any other breakage to the
> error it prints since our behaviour changed...

I meant "make wpa_supplicant not print anything out on -ENOENT".

Dan