linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Joshua Smith <JoshuaESmith@charter.net>
Cc: "linux-wireless" <linux-wireless@vger.kernel.org>,
	users@rt2x00.serialmonkey.com, Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: Question about starting up an AP
Date: Fri, 1 Oct 2010 07:42:07 +0200	[thread overview]
Message-ID: <201010010742.07605.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <201009301814.47318.helmut.schaa@googlemail.com>

Hi Joshua,

Am Donnerstag 30 September 2010 schrieb Helmut Schaa:
> Am Donnerstag 30 September 2010 schrieb Joshua Smith:
> > I think I have a clue about the WPDMA TX/RX busy bug.  I was having trouble
> > using the latest compat-wireless with USB dongle I have (ID AB50:2019
> > rt73usb), so I tried rolling Helmut's "oops" fix into:
> > 
> > compat-wireless-2010-07-15
> > 
> > which I have been using successfully for the last few months.  Lo and behold,
> > this version does *NOT* exhibit the TX/RX busy error.  So whatever is causing
> > that problem was introduced between 7/15/2010 and 9/20/2010.
> 
> Thanks for the analysis Joshua! Since this is a regression I guess we
> should try to find out quickly which commit introduced it (and fix it up
> of course) ...

Unfortunately during that time a lot of rt2x00 patches went into
wireless-testing. However, there's one suspicious commit that touches the
relevant code: "rt2x00: Merge rt2800{pci/usb} radio enabling/disabling code
to rt2800lib".

This is again a shot in the dark but worth a try. Could you please revert this
commit [1] from the newer compat-wireless tarball and try if it fixes the "DMA
Busy" issue?

Thanks Joshua,
Helmut

[1] http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commit;h=b9a07ae9d9e09662013992088fd58ffbcb2f9a30

  reply	other threads:[~2010-10-01  5:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 19:25 Question about starting up an AP Joshua Smith
2010-09-25  8:18 ` Helmut Schaa
2010-09-25  8:34 ` Helmut Schaa
     [not found]   ` <B17955D1-62BE-4A7E-8ECD-05FA62BD80B9@kaon.com>
2010-09-27 17:56     ` Helmut Schaa
2010-09-27 19:21       ` Joshua Smith
2010-09-27 19:43         ` Helmut Schaa
2010-09-27 20:26           ` Joshua Smith
2010-09-27 20:35             ` Helmut Schaa
2010-09-29 18:21               ` Joshua Smith
2010-09-30 15:52                 ` Joshua Smith
2010-09-30 16:14                   ` Helmut Schaa
2010-10-01  5:42                     ` Helmut Schaa [this message]
2010-10-14 17:16                       ` Joshua Smith
2010-10-15  9:46                         ` Helmut Schaa
2010-10-15 13:36                           ` Joshua Smith
2010-10-26  9:35                           ` Helmut Schaa
2010-10-26  9:41                             ` Johannes Berg
2010-10-26 10:04                               ` Helmut Schaa
2010-10-26 11:34                                 ` Ivo Van Doorn
2010-09-27 19:46         ` Helmut Schaa

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=201010010742.07605.helmut.schaa@googlemail.com \
    --to=helmut.schaa@googlemail.com \
    --cc=JoshuaESmith@charter.net \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=users@rt2x00.serialmonkey.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).