madwifi && v2.6.26-rc4

madwifi && v2.6.26-rc4

[Oliver Pinter]

Hi all!

os: debian lenny
madwifi 0.9.3.3

CONFIG_ATHEROS=y
# CONFIG_ATHEROS_RATE_DEFAULT_AMRR is not set
# CONFIG_ATHEROS_RATE_DEFAULT_ONOE is not set
CONFIG_ATHEROS_RATE_DEFAULT_SAMPLE=y
CONFIG_ATHEROS_RATE_DEFAULT="sample"
# CONFIG_ATHEROS_RATE_AMRR is not set
# CONFIG_ATHEROS_RATE_ONOE is not set
CONFIG_ATHEROS_RATE_SAMPLE=y


linux-2.6 head on: 2548baa07ddf37ea8604e9627f042616d1cdc43e
lockdep enabled

CONFIG_LOCKDEP_SUPPORT=y
CONFIG_LOCKDEP=y
CONFIG_DEBUG_LOCKDEP=y

=================================
[ INFO: inconsistent lock state ]
2.6.26-rc3-git8-00438-g61f522f #1
---------------------------------
inconsistent {in-softirq-W} -> {softirq-on-W} usage.
wpa_supplicant/2846 [HC0[0]:SC0[0]:HE1:SE1] takes:
 (&st->st_lock){-+..}, at: [<c039d4f0>] sta_iterate+0x38/0x99
{in-softirq-W} state was registered at:
  [<c0143d81>] __lock_acquire+0x361/0x10cb
  [<c0144b67>] lock_acquire+0x7c/0x96
  [<c039e488>] sta_add+0x49/0x48a
  [<c0505d44>] _spin_lock+0x2c/0x55
  [<c039e488>] sta_add+0x49/0x48a
  [<c039e43f>] sta_add+0x0/0x48a
  [<c039e488>] sta_add+0x49/0x48a
  [<c0142e39>] check_usage_forwards+0x19/0x42
  [<c014105b>] save_trace+0x37/0x91
  [<c039e43f>] sta_add+0x0/0x48a
  [<c0390b85>] ieee80211_add_scan+0x74/0x240
  [<c010b427>] save_stack_trace+0x28/0x43
  [<c0143c8c>] __lock_acquire+0x26c/0x10cb
  [<c017a045>] add_partial+0xe/0x53
  [<c038557a>] ieee80211_recv_mgmt+0x2585/0x483b
  [<c0505c57>] _spin_unlock+0x14/0x1c
  [<c014340d>] mark_held_locks+0x45/0x76
  [<c017c481>] kmem_cache_free+0x8f/0xb4
  [<c0143549>] trace_hardirqs_on+0x78/0x132
  [<c038b757>] ieee80211_hardstart+0x32/0x37c
  [<c038b757>] ieee80211_hardstart+0x32/0x37c
  [<c038b757>] ieee80211_hardstart+0x32/0x37c
  [<c0109075>] native_sched_clock+0x66/0xa1
  [<c0134b63>] __kernel_text_address+0x5/0xe
  [<c0358747>] ath_recv_mgmt+0x43/0x1c3
  [<c0143c8c>] __lock_acquire+0x26c/0x10cb
  [<c0358704>] ath_recv_mgmt+0x0/0x1c3
  [<c03821aa>] ieee80211_input+0xa34/0x17fb
  [<c0109075>] native_sched_clock+0x66/0xa1
  [<c0506295>] _spin_unlock_irqrestore+0x34/0x39
  [<c0382fb9>] ieee80211_input_all+0x48/0x84
  [<c035e3a7>] ath_rx_tasklet+0x7e5/0x817
  [<c034f46a>] skge_intr+0x143/0x465
  [<c0129dbc>] tasklet_action+0x2e/0xbf
  [<c0129ddb>] tasklet_action+0x4d/0xbf
  [<c01298bb>] __do_softirq+0x85/0xf9
  [<c0129985>] do_softirq+0x56/0x58
  [<c0129d21>] irq_exit+0x64/0x75
  [<c010658e>] do_IRQ+0x4a/0x94
  [<c01026b3>] default_idle+0x0/0x4c
  [<c010447c>] common_interrupt+0x24/0x34
  [<c01026b3>] default_idle+0x0/0x4c
  [<c0104486>] common_interrupt+0x2e/0x34
  [<c01026b3>] default_idle+0x0/0x4c
  [<c01026eb>] default_idle+0x38/0x4c
  [<c010260b>] cpu_idle+0x5d/0x9d
  [<ffffffff>] 0xffffffff
irq event stamp: 781
hardirqs last  enabled at (781): [<c017c892>] __kmalloc+0x60/0xe8
hardirqs last disabled at (780): [<c017c868>] __kmalloc+0x36/0xe8
softirqs last  enabled at (710): [<c04d6c92>] packet_poll+0x5a/0x65
softirqs last disabled at (708): [<c0505d79>] _spin_lock_bh+0xc/0x5a

other info that might help us debug this:
2 locks held by wpa_supplicant/2846:
 #0:  (rtnl_mutex){--..}, at: [<c04f60dc>] wext_handle_ioctl+0x3e/0x3f9
 #1:  (&st->st_scanlock){--..}, at: [<c039d4d8>] sta_iterate+0x20/0x99

stack backtrace:
Pid: 2846, comm: wpa_supplicant Not tainted 2.6.26-rc3-git8-00438-g61f522f #1
 [<c0142116>] print_usage_bug+0x13c/0x146
 [<c014324d>] mark_lock+0x3eb/0x566
 [<c0143dc0>] __lock_acquire+0x3a0/0x10cb
 [<c039d4d8>] sta_iterate+0x20/0x99
 [<c0144b67>] lock_acquire+0x7c/0x96
 [<c039d4f0>] sta_iterate+0x38/0x99
 [<c0505d44>] _spin_lock+0x2c/0x55
 [<c039d4f0>] sta_iterate+0x38/0x99
 [<c039d4f0>] sta_iterate+0x38/0x99
 [<c0397ad9>] giwscan_cb+0x0/0x907
 [<c0397ad9>] giwscan_cb+0x0/0x907
 [<c039081f>] ieee80211_scan_iterate+0x18/0x1f
 [<c0392dc0>] ieee80211_ioctl_giwscan+0x50/0xa9
 [<c04f5ed6>] ioctl_standard_call+0x182/0x34a
 [<c04f60dc>] wext_handle_ioctl+0x3e/0x3f9
 [<c04f60dc>] wext_handle_ioctl+0x3e/0x3f9
 [<c04f63fd>] wext_handle_ioctl+0x35f/0x3f9
 [<c0392d70>] ieee80211_ioctl_giwscan+0x0/0xa9
 [<c0392d70>] ieee80211_ioctl_giwscan+0x0/0xa9
 [<c02a0af7>] inode_has_perm+0x48/0x70
 [<c042e3d1>] dev_ioctl+0x4b4/0x51f
 [<c0109075>] native_sched_clock+0x66/0xa1
 [<c0423661>] sock_ioctl+0x0/0x17f
 [<c018a8ff>] vfs_ioctl+0x1f/0x6d
 [<c018ab8b>] do_vfs_ioctl+0x23e/0x287
 [<c018ac2a>] sys_ioctl+0x56/0x64
 [<c0103a09>] sysenter_past_esp+0x6a/0xb1
 =======================


-- 
Thanks,
Oliver

Re: madwifi && v2.6.26-rc4

[Arjan van de Ven]

On Tue, 27 May 2008 17:20:23 +0200
"Oliver Pinter" <oliver.pntr@gmail.com> wrote:

> Hi all!
> 
> os: debian lenny
> madwifi 0.9.3.3


you probably want to use ath5k instead since you're posting to this
list.....



-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

Re: madwifi && v2.6.26-rc4

[Oliver Pinter]

jah, i know, that the ath5k is the official driver, but ath5k don't
supported WPA2-PSK.
I cc-ed mrenzmann, hi is the madiwifi webmaster / maintainer

On 5/27/08, Arjan van de Ven <arjan@infradead.org> wrote:
> On Tue, 27 May 2008 17:20:23 +0200
> "Oliver Pinter" <oliver.pntr@gmail.com> wrote:
>
>> Hi all!
>>
>> os: debian lenny
>> madwifi 0.9.3.3
>
>
> you probably want to use ath5k instead since you're posting to this
> list.....
>
>
>
> --
> If you want to reach me at my work email, use arjan@linux.intel.com
> For development, discussion and tips for power savings,
> visit http://www.lesswatts.org
>


-- 
Thanks,
Oliver

Re: madwifi && v2.6.26-rc4

[Arjan van de Ven]

On Wed, 28 May 2008 01:23:06 +0200
"Oliver Pinter" <oliver.pntr@gmail.com> wrote:

> On 5/27/08, Arjan van de Ven <arjan@infradead.org> wrote:
> > On Tue, 27 May 2008 17:20:23 +0200
> > "Oliver Pinter" <oliver.pntr@gmail.com> wrote:
> >
> >> Hi all!
> >>
> >> os: debian lenny
> >> madwifi 0.9.3.3
> >
> >
> > you probably want to use ath5k instead since you're posting to this
> > list.....

> jah, i know, that the ath5k is the official driver, but ath5k don't
> supported WPA2-PSK.
> I cc-ed mrenzmann, hi is the madiwifi webmaster / maintainer


but you posted to the linux-kernel mailing list, which is about an open
source project.... if you want to ask questions about proprietary
stuff, you're just better off asking the vendor of said module.... not
lkml, for which your question is basically off-topic.


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

Re: madwifi && v2.6.26-rc4

[Michael Renzmann]

Hi.

> jah, i know, that the ath5k is the official driver, but ath5k don't
> supported WPA2-PSK.
> I cc-ed mrenzmann, hi is the madiwifi webmaster / maintainer

I'm not "the maintainer" of MadWifi, just one of the guys working on the
project.

I agree with Arjan that this report is off-topic on lkml, since MadWifi is
not part of the Linux kernel. Please report this either via our bugtracker
or via one of the MadWifi-related mailing lists (see
http://madwifi.org/wiki/Resources).

Bye, Mike