linux-kernel - Re: Probe Timeouts with 47afbaf5af9454a7a1a64591e20cbfcc27ca67a8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.01.0905111157561.3586@localhost.localdomain>
Date:	Mon, 11 May 2009 12:14:42 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Johannes Berg <johannes@...solutions.net>
cc:	Parag Warudkar <parag.lkml@...il.com>,
	"John W. Linville" <linville@...driver.com>,
	LKML <linux-kernel@...r.kernel.org>, niel.lambrechts@...il.com
Subject: Re: Probe Timeouts with 47afbaf5af9454a7a1a64591e20cbfcc27ca67a8

On Mon, 11 May 2009, Johannes Berg wrote:
> 
> Curious really, since with that fix and a revert it would go to -1 dBm.
> The only explanation I have is that then the Intel card defaults to some
> safe value because it doesn't support values < 0.

Well, since I'm testing this laptop for any corner cases, the non-working 
case had actually been tested with things like multiple suspend-to-ram 
cycles (while doing accelerated 3D and sound at the same time), along with 
testing anything else I could think of. And everything worked, but 
wireless wouldn't associate.

Reverting and rebooting, and it worked. But then when I wanted to 
double-check (sadly _after_ having already sent out the complaint), I 
now cannot get it to not work even without the revert.

And I've re-done all the STR testing, and that isn't the cause of it.

Oh well.

I don't actually tend to _use_ that laptop, it gets dug out for release 
and distro testing and for some very occasional travel.  I've not had 
issues with wireless on that thing before (apart from any normal iwl 
issues), but maybe it just happened to take a really really long time to 
associate that one time.

				Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/