14e4:4727 wifi lock-up with brcmsmac and broadcom bcm4313

Bug #871580 reported by Ben on 2011-10-10
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

This is a duplicate of 856314, I am adding it here because the original poster has not submitted the apport info to the other bug report.

I experience intermittent network lock-ups when using the brcmsmac driver with broadcom bcm4313 wireless NIC. Pinging to a remote machine returns the following message

ping: sendmsg: No buffer space available

Unloading a reloading the module may temporarily fix the problem.

I have noticed that the lock-up frequency varies with the access point. I have a Belkin F5D8236-4 that I experience frequent lock ups with. Typically I have to use the updated drivers from http://linuxwireless.org to connect to it under linux 2.6.x. On most other access points I can work all day without a problem.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ben 1573 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb44000 irq 43'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card0.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Card1.Amixer.info:
 Card hw:1 'SB'/'HDA ATI SB at 0xfeb40000 irq 16'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,1043841c,00100100'
   Controls : 13
   Simple ctrls : 9
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=4c9db147-fccc-4793-afc5-ae8c80067362
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
MachineType: ASUSTeK Computer INC. 1215B
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=/dev/mapper/rock-u1110_root ro
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
StagingDrivers: brcmsmac brcmutil
Tags: oneiric running-unity staging
Uname: Linux 3.0.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/17/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 1215B
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd06/17/2011:svnASUSTeKComputerINC.:pn1215B:pvrx.x:rvnASUSTeKComputerINC.:rn1215B:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1215B
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

apport information

tags: added: apport-collected oneiric running-unity staging
description: updated

apport information

apport information

Ben (a0-ben-ch) wrote : BootDmesg.txt

apport information

apport information

apport information

apport information

apport information

Ben (a0-ben-ch) wrote : IwConfig.txt

apport information

Ben (a0-ben-ch) wrote : Lspci.txt

apport information

Ben (a0-ben-ch) wrote : Lsusb.txt

apport information

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 871580

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

apport information

apport information

apport information

Brad Figg (brad-figg) on 2011-10-10
Changed in linux (Ubuntu):
status: New → Incomplete

apport information

apport information

apport information

Ben (a0-ben-ch) wrote : RfKill.txt

apport information

Ben (a0-ben-ch) wrote : UdevDb.txt

apport information

Ben (a0-ben-ch) wrote : UdevLog.txt

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

tags: added: needs-upstream-testing
Greg (g6) wrote :

I had this problem on Oneiric and found installing the 3.1.8 kernel from the mainline repo fixed it (I tried a few other kernel versions that also didn't work). Network connectivity now seems fine and I've been running a ping for a long time with minimal packet loss and no buffer error messages.

Greg (g6) wrote :

Spoke too soon. Still broken on 3.1.8, it just takes longer to appear. I'm also seeing a ton of these:
kernel: [25263.577957] ieee80211 phy0: START: tid 1 is not agg'able

tags: removed: needs-upstream-testing

Ben, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Ben (a0-ben-ch) wrote :

Testing with kernel 3.5.2 produces the same lock-ups. The issue appears to be associated with signal strength, with the lock ups being much more likely with a weak signal. The surest way to cause a lock up is to connect and then walk with the laptop out of signal reach.

summary: - wifi lock-up with brcmsmac and broadcom bcm4313
+ 14e4:4727 wifi lock-up with brcmsmac and broadcom bcm4313

are you sure it's broadcom specific?

i'm experiencing pretty much the same behavior with iwlwifi on 3.2.0-4-amd64.

Greg / Attila Lendvai, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers