From: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>
To: Arend van Spriel <arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Cc: <balbi-l0cyMroinI0@public.gmane.org>,
Pieter-Paul Giesberts
<pieterpg-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
Hauke Mehrtens <hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>,
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<brcm80211-dev-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: brcm WARN() on v3.7.2
Date: Sat, 26 Jan 2013 14:56:22 +0200 [thread overview]
Message-ID: <20130126125622.GA9542@arwen.pp.htv.fi> (raw)
In-Reply-To: <5103B595.8060805-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
Hi,
On Sat, Jan 26, 2013 at 11:53:09AM +0100, Arend van Spriel wrote:
> On 01/25/2013 09:23 PM, Felipe Balbi wrote:
> > Hi folks,
> >
> > I'm running Fedora 18 with v3.7.2 on her MacBookAir 11" and it
> > turns out that brcm is acting out, see below full dmesg. Any tips ?
> > Is this fixed already ?
>
> Thanks, Felipe
>
> The warning itself means flush timed out, ie. not all outstanding
> packets could be transmitted. It does not necessarily mean the driver
> is failing. So do you have any connectivity issues after the warning
> has occurred?
not really, just thought I'd mention it ;-)
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-26 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 20:23 brcm WARN() on v3.7.2 Felipe Balbi
2013-01-26 10:53 ` Arend van Spriel
[not found] ` <5103B595.8060805-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2013-01-26 12:56 ` Felipe Balbi [this message]
2013-01-26 15:14 ` Luciano Coelho
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=20130126125622.GA9542@arwen.pp.htv.fi \
--to=balbi-l0cymroini0@public.gmane.org \
--cc=arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=brcm80211-dev-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pieterpg-dY08KVG/lbpWk0Htik3J/w@public.gmane.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).