All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Francesco Gringoli <francesco.gringoli@ing.unibs.it>
Cc: Lorenzo Nava <navalorenx@gmail.com>,
	wireless <linux-wireless@vger.kernel.org>,
	Michael Buesch <mb@bu3sch.de>
Subject: Re: More data on open-source firmware crash
Date: Tue, 24 Feb 2009 12:42:18 -0600	[thread overview]
Message-ID: <49A43F8A.5000500@lwfinger.net> (raw)
In-Reply-To: <7528B52E-1B77-4CA9-A17F-01E24FDF81DC@ing.unibs.it>

Francesco Gringoli wrote:
> 
> On Feb 24, 2009, at 5:35 PM, Larry Finger wrote:
> 
>> Francesco Gringoli wrote:
>>> What about drop info from dmesg? Another try could be halve the dma
>>> queue, I believe now it is 64 slots. Could you give a try setting it
>>> to 32?
>>
>> The RX DMA queue was 64 and TX was 256. Both will be 32 in my next run.
>>
>> I don't understand the "drop info from dmesg" part.
> Sorry Larry,
> 
> sometimes when I modify something, I can read
> 
> [334415.451028] b43-phy244 debug: RX: Packet dropped
> 
> in the dmesg because the received bytes were not correctly copied
> between the "air-buffer" to the internal buffer and finally to the
> rx-fifo along with the rxheader.
> 
> Did you notice something similar?

I hadn't noticed them before, but I do see one of these messages just before
some of my out-of-order cookies. There is no associated diagnostic message, thus
it must come from the status.rate_index test. I'll see if I can get some info
from there.

Larry


  reply	other threads:[~2009-02-24 18:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 19:10 More data on open-source firmware crash Larry Finger
2009-02-22 19:20 ` Michael Buesch
2009-02-22 19:47 ` Francesco Gringoli
2009-02-24 16:23   ` Larry Finger
2009-02-24 16:29     ` Francesco Gringoli
2009-02-24 16:35       ` Larry Finger
2009-02-24 16:44         ` Francesco Gringoli
2009-02-24 18:42           ` Larry Finger [this message]
2009-02-24 18:50             ` Francesco Gringoli

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=49A43F8A.5000500@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=francesco.gringoli@ing.unibs.it \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=navalorenx@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.