public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Nico -telmich- Schottelius <nico-linux-next@schottelius.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	johannes@sipsolutions.net
Subject: Re: iwlagn broken in next-20090514 and next-20090515
Date: Mon, 18 May 2009 09:03:55 -0700	[thread overview]
Message-ID: <1242662635.32358.523.camel@rc-desk> (raw)
In-Reply-To: <20090518171505.d30d2f64.sfr@canb.auug.org.au>

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


  reply	other threads:[~2009-05-18 15:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15  5:37 linux-next: Tree for May 15 Stephen Rothwell
2009-05-15 10:26 ` iwlagn broken in next-20090514 and next-20090514 Nico -telmich- Schottelius
2009-05-18  7:15   ` iwlagn broken in next-20090514 and next-20090515 Stephen Rothwell
2009-05-18 16:03     ` reinette chatre [this message]
2009-05-18 16:16       ` Dan Williams
2009-05-18 16:24       ` Johannes Berg
2009-05-18 17:50         ` Dan Williams
2009-05-18 18:10           ` Johannes Berg
2009-05-18 18:35             ` Dan Williams
2009-05-15 13:07 ` linux-next: Tree for May 15 Borislav Petkov
2009-05-17 14:07   ` Stephen Rothwell
2009-05-18  9:48     ` Borislav Petkov
2009-05-18 23:36       ` Stephen Rothwell

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=1242662635.32358.523.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nico-linux-next@schottelius.org \
    --cc=sfr@canb.auug.org.au \
    /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