Date: Thu, 14 Mar 2002 11:14:59 -0500 From: "Dan Langille" <dan@langille.org> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: mobile@FreeBSD.ORG, Oliver Brandmueller <ob@gruft.de>, Rasputin <rasputin@submonkey.net>, Dan Langille <dan@langille.org> Subject: Re: patch for Lucent command timeouts Message-ID: <20020314161503.963073F0E@bast.unixathome.org> In-Reply-To: <20020313143226.A18204@Odin.AC.HMC.Edu> References: <20020313113313.B11290@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Wed, Mar 13, 2002 at 11:33:13AM -0800
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 Mar 2002 at 14:32, Brooks Davis wrote:
> On Wed, Mar 13, 2002 at 11:33:13AM -0800, Brooks Davis wrote:
> > The following patch attempts to address the timeouts people have been
> > seeing in after my recent MFC of Linksys support.
>
> Here's a slightly improved patch which avoids some timeouts on INI
> commands thanks to Thomas Skibo.
I have had mixed success with this patch.
- The laptop likes the new patch, the desktop does not.
- The timeout messages I was originally seeing are no longer occurring.
I tried the patch on my desktop (which acts as a wireless gateway). It
wasn't until about an hour after a reboot with the new kernel that this
message appeared:
wi0: timeout in wi_cmd 0x010b; event status 0x000b
wi0: xmit failed
wi0: timeout in wi_cmd 0x010b; event status 0x000b
wi0: xmit failed
Under traffic, the above messages appear on the desktop. I generate the
traffic by sshing to the laptop from the desktop and issuing a command
such as "find ." when in /usr/src which is an NFS mount from the desktop.
Coincidentally (I think not), these messages started after I logged into
the laptop (remotely) and traffic started across the waveless net.
In case it helps, here are some messages from the laptop /var/log/messages
during the boot process:
laptop pccardd[50]: Card "Lucent Technologies"("WaveLAN/IEEE") [Version
01.01] [] matched "Lucent Techn
ologies" ("WaveLAN/IEEE") [(null)] [(null)]
Mar 14 11:02:55 laptop /kernel: wi0: <WaveLAN/IEEE 802.11> at port 0x240-
0x27f irq 3 slot 1 on pccard1
laptop /kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8000
laptop /kernel: wi0: 802.11 address: 00:02:2d:0e:66:bd
laptop /kernel: wi0: using Lucent chip or unknown chip
Mar 14 11:02:56 laptop /kernel: wi0: timeout in wi_cmd 0x0000; event
status 0x0000
laptop last message repeated 4 times
laptop /kernel: wi0: init failed
laptop pccardd[50]: wi0: Lucent Technologies (WaveLAN/IEEE) inserted.
laptop sshd[95]: Server listening on :: port 22.
laptop sshd[95]: Server listening on 0.0.0.0 port 22.
laptop /kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8080
laptop last message repeated 4 times
laptop /kernel: wi0: init failed
laptop /kernel: wi0: timeout in wi_cmd 0x0121; event status 0x0000
laptop /kernel: wi0: timeout in wi_seek to fc07/0; last status 8000
laptop /kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8080
laptop last message repeated 4 times
laptop /kernel: wi0: init failed
laptop /kernel: wi0: timeout in wi_cmd 0x0121; event status 0x0000
laptop /kernel: wi0: timeout in wi_seek to fc07/0; last status 8000
laptop /kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8080
laptop last message repeated 4 times
laptop /kernel: wi0: init failed
laptop /kernel: wi0: timeout in wi_cmd 0x0121; event status 0x0000
laptop /kernel: wi0: timeout in wi_cmd 0x0121; event status 0x0000
laptop /kernel: wi0: timeout in wi_seek to fc00/0; last status 8000
laptop /kernel: wi0: timeout in wi_cmd 0x0000; event status 0x0080
laptop last message repeated 4 times
laptop /kernel: wi0: init failed
laptop pccardd[50]: pccardd started
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020314161503.963073F0E>