linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: Daniel <dan@f-box.org>, linux-wireless@vger.kernel.org
Subject: Re: 4311 v2 Bail - 2.6.26-rc2
Date: Wed, 14 May 2008 01:27:22 +0200	[thread overview]
Message-ID: <200805140127.22302.mb@bu3sch.de> (raw)
In-Reply-To: <482A08A5.3000204@f-box.org>

On Tuesday 13 May 2008 23:31:17 Daniel wrote:
> Hello,
> 
> Michael Buesch wrote:
> > Could you _please_ be so kind an explain your actual problem??
> > My magic crystalball is broken today.
> 
> Sorry, it's the problem where after X minutes the device seems to loose 
> the ability to communicate. It seems to be on a high number of 
> connections/sec scenario.
> 
> It seems to occur at the 2nd or 3rd issue of the "wrong buffer size" 
> message.

Where does this "wrong buffer size" message come from, and what does it mean?

> b43-phy1 debug: Using hardware based encryption for keyidx: 1, mac: 
> ff:ff:ff:ff:ff:ff
> wlan0: wrong buffer size<7>wlan0: wrong buffer size<7>wlan0: wrong 
> buffer size<7>wlan0: wrong buffer size
> b43-phy1 debug: Disabling hardware based encryption for keyidx: 1, mac: 
> ff:ff:ff:ff:ff:ff

-- 
Greetings Michael.

       reply	other threads:[~2008-05-13 23:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48294F0B.4040908@f-box.org>
     [not found] ` <200805131119.09964.mb@bu3sch.de>
     [not found]   ` <482A08A5.3000204@f-box.org>
2008-05-13 23:27     ` Michael Buesch [this message]
2008-05-13 23:33       ` 4311 v2 Bail - 2.6.26-rc2 Johannes Berg
2008-05-13 23:36         ` Johannes Berg
2008-05-13 23:46           ` Michael Buesch
2008-05-13 23:48             ` Johannes Berg
2008-05-13 23:52               ` Johannes Berg
2008-05-15 15:13                 ` Daniel
2008-05-15 16:18                   ` Johannes Berg
2008-05-14  4:46       ` Pavel Roskin

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=200805140127.22302.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=dan@f-box.org \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).