Date: Tue, 19 Sep 2006 13:01:28 -0700 From: David King <dking@ketralnis.com> To: freebsd-hardware@freebsd.org Subject: wi0: timeout in wi_cmd 0x0002; event status 0x8000 Message-ID: <662BF2EB-7CC9-4145-83A4-F96974FA87FB@ketralnis.com>
next in thread | raw e-mail | index | archive | help
I have a wireless card on wi0 that occasionally cuts out. I get lines
in /var/log/messages that suggest that it's probably the wireless
card dying on me, but in case it's a problem that I can correct, here
are the messages that I get:
Sep 9 22:48:05 melchoir kernel: wi0: device timeout
Sep 9 22:48:05 melchoir kernel: wi0: timeout in wi_cmd 0x0002; event
status 0x8000
Sep 9 22:48:05 melchoir kernel: wi0: timeout in wi_cmd 0x0000; event
status 0x8000
Sep 9 22:48:05 melchoir kernel: wi0: wi_cmd: busy bit won't clear.
Sep 9 22:48:05 melchoir kernel: wi0: init failed
Sep 9 22:48:05 melchoir kernel: wi0: failed to allocate 2372 bytes
on NIC
Sep 9 22:48:05 melchoir kernel: wi0: tx buffer allocation failed
(error 12)
Sep 9 22:48:05 melchoir kernel: wi0: interface not running
It happens about once a week, usually when the wireless card is quite
active, like when transferring a large file. Sometimes I'll get quite
a few of these:
Sep 10 16:45:03 melchoir kernel: wi0: init failed
Sep 10 16:45:03 melchoir kernel: wi0: timeout in wi_seek to fc00/0
Sep 10 16:45:03 melchoir kernel: wi0: timeout in wi_seek to fc81/0
...
Sep 10 16:45:03 melchoir kernel: wi0: timeout in wi_seek to fc28/0
Sep 10 16:45:03 melchoir kernel: wi0: timeout in wi_seek to fc80/0
Sep 10 16:45:03 melchoir kernel: wi0: failed to allocate 2372 bytes
on NIC
Sep 10 16:45:03 melchoir kernel: wi0: tx buffer allocation failed
(error 12)
Sep 10 16:45:03 melchoir kernel: wi0: interface not running
The problem can't be cleared up by "ifconfig wi0 down; ifconfig wi0
up", nor by rebooting, I actually have to shut off the machine, wait
a few seconds, and power it back on. The card comes up in dmesg like
this:
wi0: <Intersil Prism2.5> mem 0x41300000-0x41300fff irq 11 at device
4.0 on pci0
wi0: [GIANT-LOCKED]
wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
wi0: Intersil Firmware: Primary (1.0.7), Station (1.3.6)
wi0: Ethernet address: 00:09:5b:40:b2:9f
and I'm running:
FreeBSD melchoir 6.1-RELEASE-p3 FreeBSD 6.1-RELEASE-p3 #1: Mon Aug 14
11:40:49 PDT 2006 root@melchoir:/usr/obj/usr/src/sys/MELCHOIR i386
It is running in hostap, like this:
wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::209:5bff:fe40:b29f%wi0 prefixlen 64 scopeid 0x2
inet 10.0.1.1 netmask 0xffffff00 broadcast 10.0.1.255
ether 00:09:5b:40:b2:9f
media: IEEE 802.11 Wireless Ethernet DS/11Mbps <hostap>
(autoselect <hostap>)
status: associated
ssid JANUS channel 6 bssid 00:09:5b:40:b2:9f
stationname JANUS_melchoir
authmode SHARED privacy MIXED deftxkey 1 wepkey 1:40-bit
txpowmax 100
dtimperiod 1 bintval 100
I see that the wi man page says:
The Intersil Prism family of chips' host-based access point
mode has bugs
for station firmware versions prior to 0.8.3. The driver
currently pre-
cludes hostap functionality with older station firmware. The
best ver-
sion of the station firmware for the Prism family of chips
seems to be
1.4.9. Some users of Prism-II and 2.5 based cards report that
station
firmware version 1.3.4 works better for them in hostap than
1.4.9. Older
versions of the Prism station firmware have a number of issues
with
hostap mode. The IBSS/adhoc mode appears to work well on station
firmware 1.3.1 and later. The IBSS/adhoc mode appears to have
problems
for some people with older versions of station firmware.
If that's the case, then my firmware (1.0.7, according to dmesg) is
way behind 1.3.4, but some quick Googling didn't turn up where to
find this firmware update. It did turn up this post: <http://
lists.freebsd.org/pipermail/freebsd-mobile/2004-February/
003112.html>, for whom a firmware update didn't seem to solve his
problem, but I'd like to at least give it a shot.
So, what could cause this problem, and has anyone had good
experiences with a firmware update in resolving it?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?662BF2EB-7CC9-4145-83A4-F96974FA87FB>