Date: Wed, 18 Jun 2008 06:10:04 GMT From: "Kevin Foo" <chflags@gmail.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/85886: [an] an0: timeouts with Cisco 350 minipci Message-ID: <200806180610.m5I6A41a068684@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/85886; it has been noted by GNATS. From: "Kevin Foo" <chflags@gmail.com> To: bug-followup@freebsd.org, jyoung@spaceball1.doogles.com, jyoung@evelocity.net Cc: Subject: Re: kern/85886: [an] an0: timeouts with Cisco 350 minipci Date: Wed, 18 Jun 2008 14:08:43 +0800 ------=_Part_33479_9076624.1213769324147 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline With FreeBSD 7.0-stable running on T42 + Cisco Aironet 350 minipci, I'm able to associate with the AP with 128bits encryption via ifconfig command, ifconfig an0 ssid 'myap' wepmode on weptxkey 1 wepkey 1:0x<mykey>. Still no luck of getting wpa_supplicant to manage it. It started giving out problem after 15-20mins or with heavy usage (using scp). The device refused to work and lockup the system for a while (few seconds to minutes). The system will alive again after an0 puked out these error messages. an0: device timeout an0: reset failed an0: failed to allocate RX descriptor an0: failed to write RID 1 ff11 a921 fdba 4365 c287, 60 an0: failed to set ssid list an0: failed to read RID 1 ff50 a921 fdba 4365 c287, 3 an0: failed to read RID 1 ff50 a921 fdba 4365 c287, 3 an0: failed to read RID 1 ff50 a921 fdba 4365 c287, 3 an0: failed to read RID 1 ff50 a921 fdba 4365 c287, 3 The firmware in use was 5.00.01. The an0 driver is still not happy with it. Or I should forget about the card and buy a new PCMCIA card to go wireless? Any help or hint on this would be great. -- Regards Kevin Foo On Mon, Jun 16, 2008 at 5:07 PM, Kevin Foo <chflags@gmail.com> wrote: > Any updates on this issue? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=85886 > > I'm still seeing this issue with 7.0-stable on IBM T42 with Cisco 350 > minipci. Scanning will make ifconfig and wpa_supplicant stop responding or > even kill the process i.e. ap_scan=1 will terminate wpa_supplicant. > > TIA > > -- > Regards > Kevin Foo ------=_Part_33479_9076624.1213769324147 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline With FreeBSD 7.0-stable running on T42 + Cisco Aironet 350 minipci, I'm able to associate with the AP with 128bits encryption via ifconfig command, ifconfig an0 ssid 'myap' wepmode on weptxkey 1 wepkey 1:0x<mykey>. Still no luck of getting wpa_supplicant to manage it. <br> <br>It started giving out problem after 15-20mins or with heavy usage (using scp). The device refused to work and lockup the system for a while (few seconds to minutes). The system will alive again after an0 puked out these error messages.<br> <br>an0: device timeout<br>an0: reset failed<br>an0: failed to allocate RX descriptor<br>an0: failed to write RID 1 ff11 a921 fdba 4365 c287, 60<br>an0: failed to set ssid list<br>an0: failed to read RID 1 ff50 a921 fdba 4365 c287, 3<br> an0: failed to read RID 1 ff50 a921 fdba 4365 c287, 3<br>an0: failed to read RID 1 ff50 a921 fdba 4365 c287, 3<br>an0: failed to read RID 1 ff50 a921 fdba 4365 c287, 3<br><br>The firmware in use was <a href="http://5.00.01.">5.00.01.</a>; The an0 driver is still not happy with it. Or I should forget about the card and buy a new PCMCIA card to go wireless? Any help or hint on this would be great.<br> <br>-- <br>Regards<br>Kevin Foo <br><br><br><div class="gmail_quote">On Mon, Jun 16, 2008 at 5:07 PM, Kevin Foo <<a href="mailto:chflags@gmail.com">chflags@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Any updates on this issue?<br><br><a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=85886" target="_blank">http://www.freebsd.org/cgi/query-pr.cgi?pr=85886</a><br clear="all"><br>I'm still seeing this issue with 7.0-stable on IBM T42 with Cisco 350 minipci. Scanning will make ifconfig and wpa_supplicant stop responding or even kill the process i.e. ap_scan=1 will terminate wpa_supplicant.<br> <br>TIA<br><br>-- <br>Regards<br><font color="#888888">Kevin Foo </font></blockquote></div><br><br clear="all"><br> ------=_Part_33479_9076624.1213769324147--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806180610.m5I6A41a068684>