From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 8 07:59:38 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 663B01065672; Wed, 8 Feb 2012 07:59:38 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id A00978FC0C; Wed, 8 Feb 2012 07:59:37 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id q187KCsm088049; Wed, 8 Feb 2012 18:20:12 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 8 Feb 2012 18:20:12 +1100 (EST) From: Ian Smith To: Adrian Chadd In-Reply-To: Message-ID: <20120208174845.A53709@sola.nimnet.asn.au> References: <20120207194931.GB1676@pgl-P5K-E> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1303104072-1328685612=:53709" Cc: freebsd-wireless@freebsd.org, Peter Lazar Subject: Re: wi driver X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2012 07:59:38 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1303104072-1328685612=:53709 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Tue, 7 Feb 2012, Adrian Chadd wrote: > On 7 February 2012 11:49, Peter Lazar wrote: > > Hi there, > > > > After reading > > > >  http://forums.freebsd.org/archive/index.php/t-27830.html > > > > Here's my two cents on the wi driver. > > Hi, > > What about 8.0 ? Rummaging through my old messages* shows I'd never tried wi on 8.0 through 8.1-stable, nor apparently 7.x, though I used to use it infrequently but successfully on 4.8-R, 5.5-S and 6.1-R. I can confirm Peter's report for my Cabletron Roamabout (Wavelan clone) on 8.2-R, now: interrupt storm detected on "irq11:"; throttling interrupt source wi0: at port 0x100-0x13f irq 11 function 0 config 1 on pccard0 wi0: [ITHREAD] wlan0: Ethernet address: 00:e0:63:82:d9:47 t23# ifconfig wlan0 create wlandev wi0 t23# ifconfig [..] wi0: flags=8802 metric 0 mtu 2290 ether 00:e0:63:82:d9:47 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier wlan0: flags=8802 metric 0 mtu 1500 ether 00:e0:63:82:d9:47 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 1 (2412 MHz 11b) country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60 bintval 0 With nothing to talk to here, I didn't try configuring wlan0 further. wi0: detached One earlier attempt on 8.2 shows the same interrupt storm on insertion, except on an immediately subsequent insertion, it picked on irq 5 - ah, but that was trying it in the other slot. On that occasion I didn't bother trying to configure wlan0. Oct 31 17:54:25 t23 kernel: interrupt storm detected on "irq11:"; throttling interrupt source Oct 31 17:54:25 t23 kernel: wi0: at port 0x100-0x13f irq 11 function 0 config 1 on pccard0 Oct 31 17:54:25 t23 kernel: wi0: [ITHREAD] Oct 31 17:56:22 t23 kernel: wi0: detached Oct 31 17:56:41 t23 kernel: interrupt storm detected on "irq5:"; throttling interrupt source Oct 31 17:56:41 t23 kernel: wi0: at port 0x100-0x13f irq 5 function 0 config 1 on pccard1 Oct 31 17:56:41 t23 kernel: wi0: [ITHREAD] Oct 31 17:58:27 t23 kernel: wi0: wi_seek_bap: timeout, id ffff off 0 Oct 31 17:58:27 t23 last message repeated 2 times Oct 31 17:58:28 t23 kernel: wi0: detached > There are other changes that have occured in the kernel besides > wireless. A lot of the "stuff used to work, now it doesn't" issues > stem from PCI/PCMCIA/cardbus resource allocation changes. Could be, but I vaguely recall a few other threads saying wi was broken? cheers, Ian --0-1303104072-1328685612=:53709--