Date: Fri, 12 Dec 2003 11:34:34 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: mobile@freebsd.org Subject: Still problems with Lucent wi0 (was: I think I wounded by Prism card) Message-ID: <20031212010434.GY81968@wantadilla.lemis.com> In-Reply-To: <20031211.132647.55844740.imp@bsdimp.com> References: <20031211182330.0D26C5D04@ptavv.es.net> <20031211.132647.55844740.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--8M+BMcg+0CmQ2H7L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 11 December 2003 at 13:26:47 -0700, M. Warner Losh wrote: > In message: <20031211182330.0D26C5D04@ptavv.es.net> > "Kevin Oberman" <oberman@es.net> writes: >> >> I have an IBM ThinkPad T30 running CURRENT as of 12/9/03. On that day I >> also updated the firmware on my WiFi card from 1.3.6 to 1.4.9 and my >> troubles began. My wireless card starts and associated normally and runs >> fine until I start a large transfer (such as an scp of a file of a MB or >> so). Then I get the dreaded: >> wi0: timeout in wi_cmd -x010b; event status 0x8000 > > That sucks. I assume no other wi messages before that? And that the > - is really a 0 and you typed it in by hand. Was this under heavy > load? FWIW, another data point. At some point in the last few months my last problems with Lucent cards went away, I thought. Then I put a different card in and had problems again: the boot wouldn't complete. Here are the results of the two probes: Dec 12 11:04:06 adelaide kernel: wi0: <Lucent Technologies WaveLAN/IEEE> at port 0x100-0x13f irq 10 function 0 config 1 on pccard0 Dec 12 11:04:06 adelaide kernel: wi0: 802.11 address: 00:02:2d:04:09:3a Dec 12 11:04:06 adelaide kernel: wi0: using Lucent Technologies, WaveLAN/IEEE Dec 12 11:04:06 adelaide kernel: wi0: Lucent Firmware: Station (6.6.1) Dec 12 11:04:06 adelaide kernel: wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Dec 12 11:04:06 adelaide kernel: wi0: bad alloc 4c2 != ff, cur 0 nxt 0 Despite the error message, this card works fine. The other one is: Dec 11 11:49:14 adelaide kernel: wi0: 802.11 address: 00:02:2d:28:d3:6e Dec 11 11:49:14 adelaide kernel: wi0: using Lucent Technologies, WaveLAN/IEEE Dec 11 11:49:14 adelaide kernel: wi0: Lucent Firmware: Station (6.16.1) Dec 11 11:49:14 adelaide kernel: wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Dec 11 11:49:23 adelaide kernel: wi0: bad alloc 1cd != ea, cur 0 nxt 0 Dec 11 11:49:27 adelaide kernel: wi0: bad alloc 633 != 1e3, cur 0 nxt 0 This one continues with messages like: Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_cmd 0x0002; event status 0x8080 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_cmd 0x0121; event status 0x8080 Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. Dec 12 11:26:40 adelaide last message repeated 11 times Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc0e/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc85/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc20/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc80/0 Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. This continues until I remove the card, when I get Dec 12 11:26:40 adelaide kernel: wi0: failed to allocate 2372 bytes on NIC Dec 12 11:26:40 adelaide kernel: wi0: tx buffer allocation failed (error 12) Dec 12 11:26:40 adelaide kernel: wi0: interface not running Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc00/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc81/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc0c/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc02/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc03/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc04/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc01/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc09/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc07/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc83/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc06/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc25/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc84/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc0e/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc85/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc20/0 Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc80/0 Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. Dec 12 11:26:40 adelaide kernel: wi0: failed to allocate 2372 bytes on NIC Dec 12 11:26:40 adelaide kernel: wi0: tx buffer allocation failed (error 12) Dec 12 11:26:40 adelaide kernel: wi0: interface not running Dec 12 11:26:40 adelaide kernel: wi0: wi_cmd: busy bit won't clear. Dec 12 11:26:40 adelaide kernel: wi0: timeout in wi_seek to fc80/0 Dec 12 11:26:40 adelaide kernel: wi0: detached After the final message, the system unlocks. Apart from the different firmware level, the second card has only 40 bit WEP, while the first one has 104 bit WEP. I'm not too fussed about the situation, since the gold card works fine, but if you want me to try something out, I can do so. Greg -- See complete headers for address and phone numbers. --8M+BMcg+0CmQ2H7L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/2RQiIubykFB6QiMRAsr/AJ4mKkv/9TvyQxaDHWyo45di9I/KfgCfakCD fA+aFhC5CZ/zqR43bQyraIg= =8unQ -----END PGP SIGNATURE----- --8M+BMcg+0CmQ2H7L--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031212010434.GY81968>