ieee80211 phy0: START: tid 1 is not agg'able

Bug #889675 reported by Nick Colgan
74
This bug affects 16 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Thousands of these error messages are clogging my syslog:

Nov 12 19:29:59 buk kernel: [ 8284.976165] ieee80211 phy0: START: tid 1 is not agg'able
Nov 12 19:29:59 buk kernel: [ 8285.252159] ieee80211 phy0: START: tid 1 is not agg'able
Nov 12 19:29:59 buk kernel: [ 8285.364155] ieee80211 phy0: START: tid 1 is not agg'able
Nov 12 19:29:59 buk kernel: [ 8285.676170] ieee80211 phy0: START: tid 1 is not agg'able
Nov 12 19:29:59 buk kernel: [ 8285.772491] ieee80211 phy0: START: tid 1 is not agg'able
Nov 12 19:30:00 buk kernel: [ 8285.880156] ieee80211 phy0: START: tid 1 is not agg'able
Nov 12 19:30:00 buk kernel: [ 8286.140176] ieee80211 phy0: START: tid 1 is not agg'able
Nov 12 19:30:00 buk kernel: [ 8286.595293] ieee80211 phy0: START: tid 1 is not agg'able
Nov 12 19:30:01 buk kernel: [ 8287.394116] ieee80211 phy0: START: tid 1 is not agg'able
Nov 12 19:30:03 buk kernel: [ 8288.988171] ieee80211 phy0: START: tid 1 is not agg'able
Nov 12 19:30:03 buk kernel: [ 8289.448161] ieee80211 phy0: START: tid 1 is not agg'able

Using Ubuntu 11.10
Linux 3.0.0-12-generic

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ieee80211 (Ubuntu):
status: New → Confirmed
Revision history for this message
Robert Hooker (sarvatt) wrote :

This error comes from the brcmsmac driver in the kernel

affects: ieee80211 (Ubuntu) → linux (Ubuntu)
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

There is a newer version of the kernel[0] than the one you tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not. You can upgrade just your kernel by running the following in a terminal:

sudo apt-get update
sudo apt-get install linux

If the bug still exists in the latest kernel, please change the status back to "Confirmed". If the bug is fixed, please change the status to "Fix Released".

Thanks in advance

[0] https://launchpad.net/ubuntu/oneiric/+source/linux/3.0.0-16.29

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: oneiric
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Robert Hooker (sarvatt) wrote :

This is still a problem in the latest precise (3.2.0-18.29)

tags: added: precise
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-18.29)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to New. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux:
status: New → Incomplete
tags: added: kernel-request-3.2.0-18.29
Revision history for this message
Ao Phidly (aophidly) wrote :

Confirming this bug as per @brad-figg's request

Changed in linux:
status: Incomplete → New
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-19.30)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to New. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux:
status: New → Incomplete
tags: added: kernel-request-3.2.0-19.30
Revision history for this message
Robert Hooker (sarvatt) wrote :

dmesg with 3.2.0-19

tags: added: bot-stop-nagging
Revision history for this message
Jim McKean (jimmckean) wrote :

Confirm this problem on

# uname -a
# Linux Oz 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:52 UTC 2012 i686 i686 i386 GNU/Linux

Wireless dropping and reconnecting frequently.

Also problem with this driver when awakening from suspend

penalvch (penalvch)
tags: added: needs-upstream-testing
removed: kernel-request-3.2.0-18.29 kernel-request-3.2.0-19.30
tags: added: needs-kernel-logs
Revision history for this message
Eduard Biceri-Matei (cubusbacau) wrote :

Confirm this on kernel 3.5.0
$ uname -a
 3.5.0-21-generic #32-Ubuntu SMP Tue Dec 11 18:51:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
$ lsmod | grep brcm
brcmsmac 531848 0
mac80211 539908 1 brcmsmac
bcma 35656 1 brcmsmac
brcmutil 14755 1 brcmsmac
cfg80211 206566 2 brcmsmac,mac80211
cordic 12535 1 brcmsmac

Dec 21 18:06:00 eduard-TravelMate-5742 kernel: [57675.823377] ieee80211 phy0: START: tid 1 is not agg'able

Revision history for this message
penalvch (penalvch) wrote :

Nick Colgan, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

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

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
alphac (alphac) wrote :

Same thing here, chip is Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)

using brcmsmac module, the proprietary one does not go over 54Mbps and has a similar logging bug, b43 is working worst than brcmsmac.

Nov 19 09:49:39 alphac-pc kernel: [ 148.430871] brcmsmac bcma0:1: START: tid 1 is not agg'able
Nov 19 09:49:43 alphac-pc kernel: [ 152.275476] brcmsmac bcma0:1: START: tid 1 is not agg'able
Nov 19 09:49:43 alphac-pc kernel: [ 152.283528] brcmsmac bcma0:1: START: tid 1 is not agg'able
Nov 19 09:50:25 alphac-pc kernel: [ 194.382852] brcmsmac bcma0:1: START: tid 1 is not agg'able
Nov 19 09:50:25 alphac-pc kernel: [ 194.414879] brcmsmac bcma0:1: START: tid 1 is not agg'able
Nov 19 09:50:25 alphac-pc kernel: [ 194.438875] brcmsmac bcma0:1: START: tid 1 is not agg'able
Nov 19 09:50:34 alphac-pc kernel: [ 203.365016] brcmsmac bcma0:1: START: tid 1 is not agg'able
Nov 19 09:50:34 alphac-pc kernel: [ 203.381033] brcmsmac bcma0:1: START: tid 1 is not agg'able

Revision history for this message
alphac (alphac) wrote : apport information

ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alphac 1565 F.... pulseaudio
CurrentDmesg:
 [ 622.146303] brcmsmac bcma0:1: START: tid 1 is not agg'able
 [ 622.170306] brcmsmac bcma0:1: START: tid 1 is not agg'able
 [ 626.343097] brcmsmac bcma0:1: START: tid 1 is not agg'able
 [ 626.359100] brcmsmac bcma0:1: START: tid 1 is not agg'able
DistroRelease: Ubuntu 15.10
InstallationDate: Installed on 2015-09-05 (74 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 2232:1001 Silicon Motion
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: SAMSUNG ELECTRONICS CO., LTD. QX310/QX410/QX510/SF310/SF410/SF510
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=it_IT
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=7a190443-4e56-4ea8-98a8-296841ad7a95 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-18-generic N/A
 linux-backports-modules-4.2.0-18-generic N/A
 linux-firmware 1.149.2
Tags: wily
UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
Uname: Linux 4.2.0-18-generic x86_64
UpgradeStatus: Upgraded to wily on 2015-10-31 (18 days ago)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 05/25/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 05MX.M008.20110525.SCY
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: QX310/QX410/QX510/SF310/SF410/SF510
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 05MX
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr05MX.M008.20110525.SCY:bd05/25/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnQX310/QX410/QX510/SF310/SF410/SF510:pvr05MX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnQX310/QX410/QX510/SF310/SF410/SF510:rvr05MX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: QX310/QX410/QX510/SF310/SF410/SF510
dmi.product.version: 05MX
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

tags: added: apport-collected wily
Revision history for this message
alphac (alphac) wrote : AlsaInfo.txt

apport information

Revision history for this message
alphac (alphac) wrote : CRDA.txt

apport information

Revision history for this message
alphac (alphac) wrote : IwConfig.txt

apport information

Revision history for this message
alphac (alphac) wrote : JournalErrors.txt

apport information

Revision history for this message
alphac (alphac) wrote : Lspci.txt

apport information

Revision history for this message
alphac (alphac) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
alphac (alphac) wrote : ProcInterrupts.txt

apport information

Revision history for this message
alphac (alphac) wrote : ProcModules.txt

apport information

Revision history for this message
alphac (alphac) wrote : RfKill.txt

apport information

Revision history for this message
alphac (alphac) wrote : UdevDb.txt

apport information

Revision history for this message
alphac (alphac) wrote : WifiSyslog.txt

apport information

Changed in linux:
status: Incomplete → New
Revision history for this message
alphac (alphac) wrote :

Added apport info, I'm also affected by this bug

Changed in linux:
status: New → Confirmed
alphac (alphac)
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.2.0-18-generic
removed: needs-kernel-logs needs-upstream-testing oneiric
tags: added: oniric
tags: added: oneiric
removed: oniric
Revision history for this message
alphac (alphac) wrote :

Adding that I also have erratic problems reconnecting after suspend (sometimes it happens also straight after boot) both with proprietary and brcmsmac, it just stops associating with AP and I have to reboot (rarely more than one time).

Revision history for this message
penalvch (penalvch) wrote :

alphac, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

tags: added: needs-kernel-logs needs-upstream-testing
removed: apport-collected kernel-bug-exists-upstream kernel-bug-exists-upstream-4.2.0-18-generic wily
no longer affects: linux (Ubuntu)
affects: linux → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
importance: Undecided → Low
Revision history for this message
alphac (alphac) wrote : Re: [Bug 889675] Re: ieee80211 phy0: START: tid 1 is not agg'able
Download full text (3.7 KiB)

Done :)

On Thu, Nov 19, 2015 at 1:17 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> alphac, it will help immensely if you filed a new report via a terminal:
> ubuntu-bug linux
>
> Please feel free to subscribe me to it.
>
> ** Tags removed: apport-collected kernel-bug-exists-upstream
> kernel-bug-exists-upstream-4.2.0-18-generic wily
> ** Tags added: needs-kernel-logs needs-upstream-testing
>
> ** No longer affects: linux (Ubuntu)
>
> ** Project changed: linux => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
> ** Attachment removed: "WifiSyslog.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889675/+attachment/4521830/+files/WifiSyslog.txt
>
> ** Attachment removed: "UdevDb.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889675/+attachment/4521829/+files/UdevDb.txt
>
> ** Attachment removed: "RfKill.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889675/+attachment/4521828/+files/RfKill.txt
>
> ** Attachment removed: "ProcModules.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889675/+attachment/4521827/+files/ProcModules.txt
>
> ** Attachment removed: "ProcInterrupts.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889675/+attachment/4521826/+files/ProcInterrupts.txt
>
> ** Attachment removed: "ProcCpuinfo.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889675/+attachment/4521825/+files/ProcCpuinfo.txt
>
> ** Attachment removed: "Lspci.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889675/+attachment/4521824/+files/Lspci.txt
>
> ** Attachment removed: "JournalErrors.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889675/+attachment/4521823/+files/JournalErrors.txt
>
> ** Attachment removed: "IwConfig.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889675/+attachment/4521822/+files/IwConfig.txt
>
> ** Attachment removed: "CRDA.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889675/+attachment/4521821/+files/CRDA.txt
>
> ** Attachment removed: "AlsaInfo.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889675/+attachment/4521820/+files/AlsaInfo.txt
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/889675
>
> Title:
> ieee80211 phy0: START: tid 1 is not agg'able
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> Thousands of these error messages are clogging my syslog:
>
>
> Nov 12 19:29:59 buk kernel: [ 8284.976165] ieee80211 phy0: START: tid 1
> is not agg'able
> Nov 12 19:29:59 buk kernel: [ 8285.252159] ieee80211 phy0: START: tid 1
> is not agg'able
> Nov 12 19:29:59 buk kernel: [ 8285.364155] ieee80211 phy0: START: tid 1
> is not agg'able
> Nov 12 19:29:59 buk kernel: [ 8285.676170] ieee80211 phy0: START: tid 1
> is not agg'able
> Nov 12 19:29:59 buk kernel: [ 8285.772491] ieee80211 phy0: START: tid 1
> is not agg'able
> Nov 12 19:30:00 buk kernel: [ 8285.880156] ieee80211 phy0: START: tid 1
> is not agg'able
> Nov 12 19:30:00 buk ke...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.