b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Chris Vine <chris@cvine.freeserve.co.uk>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
	wireless <linux-wireless@vger.kernel.org>,
	"Michael Büsch" <mb@bu3sch.de>,
	b43-dev <b43-dev@lists.infradead.org>
Subject: b43 error under heavy load
Date: Wed, 1 Jun 2011 16:01:01 +0100	[thread overview]
Message-ID: <20110601160101.75e30b3d@boulder.homenet> (raw)
In-Reply-To: <BANLkTi=2xYrrjEdHuYCKFKy4H2EXoUGQuQ@mail.gmail.com>

On Wed, 1 Jun 2011 14:25:23 +0200
Rafa? Mi?ecki <zajec5@gmail.com> wrote:
> I think you should easily get this error by transmitting. Streaming
> some video is mostly receiving. Just putting some random
> (ftp/sftp/iperf) server in the network would make the trick.

OK rather than recompile the kernel with debugfs enabled, as you
suggested I took the debugging call to b43dbg() out of the
B43_DBG_DMAVERBOSE if block (so it is entered whether or not verbose
debugging is set).

I transferred a 268MB file across the LAN in a little over 5 minutes
(so the transfer speed was a little under 10Mb/s).  During the course
of the transfer I got about 500 "b43-phy0 debug: Stopped TX ring 1"
statements logged.

However the interesting thing is that with this debugging statement
included, I got no messages about any out of order TX status; instead,
apart from the overrun messages to the debug log, the link performed
normally. The file transfer did not fail (I have checked that the file
received is identical to the file sent) nor was the link to the router
lost. Probably writing to the debug log has changed some timing race
somewhere to the benefit of link integrity.

However, as I said, I am not going to be in a position to do much
testing by way of transferring further files over the LAN for a period
of time, for unrelated reasons.

Chris

  reply	other threads:[~2011-06-01 15:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 18:41 b43 error under heavy load Larry Finger
2010-11-22 18:53 ` Michael Büsch
2010-11-22 19:12   ` Larry Finger
2011-05-10  5:08     ` Rafał Miłecki
2011-05-10 18:34       ` Larry Finger
2011-05-10 21:19         ` Rafał Miłecki
2011-06-01  9:23           ` Rafał Miłecki
2011-06-01  9:24             ` Rafał Miłecki
2011-06-01 10:48             ` Chris Vine
2011-06-01 10:56               ` Rafał Miłecki
2011-06-01 12:08                 ` Chris Vine
2011-06-01 12:25                   ` Rafał Miłecki
2011-06-01 15:01                     ` Chris Vine [this message]
2011-06-01 15:42                       ` Rafał Miłecki
2011-06-01 17:49                         ` Chris Vine
2011-06-01 18:03                           ` Rafał Miłecki
2011-06-01 18:09                             ` Chris Vine
2011-06-01 18:10                               ` Rafał Miłecki
2011-07-26  9:28                                 ` Chris Vine
2011-08-14 11:10                           ` Rafał Miłecki
2011-08-14 11:11                             ` Rafał Miłecki
2011-08-14 20:46                               ` Chris Vine
2011-08-14 20:54                                 ` Rafał Miłecki
2011-08-14 21:19                                   ` Chris Vine

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=20110601160101.75e30b3d@boulder.homenet \
    --to=chris@cvine.freeserve.co.uk \
    --cc=Larry.Finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=zajec5@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 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).