From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Pavel Roskin <proski@gnu.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] Crda oopses the system
Date: Fri, 22 May 2009 03:20:11 +0300 [thread overview]
Message-ID: <1242951611.5206.9.camel@maxim-laptop> (raw)
In-Reply-To: <1242742647.23110.10.camel@ibm172>
On Tue, 2009-05-19 at 17:17 +0300, Maxim Levitsky wrote:
> On Thu, 2009-05-14 at 10:20 -0400, Bob Copeland wrote:
> > On Wed, May 13, 2009 at 8:07 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> > >>
> > >> I wish I had time to set up, an ath5k in AP mode. There are rumors that
> > >> it works more or less now, then I could use the same beacon frame to
> > >> test.
> > >
> > > It does and if it doesn't its a bug.
> >
> > Just FYI, it's known to have problems if the STA uses power saving --
> > ath5k never updates the beacon. I have a patch that should work in the
> > relevant bugzilla but I haven't been back to retest it (at first I
> > thought it was causing hangs, but later realized the hangs were due to
> > other bugs in w-t).
> >
>
I was just able to reproduce that bug on latest wireless-testing that I
belive contains the patches you sent for me to test.
I reproduced it against ath5k running in AP mode at home.
I finally made the ath5k send beacons (although not much works besides
this).
Note that I noticed that this bug happens once at boot, if I set NM to
use system settings, when I try to connect again it doesn't happen. Its
a race condition after all.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-05-22 0:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 5:04 [BUG] Crda oopses the system Maxim Levitsky
2009-05-05 18:46 ` Luis R. Rodriguez
2009-05-06 10:47 ` Maxim Levitsky
2009-05-06 20:34 ` Pavel Roskin
2009-05-10 12:20 ` Maxim Levitsky
2009-05-10 18:33 ` Luis R. Rodriguez
2009-05-10 19:34 ` Maxim Levitsky
2009-05-10 19:36 ` Luis R. Rodriguez
2009-05-12 15:05 ` Maxim Levitsky
2009-05-12 17:24 ` Luis R. Rodriguez
2009-05-12 17:34 ` Maxim Levitsky
2009-05-12 22:00 ` Luis R. Rodriguez
2009-05-12 22:07 ` Maxim Levitsky
2009-05-13 21:28 ` Luis R. Rodriguez
2009-05-13 23:08 ` Maxim Levitsky
2009-05-13 23:12 ` Luis R. Rodriguez
2009-05-13 23:22 ` Maxim Levitsky
2009-05-13 23:28 ` Luis R. Rodriguez
2009-05-13 23:47 ` Maxim Levitsky
2009-05-14 0:07 ` Luis R. Rodriguez
2009-05-14 14:20 ` Bob Copeland
2009-05-19 14:17 ` Maxim Levitsky
2009-05-22 0:20 ` Maxim Levitsky [this message]
2009-05-22 0:36 ` Luis R. Rodriguez
2009-05-22 10:08 ` Maxim Levitsky
2009-05-31 6:22 ` Luis R. Rodriguez
2009-05-31 12:47 ` Maxim Levitsky
2009-05-31 20:54 ` Maxim Levitsky
2009-05-31 21:13 ` Maxim Levitsky
2009-05-31 22:24 ` Luis R. Rodriguez
2009-05-31 22:48 ` Maxim Levitsky
2009-06-01 0:32 ` Bob Copeland
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=1242951611.5206.9.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=proski@gnu.org \
/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