Date: Thu, 19 Dec 2013 09:03:16 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Stefan Farfeleder <stefanf@freebsd.org> Cc: "freebsd-mobile@freebsd.org" <mobile@freebsd.org> Subject: Re: iwn debug messages Message-ID: <CAJ-VmonJz%2BysOb0cY6TAxtR=D3DjYanUN6LWe1OQORfyYZ_oPw@mail.gmail.com> In-Reply-To: <20131219134429.GA1515@mole.fafoe.narf.at> References: <20131219134429.GA1515@mole.fafoe.narf.at>
next in thread | previous in thread | raw e-mail | index | archive | help
1) It's an indication that the air is busy. It's supposed to retune after that but I haven't yet finished that part. 2) Beause of how we do single channel scans, we seem to trigger the occasional bug where the firmware will sit on a passive channel (eg 13) for a couple of minutes at a time before moving on. Beforehand we would send another scan command even if the previous scan was not finished and this could cause the firmware to get upset. Now I track whether we're scanning on a channel and print out an error if we try to submit another scan. The real solution is to rewrite the net80211 scan stuff to be modular so iwn can implement its own multi-channel scanning but I just don't have the time at the moment. -a On 19 December 2013 05:44, Stefan Farfeleder <stefanf@freebsd.org> wrote: > Hi Adrian, > > as of late I see the following messages being printed by the kernel: > > "iwn0: iwn_check_rx_recovery: PLCP error threshold raw (278) comparison (27800) over limit (20400); retune!" > (the values vary wildly) > > and: > > "iwn0: iwn_scan: called whilst scanning!" > > Is this something I should worry about? This is a <Intel WiFi Link 5100>. > > BR, > Stefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonJz%2BysOb0cY6TAxtR=D3DjYanUN6LWe1OQORfyYZ_oPw>