iwn(4) association issues in 11-Stable (and maybe RC)

[Adrian Chadd]

IWN_DEBUG worked, it's 'dev.iwn.0.debug', not 'debug.iwn.0.debug'. My bad.

Make sure you build the module by doing 'buildkernel', not 'cd
sys/modules/iwn && make', as (because reasons I want to grr) we don't
enforce that people put in a path to their kernel config .h directory,
so it defaults to "some arbitrary options".


-a


On 24 August 2016 at 15:42, Kevin Oberman <kob6558 at gmail.com> wrote:
> On Wed, Aug 24, 2016 at 12:45 PM, Glen Barber <gjb at freebsd.org> wrote:
>>
>> On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote:
>> > <kob6558 at gmail.com>
>> > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber <gjb at freebsd.org> wrote:
>> >
>> > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote:
>> > > > Not working right. I do see 802.11 messages but nothing from iwn.
>> > > > Rebuilt with:
>> > > > options        IEEE80211_DEBUG
>> > > > options        IWN_DEBUG
>> > > >
>> > > > [...]
>> > > >
>> > > > Any idea what is going on?
>> > >
>> > > Your original email mentions 11.0-BETA4.  Are you still running
>> > > stable/11?  If so, could you please update to r304715?  If running
>> > > releng/11.0, the matching commit is r304719.
>> > >
>> >
>> > Since my initial post I have updated to r304734 (running 11-STABLE). I
>> > did
>> > that before rebuilding my kernel with the DEBUG options as it was
>> > already
>> > three weeks old. So this does not seem to have fixed the issue.
>>
>> Dumb question, but with reason.
>>
>> Does ifconfig(8) actually show wlan0 'UP'?
>>
>> I'm asking this because I'm seeing something strange locally on one
>> machine.
>>
>> Glen
>
>
> I have stopped and started the network repeatedly using both my home router
> and my hot-spot and I can't get it to fail. It associates the first time
> every time. I'm about ready to chalk up my one failure with the new kernel
> as a fluke. I'll continue testing later today, but this one may be resolved.
>
> I'll also rebuild my kernel without the debug options just in case the
> slight timing change had some impact on this.
>
> Thanks to both Glen and Adrian for helping me look into this. Still have no
> idea why IWN_DEBUG didn't seem to work.
> --
> R. Kevin Oberman, Network Engineer
> E-mail: kob6558 at gmail.com