From owner-freebsd-wireless@FreeBSD.ORG Fri May 23 09:59:50 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BDDA22E3; Fri, 23 May 2014 09:59:50 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (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 9459628D2; Fri, 23 May 2014 09:59:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=1fETEnakpdfJOigot4VTjVSrb6cN5Bwdww2hEEazGJk=; b=yA+qsImn8U5K1YoUjJSHikdieqWosrrCKMPacZ14px9cJNrRzAMwf8SdCgqVLscAJTAVPqHRT04nJktq3AM/sBW0qo8HgjJo5OXQ76Z3iq51IMZlewKHGQ1kvHQeuBrcYMWtVIId5M7l2sEXDPF5dQOn0oRF1wffifnh1r4DUOs=; Received: from [182.7.116.7] (port=15880 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WnmGM-001y09-Ti; Fri, 23 May 2014 03:59:43 -0600 Date: Fri, 23 May 2014 17:59:35 +0800 From: Erich Dollansky To: Adrian Chadd Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140523175935.468039f4@X220.alogt.com> In-Reply-To: References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <20140409113254.3a3277a3@X220.alogt.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-wireless@freebsd.org" , sean bruno X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Fri, 23 May 2014 09:59:50 -0000 Hi, On Tue, 8 Apr 2014 20:40:01 -0700 Adrian Chadd wrote: > I'm not sure. I'd really like to see what the story is with > coexistence somehow. > I upgraded my machine to this: FreeBSD X220.alogt.com 10.0-STABLE FreeBSD 10.0-STABLE #36 r266578: Fri May 23 16:56:23 WITA 2014 erich@X220.alogt.com:/usr/obj/usr/src/sys/X220 amd64 It is still the same with iwn. It crashes when trying to read instruction at 0x20:0. It seems to me that this behaviour is now quite normal on my machine. What can I do best to help finding the source of the problem? Erich > > -a > > > On 8 April 2014 20:32, Erich Dollansky > wrote: > > Hi, > > > > On Tue, 8 Apr 2014 20:07:39 -0700 > > Adrian Chadd wrote: > > > >> Coexistence is to deal with the fact that a 40MHz channel may > >> overlap a 20MHz-only AP in the extension channel. > >> > >> If the AP finds a 20MHz AP in the extension channel (ie, the other > >> half of its 40MHz) channel then it'll flip itself to 20MHz. If it > >> determines it isn't there any more, it'll flip the BSS to the 40MHz > >> channel. > >> > >> Now, why the hell it's causing the connection to fail? I have no > >> idea. > >> > >> can someone file a PR that says it's all busted with 40MHz > >> coxistence enabled? We can then start debugging from that position. > >> > > I am not so sure if it is a general problem or just a DLink problem. > > > > I just activated my own access point and it worked there. The only > > problem is that it also works with DLink but only randomly. So, it > > still could have been that I was just always lucky when connecting > > to the ProLink access point I have. > > > > As the DLink is not mine, I am not even able to access its > > administration interface. > > > > Can I suggest to wait a bit to get more feedback to see if it is a > > general problem or a problem only linked to one manufacturer? > > > > Erich