Opened 16 years ago
Closed 16 years ago
#23 closed defect (fixed)
wi0: device timeout > wi_cmd: busy bit won't clear > wi0: link state changed to DOWN
Reported by: | tim | Owned by: | tim |
---|---|---|---|
Priority: | major | Milestone: | |
Keywords: | Cc: | huub | |
Resource needed to fix: |
Description
I noted the following events in the log/messages of CNodeHuub.
2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: device timeout 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: device timeout 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: timeout in wi_cmd 0x0002; event status 0x8000 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: timeout in wi_cmd 0x0002; event status 0x8000 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8000 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8000 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: wi_cmd: busy bit won't clear. 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: wi_cmd: busy bit won't clear. 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: init failed 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: init failed 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: failed to allocate 2372 bytes on NIC 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: failed to allocate 2372 bytes on NIC 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: tx buffer allocation failed (error 12) 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: tx buffer allocation failed (error 12) 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: interface not running 2009 Mar 17 18:41:51 <kern.crit> kernel: wi0: interface not running 2009 Mar 17 18:41:51 <kern.notice> kernel: wi0: link state changed to DOWN 2009 Mar 17 18:41:51 <kern.notice> kernel: wi0: link state changed to DOWN
After that wi0 doesn't come up anymore. According to a previous email from Huub, the wi0 interface has the following specifications:
mini-pci senao with a prism2.5 chipset,
firmware version P 1.1.0 S 1.4.9
googling it up states some problems with older firmware versions, but i didn't really find any relevant topics for the problem at hand.
Change History (2)
comment:1 by , 16 years ago
Cc: | added |
---|---|
version: | → 0.9.2 |
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Ik heb de firmware geflashd en het kaartje vervangen:
wi0: <Intersil Prism2.5> mem 0xa0000000-0xa0000fff irq 10 at device 16.0 on pci0
wi0: [ITHREAD]
wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
wi0: Intersil Firmware: Primary (1.1.1), Station (1.8.2)
wi0: Ethernet address: 00:02:6f:4a:cd:f5
P1.1.1 and S1.5.4 was chosen a long time ago as being the stable firmware release to use. Reason unknown, but some testing had been done in order to verify this.
Firmware to be found at: http://www.red-bean.com/~proski/firmware/readme.html (please don't put firmware into subversion, due to legal rights)
Flashing instructions at (linux/windows): http://linux.junsun.net/intersil-prism/ We also have been doing it the windows way, but the Linux way also looks promising (at least much more stable than years before)
They suggest using P1.1.1 S.1.8.2 (WPA support(!)). So I would say give it a try, as some bonus features would always be nice :-).
Huub (in CC), could you do the flashing?