From owner-freebsd-mobile@FreeBSD.ORG Thu Nov 10 20:59:11 2005 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 0C43916A420; Thu, 10 Nov 2005 20:59:11 +0000 (GMT) In-Reply-To: <4373B099.8050301@altadena.net> from Peter Carah at "Nov 10, 2005 12:42:01 pm" To: pete@altadena.net (Peter Carah) Date: Thu, 10 Nov 2005 20:59:11 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051110205911.0C43916A420@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-mobile@freebsd.org Subject: Re: Broadcom wireless ndis 64 bit X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2005 20:59:11 -0000 > > So does your laptop have a "turn the radio on/off" switch on it and did > > you remember to use it to turn the radio on? > > Yes, and the blue light never went on. With the previous attempts ifconfig up > and ifconfig down switched the blue light on and off so the button was > redundant. That worked once, then never again. I didn't power down+up > between, though. I'm running the atlas blas build at the moment; it takes > almost 2 days, though 'make' after an interruption does catch up pretty quick. > Also there is a 3-4 second pause where *nothing* works (uninterruptible cpu > bound) after the "ifconfig up". > > -- Pete Try it again after you reboot. I think long delay when you do ifconfig up occurs when the driver is trying to allocate chunks of shared memory with NdisMAllocateSharedMemory(). It wants a lot of little buffers, and it takes a while to allocate them all through busdma. Also, if the system has been running for a while and memory has become sufficiently fragmented, the allocations can fail. Unfortunately, NDIS drivers to not allocate shared memory buffers once at attach time: they allocated them every time you do MiniportInitialize() (and release them when you do MiniportHalt()). -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose =============================================================================