From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 23 20:39:00 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8296C8A7 for ; Wed, 23 Apr 2014 20:39:00 +0000 (UTC) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 11C191515 for ; Wed, 23 Apr 2014 20:38:59 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBFFA4.dip0.t-ipconnect.de [93.203.255.164]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id s3NKcYTs079298; Wed, 23 Apr 2014 20:38:35 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id s3NKchsD064116; Wed, 23 Apr 2014 22:38:43 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id s3NKcP2X054576; Wed, 23 Apr 2014 22:38:37 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201404232038.s3NKcP2X054576@fire.js.berklix.net> To: Anthony Jenkins Subject: Re: urtwn panic From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Wed, 23 Apr 2014 09:46:33 -0400." <5357C439.4040101@yahoo.com> Date: Wed, 23 Apr 2014 22:38:25 +0200 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 23 Apr 2014 20:39:00 -0000 Anthony Jenkins wrote: > I'm getting a panic with the latest kernel (r264719) and the if_urtwn driver. Might the urtwn device overheat, not return & cause a panic ? My urtwn device is very small, no thermal path to dump heat. I've not tried on current, but on 10.0-RELEASE I saw my urtwn0 interface disappearing; I read parts of the driver; & noticed there's mention of a temperature level, I didn't tweak it, but hung my device on a USB extension cable at 10 C outside the window, & later in front of a chassis input fan at ~ 20 C room temp., I think both locations lasted longer or perhaps indefinately without urtwn0 , can't remember, I suspended pursuing it. Device picture for those who don't know how small this, & other URLs via: http://www.berklix.com/~jhs/hardware/urtwn/ Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Interleave replies below like a play script. Indent old text with "> ". Google breach privacy http://berklix.com/jhs/adverts/