linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Randolf <br1@einfach.org>
To: sedat.dilek@gmail.com
Cc: wireless <linux-wireless@vger.kernel.org>,
	John Linville <linville@tuxdriver.com>,
	Nick Kossifidis <mickflemm@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [linux-next] next-20101201: ath5k permanently disconnecting
Date: Wed, 1 Dec 2010 19:21:11 +0900	[thread overview]
Message-ID: <201012011921.11151.br1@einfach.org> (raw)
In-Reply-To: <AANLkTi=_F0orXPY79ojoPKEqn4ohQjV5Rj5Qb3H7CR8f@mail.gmail.com>

On Wed December 1 2010 19:09:03 Sedat Dilek wrote:
> Hi,
> 
> I have built today a linux-next (next-20101201) kernel which includes
> wireless-next-2.6 up to master-2010-11-30.
> 
> >From tig utility:
> 2010-11-30 15:33 Stanislaw Gruszka  [wireless-next-2.6] iwlagn: fix
> microcode error on 4965
> [main] 61790c5f3c5f158821821a00797d94504531839f - commit 1929 of 226338
> (0%)
> 
> Unfortunately, my wlan network connection is totally unstable.
> 
> $ dmesg | grep "RX AssocResp" | wc -l
> 216
> 
> The block looks like this:
> [ 4436.504059] ieee80211 phy0: wlan0: No probe response from AP
> 00:04:0e:e4:00:3d after 500ms, disconnecting.
> [ 4436.504490] cfg80211: Calling CRDA to update world regulatory domain
> [ 4440.677020] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
> [ 4440.679096] wlan0: authenticated
> [ 4440.679158] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
> [ 4440.684667] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411
> status=0 aid=1)
> [ 4440.684673] wlan0: associated
> 
> My wlan device is an ath5k:
> 
> $ lspci -nnvv | grep "Ethernet controller" | grep -i ath
> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
> 802.11abg NIC [168c:1014] (rev 01)
> 
> Any idea what's wrong? (Just speculating on the last patch-set from
> Nick...) How can I help to dig into this problem?
> Debug-session with wpasupplicant? Which kernel-parameters (debug) to
> be considered/set?

1.) For identification of the chipset, please:
dmesg |grep "ath5.*chip"

2.) Is there a problem when you don't use encryption?

3.) git bisect might help track it down.

bruno

  reply	other threads:[~2010-12-01 10:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 10:09 [linux-next] next-20101201: ath5k permanently disconnecting Sedat Dilek
2010-12-01 10:21 ` Bruno Randolf [this message]
2010-12-01 10:56   ` Sedat Dilek
2010-12-01 11:21     ` Sedat Dilek
2010-12-01 21:04   ` Sedat Dilek
2010-12-02 17:33   ` Sedat Dilek
2010-12-02 17:56     ` Nick Kossifidis
2010-12-02 18:23       ` Nick Kossifidis
2010-12-02 22:33         ` Nick Kossifidis
2010-12-02 22:39           ` Nick Kossifidis
2010-12-03  2:10             ` Nick Kossifidis
2010-12-03  4:16               ` Nick Kossifidis
2010-12-03  6:15                 ` Sedat Dilek
2010-12-03  6:19                   ` Sedat Dilek
2010-12-03  6:31                   ` Nick Kossifidis
2010-12-03  6:49                     ` Sedat Dilek
2010-12-03 16:24                     ` Sedat Dilek
2010-12-01 22:05 ` Nick Kossifidis
2010-12-01 23:08   ` Sedat Dilek
2010-12-01 23:26   ` Sedat Dilek
2010-12-02 12:17 ` Sedat Dilek
2010-12-02 13:40   ` Sedat Dilek

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=201012011921.11151.br1@einfach.org \
    --to=br1@einfach.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mickflemm@gmail.com \
    --cc=sedat.dilek@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).