linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Henry Ptasinski" <henryp@broadcom.com>
To: "Pedram Navid" <pedram.navid@gmail.com>
Cc: "ali@internetdog.org" <ali@internetdog.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Henry Ptasinski" <henryp@broadcom.com>
Subject: Re: brcmsmac: fifo 0: descriptor error
Date: Thu, 11 Aug 2011 15:26:24 -0700	[thread overview]
Message-ID: <20110811222624.GJ8119@broadcom.com> (raw)
In-Reply-To: <CAPoLzpeQF_xO_4eT2CKfp9cXKWUopssHjCkXd3_b0e8EAn8e_w@mail.gmail.com>

On Thu, Aug 11, 2011 at 03:35:32AM -0700, Pedram Navid wrote:
> Thank you Ali, I apologize, this is my first time reporting a bug
> through a mailing list.
> 
> Both lines repeat almost every second until I either run ifconfig
> wlan0 down or remove the module completely. I have since downgraded to
> 2.6.39 and am using the wl module and don't seem to have any problems.
> I still have the 3.0 Kernel available if anyone would like me to test
> further.
> 
> On Wed, Aug 10, 2011 at 10:15 PM, Ali Bahar <ali@internetdog.org> wrote:
> > Hi Pedram,
> >
> > you must use a meaningful Subject-line for your email.
> > Hopefully, this'll attract the attention of the couple of Broadcom guys
> > who are on this list.
> >
> > Also,
> >
> >
> > On Wed, Aug 10, 2011 at 06:48:45PM -0400, Pedram Navid wrote:
> >> Hello,
> >>
> >> I'd like to report a bug I have not been able to find elsewhere. I am on
> >> a fresh Arch install with linux 3.0.1-1, using the brcmsmac module.
> >> Initially, the wireless works for a few days. At some point, it will
> >> stop, outputing the following error repeatedly:
> >>
> >> Aug  7 09:55:27 localhost kernel: [  825.796697] ieee80211 phy0: wl0:
> >> fifo 0: descriptor error
> >> Aug  7 09:55:27 localhost kernel: [  825.796713] ieee80211 phy0: wl0:
> >> fatal error, re-initializing
> >
> > You may wish to note which of these lines repeat. Do both repeat, or
> > only the "re-initializing" line? (It may be easier to just paste a few
> > lines into your mail.)
> >
> > later,
> > ali
> >
> >
> >> I can rmmod brcmsmac, reboot, shutdown, give it a few days, and start
> >> over and it will sometimes work. Other times, it will persist with the
> >> fifo errors. 

Just to be clear:  You can power off the machine, and immediately after
starting up again you see these error messages?

> >> Please let me know you need additional log files. I had
> >> this problem since 2.6.38 and reinstalled Arch twice, thinking it was
> >> something with my setup that was done incorrectly but haven't been
> >> able to figure it out. I can't find another case of this error on the
> >> internet.

Can you provide some details about the network setup where you see this issue
(band, channel, a/b/g/n, security enabled/disabled) and the host (cpu, 32- or
64-bit kernel).

> >>
> >> #    lspci -vnn | grep 14e4
> >> 05:00.0 Network controller [0280]: Broadcom Corporation
> >> 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
> >>        Subsystem: Broadcom Corporation Device [14e4:0510]
> >>
> >>  #  lsmod  | grep brc
> >> brcmsmac              594624  0
> >> brcmutil                6563  1 brcmsmac
> >> mac80211              215605  1 brcmsmac
> >> cfg80211              160516  2 brcmsmac,mac80211
> >> crc_ccitt               1331  1 brcmsmac

Can you provide the full output of lsmod?

Also, can you file this as a bug in bugzilla.kernel.org to make it easier for
us to track?  CC henryp@broadcom.com and rvossen@broadcom.com on the bug.

Thanks,
- Henry



  reply	other threads:[~2011-08-11 22:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6264DDFA6754194CAB6452BFF5202C330F5F2115@SXGM-401.fg.rbc.com>
2011-08-10 22:48 ` Fwd: Pedram Navid
2011-08-11  2:15   ` brcmsmac: fifo 0: descriptor error Ali Bahar
2011-08-11 10:35     ` Pedram Navid
2011-08-11 22:26       ` Henry Ptasinski [this message]
2011-08-12  0:33         ` Pedram Navid
2011-08-19 14:29           ` Roland Vossen

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=20110811222624.GJ8119@broadcom.com \
    --to=henryp@broadcom.com \
    --cc=ali@internetdog.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pedram.navid@gmail.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).