linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Josh Boyer" <jwboyer@fedoraproject.org>
Cc: "Felix Fietkau" <nbd@openwrt.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Tom Gundersen" <teg@jklm.no>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"Linux Wireless List" <linux-wireless@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Johannes Berg" <johannes@sipsolutions.net>
Subject: Re: [REGRESSION] 3.10.{6,7} crashes on network activity
Date: Wed, 21 Aug 2013 16:27:43 +0200	[thread overview]
Message-ID: <5214CE5F.5010009@broadcom.com> (raw)
In-Reply-To: <CA+5PVA5Wi=Xjrsb_Rh53A4NkWHe3h-gfs89dO6Zfb+6uh+G=dQ@mail.gmail.com>

On 08/21/13 14:38, Josh Boyer wrote:
> On Wed, Aug 21, 2013 at 4:52 AM, Arend van Spriel<arend@broadcom.com>  wrote:
>>>> Hi Felix,
>>>>
>>>> I have been diving into root causing why brcmsmac can not handle cck
>>>> fallback rates, because it should. Maybe it is better to flag no cck
>>>> support
>>>> and only change brcmsmac.
>>>
>>>
>>> We have a number of users hitting this in Fedora 18 and 19 now.  We're
>>> tracking it with https://bugzilla.redhat.com/show_bug.cgi?id=998080
>>> and I'm sure we can find people to test easily.
>>
>>
>> There is already another one (possibly) dealing with the same issue:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=989269
>>
>> One of them should probably be flagged as duplicate.
>>
>>
>>> If you have a patch disabling cck in brcmsmac, I'd be happy to build a
>>> kernel for people.  If that's going to be some time coming, perhaps
>>> it's better to grab Felix's patch on a temporary basis?
>>
>>
>> I think it is better to grab Felix's patch because as we both observed there
>> is stuff missing in brcmsmac to deal with CCK rates and A-MPDU packet
>> aggregation.
>
> OK, thanks.
>
> Felix, are you going to send that upstream?

It already has been sent: 
http://mid.gmane.org/1377020634-27064-1-git-send-email-nbd@openwrt.org

Johannes has submitted it to John so it is getting there soon(ish).

> josh

Regards,
Arend




  reply	other threads:[~2013-08-21 14:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAG-2HqUXQeq=30EpGWmn6tkC=CP1W+=UZCVPTYhhE0WyU_C4nw@mail.gmail.com>
2013-08-20  0:03 ` [REGRESSION] 3.10.{6,7} crashes on network activity Greg Kroah-Hartman
2013-08-20  0:26   ` Tom Gundersen
2013-08-20  0:28     ` Greg Kroah-Hartman
2013-08-20  4:56       ` Felix Fietkau
2013-08-20  8:15         ` Arend van Spriel
2013-08-20  8:36           ` Tom Gundersen
2013-08-20  9:58             ` Arend van Spriel
2013-08-20 10:10               ` Georgios Magklaras
2013-08-20 17:36           ` Felix Fietkau
2013-08-20 19:04             ` Arend van Spriel
2013-08-21  0:11           ` Josh Boyer
2013-08-21  8:52             ` Arend van Spriel
2013-08-21 12:38               ` Josh Boyer
2013-08-21 14:27                 ` Arend van Spriel [this message]
2013-08-21 14:45                   ` Josh Boyer
2013-08-20  8:34         ` Tom Gundersen

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=5214CE5F.5010009@broadcom.com \
    --to=arend@broadcom.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.org \
    --cc=stable@vger.kernel.org \
    --cc=teg@jklm.no \
    /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).