local_bh_enable() was called in hard irq context. This is probably a bug

Kyle Rose krose+hostap at krose.org
Sun Nov 16 16:15:09 EST 2003


Installed linux-2.6.0-test9-mm3 on a new Thinkpad T40 today, and
compiled the hostap 0.1.2 modules.  Got an interesting set of error
messages:

hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
hostap_cs: Registered netdevice wlan0
prism2_hw_init: initialized in 194 ms
wlan0: trying to read PDA from 0x007f0000: OK
wlan0: NIC: id=0x801b v1.0.0
wlan0: PRI: id=0x15 v1.1.1
wlan0: STA: id=0x1f v1.7.4
local_bh_enable() was called in hard irq context.   This is probably a bug
Call Trace:
 [<c0120e79>] local_bh_enable+0x79/0x80
 [<d09963d9>] prism2_transmit_cb+0x99/0xe0 [hostap_cs]
 [<c024c558>] dev_queue_xmit+0x1d8/0x270
 [<d09967f4>] prism2_cmd_ev+0x314/0x400 [hostap_cs]
 [<d09995ee>] prism2_interrupt+0x29e/0x350 [hostap_cs]
 [<c0124f79>] run_timer_softirq+0xb9/0x190
 [<c010c789>] handle_IRQ_event+0x49/0x80
 [<c010ca7e>] do_IRQ+0x6e/0xf0
 [<c0107000>] _stext+0x0/0x30
 [<c02ac9c4>] common_interrupt+0x18/0x20
 [<c0107000>] _stext+0x0/0x30
 [<c0109053>] default_idle+0x23/0x40
 [<c01090e4>] cpu_idle+0x34/0x40
 [<c035a6fb>] start_kernel+0x13b/0x150
 [<c035a470>] unknown_bootoption+0x0/0x120

prism2: wlan0: operating mode changed 3 -> 2
wlan0: LinkStatus=2 (Disconnected)
wlan0: LinkStatus: BSSID=00:06:25:ab:9d:84
wlan0 (WE) : Buffer for request 8B1B too small (0<4)
local_bh_enable() was called in hard irq context.   This is probably a bug
Call Trace:
 [<c0120e79>] local_bh_enable+0x79/0x80
 [<d09963d9>] prism2_transmit_cb+0x99/0xe0 [hostap_cs]
 [<c0118e68>] recalc_task_prio+0xa8/0x1d0
 [<d09967f4>] prism2_cmd_ev+0x314/0x400 [hostap_cs]
 [<d09995ee>] prism2_interrupt+0x29e/0x350 [hostap_cs]
 [<c0124f79>] run_timer_softirq+0xb9/0x190
 [<c010c789>] handle_IRQ_event+0x49/0x80
 [<c010ca7e>] do_IRQ+0x6e/0xf0
 [<c0107000>] _stext+0x0/0x30
 [<c02ac9c4>] common_interrupt+0x18/0x20
 [<c0107000>] _stext+0x0/0x30
 [<c0109053>] default_idle+0x23/0x40
 [<c01090e4>] cpu_idle+0x34/0x40
 [<c035a6fb>] start_kernel+0x13b/0x150
 [<c035a470>] unknown_bootoption+0x0/0x120

wlan0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
   retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
   A1=44:44:44:44:44:44 A2=00:06:25:ab:9d:84 A3=44:44:44:44:44:44 A4=00:00:00:00:00:00
local_bh_enable() was called in hard irq context.   This is probably a bug
Call Trace:
 [<c0120e79>] local_bh_enable+0x79/0x80
 [<d09963d9>] prism2_transmit_cb+0x99/0xe0 [hostap_cs]
 [<d09967f4>] prism2_cmd_ev+0x314/0x400 [hostap_cs]
 [<d09995ee>] prism2_interrupt+0x29e/0x350 [hostap_cs]
 [<d09b0510>] addrconf_dad_timer+0x0/0x170 [ipv6]
 [<c0124f79>] run_timer_softirq+0xb9/0x190
 [<c010c789>] handle_IRQ_event+0x49/0x80
 [<c010ca7e>] do_IRQ+0x6e/0xf0
 [<c0107000>] _stext+0x0/0x30
 [<c02ac9c4>] common_interrupt+0x18/0x20
 [<c0107000>] _stext+0x0/0x30
 [<c0109053>] default_idle+0x23/0x40
 [<c01090e4>] cpu_idle+0x34/0x40
 [<c035a6fb>] start_kernel+0x13b/0x150
 [<c035a470>] unknown_bootoption+0x0/0x120


And this goes on and on until I remove the card.  xsupplicant cannot
complete its request, or at least the hostap master thinks so.

Clues?

Kyle



More information about the HostAP mailing list