From owner-freebsd-bugs@FreeBSD.ORG  Wed May 11 10:10:06 2005
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E4C3316A4CE
	for <freebsd-bugs@hub.freebsd.org>;
	Wed, 11 May 2005 10:10:06 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B690443D6A
	for <freebsd-bugs@hub.freebsd.org>;
	Wed, 11 May 2005 10:10:06 +0000 (GMT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j4BAA6aS050393
	for <freebsd-bugs@freefall.freebsd.org>; Wed, 11 May 2005 10:10:06 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j4BAA64B050392;
	Wed, 11 May 2005 10:10:06 GMT
	(envelope-from gnats)
Date: Wed, 11 May 2005 10:10:06 GMT
Message-Id: <200505111010.j4BAA64B050392@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Brian Candler <B.Candler@pobox.com>
Subject: Re: kern/73871: Intersil Prism wireless wi0 locks up, "busy bit
	won't clear"
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Brian Candler <B.Candler@pobox.com>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2005 10:10:07 -0000

The following reply was made to PR kern/73871; it has been noted by GNATS.

From: Brian Candler <B.Candler@pobox.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/73871: Intersil Prism wireless wi0 locks up, "busy bit won't clear"
Date: Wed, 11 May 2005 10:46:48 +0100

 Supplementary information.
 
 I can make the interface lockup immediately when in a busy wireless
 environment (multiple access points and ssids).
 
 # kldload if_wi
 May 11 10:07:45 thinkdog kernel: wi0: <Intersil Prism2.5> mem 0xf8000000-0xf8000fff irq 11 at device 2.0 on pci1
 May 11 10:07:45 thinkdog kernel: wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
 May 11 10:07:45 thinkdog kernel: wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9)
 May 11 10:07:45 thinkdog kernel: wi0: Ethernet address: 00:05:3c:09:7e:9d
 May 11 10:07:45 thinkdog kernel: wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
 # ifconfig wi0 up
 # ifconfig wi0 ssid 'somessid'
 May 11 10:08:24 thinkdog kernel: wi0: timeout in wi_cmd 0x0002; event status 0x8008
 May 11 10:08:24 thinkdog kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8008
 May 11 10:08:24 thinkdog kernel: wi0: wi_cmd: busy bit won't clear.
 May 11 10:08:24 thinkdog kernel: wi0: init failed
 May 11 10:08:24 thinkdog kernel: wi0: failed to allocate 2372 bytes on NIC
 May 11 10:08:24 thinkdog kernel: wi0: tx buffer allocation failed (error 12)
 May 11 10:08:24 thinkdog kernel: wi0: interface not running
 
 The commands have to be given in this order to cause the lockup. If instead
 I do:
 
 # kldload if_wi
 # ifconfig wi0 ssid 'somessid'
 # ifconfig wi0 up
 
 then it appears to associate.
 
 Taking the interface down and up a few times, I can get into a state where
 consistently 'ifconfig wi0 down' causes an error:
 
 # ifconfig wi0 down
 May 11 10:25:32 thinkdog kernel: wi0: timeout in wi_cmd 0x0002; event status 0x8008
 
 However it's possible then to bring the interface back up.
 
 I have also had some problems where the client fails to associate with the
 access point until I kldunload/kldload the module again, but this may be a
 problem with the particular AP I'm working with.
 
 Regards,
 
 Brian.