From: reinette chatre <reinette.chatre@intel.com>
To: "lmage11@twcny.rr.com" <lmage11@twcny.rr.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Help debugging unexpected disassociations?
Date: Thu, 08 Jan 2009 15:12:51 -0800 [thread overview]
Message-ID: <1231456371.7467.103.camel@rc-desk> (raw)
In-Reply-To: <20090108224343.F9TJC.227705.root@hrndva-web20-z02>
On Thu, 2009-01-08 at 14:43 -0800, lmage11@twcny.rr.com wrote:
> ---- lmage11@twcny.rr.com wrote:
> > Hey everyone. I'm using an Intel 4965AGN using the iwlagn
> > driver in 2.6.28. When using a specific AP, my connection is
> > unexpectedly dropping with nothing more than a
> > "wlan0: deauthenticated". Any tips on how I could figure out
> > whether this is the driver's fault or the AP's? Another problem I'm
> > having is that dhcpcd is timing out a lot, usually after trying to
> > reconnect from a connection drop.
> >
> > The AP is a Linksys WRT54Gv1 with WPA2 and ssid broadcasting enabled.
> >
> > Thanks!
> >
> > Ari
>
> Um... Bump?
This is very little information to go by. Does the log print a reason
code? Could you please provide some debug logs? Ensure driver is
compiled with debugging and load module with debug=0x43fff.
Reinette
next prev parent reply other threads:[~2009-01-08 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 1:38 Help debugging unexpected disassociations? lmage11
2009-01-08 22:43 ` lmage11
2009-01-08 23:06 ` Hin-Tak Leung
2009-01-08 23:18 ` lmage11
2009-01-09 21:08 ` Hin-Tak Leung
2009-01-08 23:12 ` reinette chatre [this message]
2009-01-08 23:22 ` lmage11
-- strict thread matches above, loose matches on Subject: below --
2009-01-10 2:13 lmage11
2009-01-10 13:16 ` Hin-Tak Leung
2009-01-11 4:58 ` Ari Entlich
2009-01-11 14:58 ` Hin-Tak Leung
2009-01-11 15:48 ` Hin-Tak Leung
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=1231456371.7467.103.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lmage11@twcny.rr.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