linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilya Kogan" <ikogan@mythicnet.org>
To: <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH] Kernel Panic on Associate with brcm80211.
Date: Thu, 20 Jan 2011 08:51:07 -0500	[thread overview]
Message-ID: <000001cbb8a9$181f4f40$485dedc0$@mythicnet.org> (raw)
In-Reply-To: <400C43189542CE41BC0A5B252FC90136952F059551@SJEXCHCCR02.corp.ad.broadcom.com>

Hey,

> I posted an official patch (removing the assert) to the staging repository
as 
> I did run into this same issue. It will take some time before it is
propagated. 
> As this is a staging driver patches are to be sent to
devel@linuxdriverproject.org 
> (see http://driverdev.linuxdriverproject.org/pipermail/devel/).

Thanks very much, guess I'm not as crazy as I thought. I'm seeing a lot more
of the 
AC_BE txop exceeded phylen errors. For some reason, I cannot maintain TCP 
connections either. I haven't had a chance to wireshark the behavior, but
even if
I'm not doing a lot of data transfers, my connections will die randomly with
no indications
as to why. I don't lose my AP association and nothing gets reinitialized.
I'm not sure if
this problem is related to the errors as they don't reliably happen around
when the
connections give out. By the way, in case there's any question, I've
confirmed that the
card works correctly on Windows.

Thanks,
-- Ilya Kogan



      reply	other threads:[~2011-01-20 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16 19:54 Kernel Panic on Associate with brcm80211 Ilya Kogan
2011-01-18  5:15 ` [PATCH] " Ilya Kogan
2011-01-20 11:21   ` zach
2011-01-20 12:23     ` Arend Van Spriel
2011-01-20 13:51       ` Ilya Kogan [this message]

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='000001cbb8a9$181f4f40$485dedc0$@mythicnet.org' \
    --to=ikogan@mythicnet.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).