Re: dhclient with if_wi&wep

From: Tai-hwa Liang <avatar_at_mmlab.cse.yzu.edu.tw>
Date: Sun, 9 Oct 2005 15:00:13 +0800 (CST)
On Sun, 9 Oct 2005, Norikatsu Shigemura wrote:
> 	dhclient with if_wi&WEP will freeze on 7-current.
>
> 	I am using following if_wi and WEP.
[...]
> Oct  8 22:01:08 pelsia kernel: <wi0: timeout in wi_cmd 0x0002; event status 0x8008
> Oct  8 22:01:08 pelsia kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8008
> Oct  8 22:01:08 pelsia kernel: wi0: wi_cmd: busy bit won't clear.
> Oct  8 22:01:08 pelsia kernel: wi0: init failed
> Oct  8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc00/0
> Oct  8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc81/0
> Oct  8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc85/0
> Oct  8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc2a/0
> Oct  8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc28/0
> Oct  8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc80/0
> Oct  8 22:01:08 pelsia kernel: wi0: failed to allocate 2372 bytes on NIC
> Oct  8 22:01:08 pelsia kernel: wi0: tx buffer allocation failed (error 12)
> Oct  8 22:01:08 pelsia kernel: wi0: interface not running
[...]

   Sometimes I run into this whilst running "ifconfig wi0 up" w/o if_wi.ko
loaded; that is, the "busy bit won't clear, init failed" happens to my
R40(builtin wi miniPCI) regardless of whether or not the WEP is enabled.

   It looks to me that the firmware doesn't ack. properly at that moment
(unfortunately I have no idea about how to fix this); however, the second
retry("kldunload if_wi" then "ifconfig wi0 up" again) works for me.

-- 
Cheers,

Tai-hwa Liang
Received on Sun Oct 09 2005 - 05:00:15 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:44 UTC