From owner-freebsd-net@FreeBSD.ORG Thu Oct 13 14:59:58 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 118BC106564A; Thu, 13 Oct 2011 14:59:58 +0000 (UTC) (envelope-from break19@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 8C5A58FC16; Thu, 13 Oct 2011 14:59:57 +0000 (UTC) Received: by qyk10 with SMTP id 10so123424qyk.13 for ; Thu, 13 Oct 2011 07:59:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AlIJ/UEF+zYABY/7VwNZhOOyTffkoSqiiyVPH2iT/vc=; b=GdvZ+NaBadya6v33l6YvgGY/Lzdq/ZGx7jqlsDODOgJOikOczqHteqw2GZEFW3m8Sj ZXsuwhYA801+qg+1Umt1wGJ8bNM8JMRk7xEmJMu3jRA4ScGOggnPGPbljU026ZyJw3yA PH0VzQv9WnUMQyXs/UrG2lnZNAni6gUlEn+uw= MIME-Version: 1.0 Received: by 10.229.90.140 with SMTP id i12mr869283qcm.106.1318517996575; Thu, 13 Oct 2011 07:59:56 -0700 (PDT) Received: by 10.229.26.18 with HTTP; Thu, 13 Oct 2011 07:59:56 -0700 (PDT) In-Reply-To: <201110110720.04292.break19@gmail.com> References: <201110110720.04292.break19@gmail.com> Date: Thu, 13 Oct 2011 09:59:56 -0500 Message-ID: From: Chuck Burns To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, Adrian Chadd Subject: Re: [urtw] Wifi link dying randomly. reboot required to reconnect. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2011 14:59:58 -0000 Some more information.. I had mentioned this issue to someone on the ##FreeBSD irc channel, and he said that his father uses the urtw driver, on an i386 system, also running 8.2, but has no issues with kernel panics, and the only drops that he knows is due to his router, and resetting the router solves (but not the box, nor unplugging/replugging the dongle, neither of those are necessary to restore service) My system on the other hand just reports "No Carrier" in ifconfig, even after resetting the router, and other devices in the home can see it, and connect to it fine. I am not sure if this information is pertinent or not, but seeing as we've appeared to reach an impasse, with no more suggestions, requests for info... I figure the more info we can gather, the better... Chuck Burns