Skip to contentSkip to conversation

mac80211 : WARN at net/mac80211/rate.h:153

DISCUSSION Dave Young 5 participants 6 messages Jul 14, 2008 – Aug 12, 2008

lore
Share & tools
lore

Dave Young

author
#0 lore raw

Hi,
I get warnings when I run
dhcpcd wlan0
The driver using is ath5k

warnings like following:

------------[ cut here ]------------
WARNING: at net/mac80211/rate.h:153 rate_control_pid_rate_init+0x7a/0xa0 [mac80211]()
Modules linked in: radeon drm snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss rfcomm l2cap bluetooth vfat fuse snd_hda_intel ath5k mac80211 rtc_cmos rtc_core rtc_lib psmouse snd_pcm snd_timer snd_page_alloc snd_hwdep 3c59x intel_agp snd e100 cfg80211 i2c_i801 serio_raw mii soundcore agpgart thermal processor button thermal_sys evdev sg
Pid: 0, comm: swapper Tainted: G        W 2.6.26-smp #1
 [<c0127954>] warn_on_slowpath+0x54/0x70
 [<c0177000>] ? print_trailer+0xa0/0xf0
 [<c0177071>] ? check_bytes_and_report+0x21/0xc0
 [<c0177452>] ? check_object+0xe2/0x1e0
 [<c0178117>] ? __slab_alloc+0x3a7/0x4c0
 [<f8d6a196>] ? rate_control_pid_alloc_sta+0x16/0x50 [mac80211]
 [<f8d6a2ba>] rate_control_pid_rate_init+0x7a/0xa0 [mac80211]
 [<f8d4fcf7>] ieee80211_ibss_add_sta+0xc7/0x110 [mac80211]
 [<f8d5a377>] __ieee80211_rx_handle_packet+0x417/0x7b0 [mac80211]
 [<c0177071>] ? check_bytes_and_report+0x21/0xc0
 [<f8d5c845>] __ieee80211_rx+0x185/0x560 [mac80211]
 [<c0109769>] ? read_tsc+0x9/0x30
 [<f89199dc>] ? ath5k_hw_get_tsf64+0x4c/0x90 [ath5k]
 [<f89161e3>] ath5k_tasklet_rx+0xf3/0x710 [ath5k]
 [<c0141f1d>] ? clocksource_get_next+0x3d/0x50
 [<c01408ad>] ? update_wall_time+0x28d/0x800
 [<f8919712>] ? ath5k_hw_is_intr_pending+0x22/0x50 [ath5k]
 [<c012d019>] tasklet_action+0x49/0xb0
 [<c012cae6>] __do_softirq+0x76/0xf0
 [<c012cb9b>] do_softirq+0x3b/0x50
 [<c012cf5c>] irq_exit+0x5c/0x70
 [<c0106995>] do_IRQ+0x45/0x80
 [<c012cf55>] ? irq_exit+0x55/0x70
 [<c011288b>] ? smp_apic_timer_interrupt+0x5b/0x90
 [<c010a220>] ? mwait_idle+0x0/0x40
 [<c0104623>] common_interrupt+0x23/0x28
 [<c010a220>] ? mwait_idle+0x0/0x40
 [<c010a252>] ? mwait_idle+0x32/0x40
 [<c01026db>] cpu_idle+0x5b/0xc0
 [<c042054e>] rest_init+0x4e/0x60
 =======================
---[ end trace de545485c8f84982 ]---
#1 lore raw

CCing PID guys.
I've seen several people hitting this. What's the meaning of this warning?

Quoted 49 lines · On Monday 14 July 2008 09:50:10 Dave Young wrote:

Hi,
I get warnings when I run
dhcpcd wlan0
The driver using is ath5k

warnings like following:

------------[ cut here ]------------
WARNING: at net/mac80211/rate.h:153 rate_control_pid_rate_init+0x7a/0xa0 [mac80211]()
Modules linked in: radeon drm snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss rfcomm l2cap bluetooth vfat fuse snd_hda_intel ath5k mac80211 rtc_cmos rtc_core rtc_lib psmouse snd_pcm snd_timer snd_page_alloc snd_hwdep 3c59x intel_agp snd e100 cfg80211 i2c_i801 serio_raw mii soundcore agpgart thermal processor button thermal_sys evdev sg
Pid: 0, comm: swapper Tainted: G        W 2.6.26-smp #1
 [<c0127954>] warn_on_slowpath+0x54/0x70
 [<c0177000>] ? print_trailer+0xa0/0xf0
 [<c0177071>] ? check_bytes_and_report+0x21/0xc0
 [<c0177452>] ? check_object+0xe2/0x1e0
 [<c0178117>] ? __slab_alloc+0x3a7/0x4c0
 [<f8d6a196>] ? rate_control_pid_alloc_sta+0x16/0x50 [mac80211]
 [<f8d6a2ba>] rate_control_pid_rate_init+0x7a/0xa0 [mac80211]
 [<f8d4fcf7>] ieee80211_ibss_add_sta+0xc7/0x110 [mac80211]
 [<f8d5a377>] __ieee80211_rx_handle_packet+0x417/0x7b0 [mac80211]
 [<c0177071>] ? check_bytes_and_report+0x21/0xc0
 [<f8d5c845>] __ieee80211_rx+0x185/0x560 [mac80211]
 [<c0109769>] ? read_tsc+0x9/0x30
 [<f89199dc>] ? ath5k_hw_get_tsf64+0x4c/0x90 [ath5k]
 [<f89161e3>] ath5k_tasklet_rx+0xf3/0x710 [ath5k]
 [<c0141f1d>] ? clocksource_get_next+0x3d/0x50
 [<c01408ad>] ? update_wall_time+0x28d/0x800
 [<f8919712>] ? ath5k_hw_is_intr_pending+0x22/0x50 [ath5k]
 [<c012d019>] tasklet_action+0x49/0xb0
 [<c012cae6>] __do_softirq+0x76/0xf0
 [<c012cb9b>] do_softirq+0x3b/0x50
 [<c012cf5c>] irq_exit+0x5c/0x70
 [<c0106995>] do_IRQ+0x45/0x80
 [<c012cf55>] ? irq_exit+0x55/0x70
 [<c011288b>] ? smp_apic_timer_interrupt+0x5b/0x90
 [<c010a220>] ? mwait_idle+0x0/0x40
 [<c0104623>] common_interrupt+0x23/0x28
 [<c010a220>] ? mwait_idle+0x0/0x40
 [<c010a252>] ? mwait_idle+0x32/0x40
 [<c01026db>] cpu_idle+0x5b/0xc0
 [<c042054e>] rest_init+0x4e/0x60
 =======================
---[ end trace de545485c8f84982 ]---

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 1 line
Greetings Michael.
#2 lore raw
Quoted 2 lines · Michael Buesch

CCing PID guys.
I've seen several people hitting this. What's the meaning of this warning?

It basically means the rate control cannot find any rate in local->hw.wiphy->bands[local->hw.conf.channel->band] that is supported by the sta in question. Normally this should not happen. I guess the reason is that the supported rates bits in the sta info are all zero, which would probably be a bug. I haven't seen this here, but I don't use the IBSS code either. To further investigate this, you could the following just before the WARN_ON:

printk(KERN_DEBUG "supported rates bitmask: %08x\n",

	sta->supp_rates[sband->band]);

Mattias

author
#3 lore raw
Quoted 12 lines · Mattias Nissler
Quoted 2 lines · Michael Buesch

CCing PID guys.
I've seen several people hitting this. What's the meaning of this warning?

It basically means the rate control cannot find any rate in local->hw.wiphy->bands[local->hw.conf.channel->band] that is supported by the sta in question. Normally this should not happen. I guess the reason is that the supported rates bits in the sta info are all zero, which would probably be a bug. I haven't seen this here, but I don't use the IBSS code either. To further investigate this, you could the following just before the WARN_ON:

Quoted 2 lines

printk(KERN_DEBUG "supported rates bitmask: %08x\n",

       sta->supp_rates[sband->band]);

Yes, as you said, I get:

supported rates bitmask: 00000000

Quoted 4 lines

Mattias

Signature · 2 lines
Regards
dave
#4 lore raw
Quoted 11 lines · Dave Young
Quoted 10 lines · Mattias Nissler
Quoted 2 lines · Michael Buesch

CCing PID guys.
I've seen several people hitting this. What's the meaning of this warning?

It basically means the rate control cannot find any rate in local->hw.wiphy->bands[local->hw.conf.channel->band] that is supported by the sta in question. Normally this should not happen. I guess the reason is that the supported rates bits in the sta info are all zero, which would probably be a bug. I haven't seen this here, but I don't use the IBSS code either. To further investigate this, you could the following just before the WARN_ON:

This has been solved already:

http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commitdiff;h=def5e9a210235d690e79ae660972792860568421

Vlado

Quoted 14 lines
Quoted 3 lines

printk(KERN_DEBUG "supported rates bitmask: %08x\n",

       sta->supp_rates[sband->band]);

Yes, as you said, I get:

supported rates bitmask: 00000000

Quoted 3 lines

Mattias

#5 lore raw
Quoted 14 lines · Vladimir Koutny
Quoted 11 lines · Dave Young
Quoted 10 lines · Mattias Nissler
Quoted 2 lines · Michael Buesch

CCing PID guys.
I've seen several people hitting this. What's the meaning of this warning?

It basically means the rate control cannot find any rate in local->hw.wiphy->bands[local->hw.conf.channel->band] that is supported by the sta in question. Normally this should not happen. I guess the reason is that the supported rates bits in the sta info are all zero, which would probably be a bug. I haven't seen this here, but I don't use the IBSS code either. To further investigate this, you could the following just before the WARN_ON:

Quoted 5 lines

This has been solved already:

http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commitdiff;h=def5e9a210235d690e79ae660972792860568421

Vlado

This pacth is wrong it causes that all IBSS traffic is transmitted rate of BEACON (1MBit) , which is pretty bad performance like. We are working on possible fixes.
Tomas

Quoted 4 lines
Quoted 1 line