Hi Henry, I have filed this as bug 40972 along with the answers to your questions: https://bugzilla.kernel.org/show_bug.cgi?id=40972 In short, yes, the error does appear immediately after a full power-off shutdown as soon as I bring the interface up after loading the module. Not always, but more often than not. I am running 32-bit but have used 64bit prior. I reinstalled my system thinking that it was a problem with 64-bit libraries. The full lsmod is on the bug report. I am currently running fine again. I will keep my laptop on throughout the day in the hopes that it goes down. Let me know if you need anything else. Thanks so much Pedram On Thu, Aug 11, 2011 at 6:26 PM, Henry Ptasinski <henryp@xxxxxxxxxxxx> wrote: > 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@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxx and rvossen@xxxxxxxxxxxx on the bug. > > Thanks, > - Henry > > > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
