linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Joshua Smith <jesmith@kaon.com>
Cc: linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: Question about starting up an AP
Date: Mon, 27 Sep 2010 19:56:40 +0200	[thread overview]
Message-ID: <201009271956.41041.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <B17955D1-62BE-4A7E-8ECD-05FA62BD80B9@kaon.com>

Hi,

Am Montag 27 September 2010 schrieb Joshua Smith:
> The change to the REGISTER_BUSY_COUNT did not eliminate the issue. 
> The device still sometimes exhibits this behavior.  (It may be exhibiting
> it less often, but the occurrences are so random, that it's hard for me to
> know for sure.)

Yeah, as I said, just a shot in the dark.

> However, the other fix DID indeed eliminate the kernel crash when I tried
> to restart hostapd, and it also fixed a crash that I experienced when I
> tried to rmmod the rt2800pci module.  So you should definitely mainline
> that patch.

Sure.

> Now that I can retry hostapd and rmmod the modules, I have found that there
> is apparently no software workaround for the case where the DMA busy
> condition does not pass. 

Hmm, maybe there is but we have't found it yet ;)

> I have tried restarting hostapd, and I have tried rmmod'ding all the
> associated modules and modprobing them back in.  Nothing clears the
> condition except a reboot.

Too bad.

> Any other ideas of what I could do to reset the hardware?  I'd love to find
> a "soft" fix for this, rather than having to reboot to clear the condition.

Nothing obviouis at least. So, no without further debugging I don't know what's
going on in your case. Would be interesting if others experience the same
problem.

Helmut

  parent reply	other threads:[~2010-09-27 17:57 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 [this message]
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
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=201009271956.41041.helmut.schaa@googlemail.com \
    --to=helmut.schaa@googlemail.com \
    --cc=jesmith@kaon.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).