[BUG] reproduceable PANIC in recent hostap driver

Jouni Malinen jkmaline
Sun Oct 19 18:01:53 PDT 2003

On Sun, Oct 19, 2003 at 09:23:40PM -0300, JuanJo Ciarlante wrote:

> System: P-166Mhz, linux-2.4.22, Debian 3.0r1, hostap-0.1.[01];
>         Prism2.5 DWL-520, PRI v1.1.1, STA v1.7.4
> Doing ifconfig wlan0 PANICs "immediatly" if ospfd (from zebra pkg) is running.

Do you mean 'ifconfig wlan0' or 'ifconfig wlan0 <something else,
like up>'?

> Oops always shows ospfd process paniced; I guess is something related to
> netlink stuff changed around 0.0.4 (I'd been getting panics but didn't find
> the possible cause, ... 'til today ;), ospfd holds a netlink socket to get
> reported about interface/routing/etc news.

Just monitoring the netlink messages with 'ip monitor all' is not enough
to trigger anything (at least on Linux 2.6.0-test8). Would you happen to
know what ospfd does after noticing a change in network devices? I would
assume it could be something like changing routing entries etc.

> Another interesting thing is that the panic is the infamous
> "Aieee killing interrupt handler"; given that it would seem to happen under
> process context --*always* ospfd--. 
> Obviously after that big red button is the only escape.
> Feeding ksymoops with hand written address (1st in the stack trace) gives
>   c0113509 <schedule+4d/314>

Could you please try to resolve couple of more functions from the back
trace? schedule() is not supposed to be called from interrupt handler,
so it is certainly not good sign.. I would like to know whether there
are any functions from Host AP in the back trace.

Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list