Date: Wed, 9 Apr 2014 12:04:51 +0800 From: Erich Dollansky <erichsfreebsdlist@alogt.com> To: Adrian Chadd <adrian@freebsd.org> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>, sean bruno <sbruno@ignoranthack.me> Subject: Re: iwn0 hangs randomly when starting the machine Message-ID: <20140409120451.4f60e599@X220.alogt.com> In-Reply-To: <CAJ-VmokCjwQNXc0ihx7jFZtE-5j9UHHf2KCrU5L2SW2p6DAwQg@mail.gmail.com> References: <20140331073054.5d7642d6@X220.alogt.com> <1397006320.5173.2.camel@powernoodle.corp.yahoo.com> <20140409093642.19c2f5cb@X220.alogt.com> <CAJ-VmokeKSpYuq-ROOX=Z00rESFGvQTb%2BdXtRrUvc5QXzJvMYg@mail.gmail.com> <20140409113254.3a3277a3@X220.alogt.com> <CAJ-VmokCjwQNXc0ihx7jFZtE-5j9UHHf2KCrU5L2SW2p6DAwQg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Tue, 8 Apr 2014 20:40:01 -0700 Adrian Chadd <adrian@freebsd.org> wrote: > I'm not sure. I'd really like to see what the story is with > coexistence somehow. one other note. I start my machine randomly with a kernel built from sources dated 26.03.14. I never faced this problem with these sources. Erich > > > -a > > > On 8 April 2014 20:32, Erich Dollansky <erichsfreebsdlist@alogt.com> > wrote: > > Hi, > > > > On Tue, 8 Apr 2014 20:07:39 -0700 > > Adrian Chadd <adrian@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140409120451.4f60e599>