> If I scan by "iw dev wlan0 scan" while sending data through the
> interface, I get a BUG in net/mac80211/tx.c:
>
> /* RC is busted */
> if (WARN_ON_ONCE(info->control.rates[i].idx >=
> sband->n_bitrates)) {
> info->control.rates[i].idx = -1;
> continue;
> }
>
> I added this statement inside the condition:
>
> printk("idx = %d, bitrates = %d, i = %d\n", info->control.rates[i].idx,
> sband->n_bitrates, i);
>
> The result is:
>
> idx = 9, bitrates = 8, i = 0
> idx = 10, bitrates = 8, i = 1
> idx = 9, bitrates = 8, i = 2
>
> The card is 802.11a capable. My interpretation is that scanning
> switches to the 802.11a band temporarily, but doesn't stop transmission.
> When transmitting, the rate indices for 2.4 GHz band are checked against
> the number of rates in the 5 GHz band, which is indeed 8. There are 12
> rates in the 2.4 GHz band.
>
> ath5k 0000:0b:00.0: PCI INT A disabled
> ath5k 0000:0b:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> ath5k 0000:0b:00.0: setting latency timer to 64
> ath5k 0000:0b:00.0: registered as 'phy2'
> ath: Country alpha2 being used: US
> ath: Regpair detected: 0x3a
> phy2: Selected rate control algorithm 'minstrel'
> ath5k phy2: Atheros AR5414 chip found (MAC: 0xa3, PHY: 0x61)
>
> I actually had to patch the kernel, or the oops would escalate to a
> panic. Perhaps it's a good idea to have that check:
I don't think it's just ath5k... I had an oops too. I think some of the
pid/minstrel "fixes" broke it but don't know yet.
johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
