iwlagn log spam

DISCUSSION pat-lkml 2 participants 4 messages May 20, 2011 – May 21, 2011

Share & tools

wwguy

2011-05-20 21:11 UTC #1 lore raw

Hi Pat,

Quoted 46 lines · pat-lkml

Resend(oops, never setup plain text vs html on this machine)
I've been getting spammed with:
iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = 00:0c:42:64:bb:1d tid = 0
Every 35s for the 16 hours my machine has been up:
anvil $ uname -a
Linux anvil 2.6.39-gentoo #1 SMP PREEMPT Fri May 20 01:53:54 EDT 2011 x86_64 Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz GenuineIntel GNU/Linux
anvil $ dmesg | grep iwlagn_tx_agg_start | wc -l
1621
anvil $ uptime
16:44:40 up 14:49, 3 users, load average: 1.11, 0.82, 0.48
Is there a good reason to print this message? Is it indicative of a problem? Everything works fine.
Here's a little dmesg info from my system:
anvil $ dmesg | grep iwlagn | grep -v iwlagn_tx_agg_start
[    3.675798] iwlagn: Intel(R) Wireless WiFi Link AGN driver for
Linux, in-tree:
[    3.675802] iwlagn: Copyright(c) 2003-2010 Intel Corporation
[    3.675877] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low)
-> IRQ 17
[    3.675893] iwlagn 0000:03:00.0: setting latency timer to 64
[    3.675983] iwlagn 0000:03:00.0: Detected Intel(R) Centrino(R)
Advanced-N + WiMAX 6250 AGN, REV=0x84
[    3.688288] iwlagn 0000:03:00.0: device EEPROM VER=0x540, CALIB=0x6
[    3.688290] iwlagn 0000:03:00.0: Device SKU: 0Xb
[    3.688306] iwlagn 0000:03:00.0: Tunable channels: 13 802.11bg,
24 802.11a channels
[    3.688373] iwlagn 0000:03:00.0: irq 57 for MSI/MSI-X
[    3.697702] iwlagn 0000:03:00.0: loaded firmware version
41.28.5.1 build 33926
[    3.760104] iwlagn 0000:03:00.0: wlan0: Features changed:
0x00004800 -> 0x00004000
[   32.590823] iwlagn 0000:03:00.0: Aggregation not enabled for tid
0 because load = 2
[  330.931071] iwlagn 0000:03:00.0: Aggregation not enabled for tid

Quoted 2 lines

0 because load = 9

Just want to be clear, which message flooding your system? is
iwlagn 0000:03:00.0: Aggregation not enabled for tid

Quoted 1 line

0 because load = 9

or
iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = 00:0c:42:64:bb:1d

Quoted 2 lines

tid = 0

the second message should only show once when the aggregation being establish. if you are seeing it every 35 seconds, that is bad. but the first message is checking the traffic load is high enough to establish the aggregation queue, which is ok. and we should not log this type of message as "ERROR", I will submit a patch to change that.

Wey

Quoted 1 line

Pat Erley

author

2011-05-20 21:27 UTC #2 lore raw

Quoted 7 lines · wwguy

Hi Pat,
Just want to be clear, which message flooding your system? is
iwlagn 0000:03:00.0: Aggregation not enabled for tid
Quoted 1 line
0 because load = 9

This I only see occasionally.

Quoted 3 lines

or
iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = 00:0c:42:64:bb:1d
Quoted 1 line
tid = 0

This message is the one that I've gotten over 1600 of in 16 hours.

Quoted 5 lines

Quoted 1 line
the second message should only show once when the aggregation being establish. if you are seeing it every 35 seconds, that is bad. but the first message is checking the traffic load is high enough to establish the aggregation queue, which is ok. and we should not log this type of message as "ERROR", I will submit a patch to change that.

Feel free to include me in on the CC for that patch. Will test.

Pat

wwguy

2011-05-21 16:54 UTC #3 lore raw

Hi Pat,

Quoted 18 lines · Pat Erley

Quoted 7 lines · wwguy
Hi Pat,
Just want to be clear, which message flooding your system? is
iwlagn 0000:03:00.0: Aggregation not enabled for tid
Quoted 1 line
0 because load = 9
This I only see occasionally.
Quoted 3 lines
or
iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = 00:0c:42:64:bb:1d
Quoted 1 line
tid = 0
This message is the one that I've gotten over 1600 of in 16 hours.
Quoted 1 line
Quoted 1 line

Quoted 7 lines

Quoted 4 lines
the second message should only show once when the aggregation being establish. if you are seeing it every 35 seconds, that is bad. but the first message is checking the traffic load is high enough to establish the aggregation queue, which is ok. and we should not log this type of message as "ERROR", I will submit a patch to change that.
Feel free to include me in on the CC for that patch. Will test.

It is not the normal behavior you are seeing over 1600 aggregation attempt in 16 hours.
Could you please help me to debug this with following debug flag

$sudo modprobe iwlagn debug=0x4100002

Thanks
Wey