[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#664767: Brcmsmac driver woes, possible regression?



Hi Camaleón,

Camaleón wrote:

> Mmm... I'm attaching a kernel oops I got after having the module
> loaded, curious is that despite the oops, the wireless link is up and
> running, no reconnects (which reminds me the first reports...). Will
> report back for any other update or change in the wireless activity.

Thanks.  I assume you mean the brcms_c_wait_... warning when you refer
to an oops.  Separating the symptoms:

  brcms_c_wait_for_tx_completion warning: bug#672891
  connection resets, segfaults, general instability: bug#664767 (this bug)
  "AMPDU status: BA Timeout": bug#674430

Seth wrote[1]:

| The trace is related to handling a disconnection, which will also
| trigger a reprocessing of the regulatory rules. The warning and the
| regulatory message share a common cause, but I don't think there's a
| direct relationship between them.

I don't think his regulatory series[2] is likely to affect your
symptoms, but maybe it will be easier to get help once that has been
reviewed and applied upstream.

In the meantime, thanks for your updates --- this helps a lot.

Regards,
Jonathan

[1] http://thread.gmane.org/gmane.linux.kernel.wireless.general/87873/focus=87922
[2] http://thread.gmane.org/gmane.linux.kernel.wireless.general/89097



Reply to: