Search Linux Wireless

Re: soft-safe -> soft-unsafe lock order detected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2009-02-10 at 17:33 +0100, Gabor Juhos wrote:

> I'm testing the ath9k driver in STA mode on an Atheros AR913x based board.

>  (&local->sta_lock){.+..}
> ... which became soft-irq-safe at:
>   [<800b21cc>] __lock_acquire+0x5a8/0x844
>   [<800b24c4>] lock_acquire+0x5c/0x84
>   [<8006b980>] _spin_lock_irqsave+0x50/0x74
>   [<c020570c>] ieee80211_beacon_get+0x14c/0x3a4 [mac80211]
>   [<c0341e08>] ath9k_beacon_tasklet+0x304/0x5c4 [ath9k]

Something is mismatched here. STA mode != beaconing.

johannes

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux