[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-tech
Subject:    Re: iwn(4): fix scan loop
From:       Jeremie Courreges-Anglas <jca () wxcvbn ! org>
Date:       2018-02-25 12:21:30
Message-ID: 87inaltg39.fsf () ritchie ! wxcvbn ! org
[Download RAW message or body]

On Sat, Feb 24 2018, Stefan Sperling <stsp@stsp.name> wrote:
> I made a mistake in my last commit to iwn and broke the scan loop.
> 
> The problem happens if we don't find an AP to connect to after one scan
> iteration. The stack then performs a SCAN -> SCAN transition to kick
> off another scan, but iwn(4) code in -current always treats this transition
> as a no-op.
> 
> With ifconfig iwn0 debug enabled, it's evident that the driver never shows
> another list of access points but the LED keeps blinking (this indicates
> SCAN state).
> 
> This diff makes iwn(4) start another scan during a SCAN->SCAN transition
> if no scan is in progress. This behaviour matches what iwm(4) does.

As advertized this seems to fix scans while not associated, using:

  iwn0 at pci2 dev 0 function 0 "Intel Centrino Advanced-N 6205" rev 0x34: msi, MIMO \
2T2R, MoW, address xx:xx:xx:xx:xx:xx

Thanks!
-- 
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE


[prev in list] [next in list] [prev in thread] [next in thread]