linux-kernel - Re: WLAN regression before this morning

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4889F7D6.4010706@lwfinger.net>
Date:	Fri, 25 Jul 2008 10:57:10 -0500
From:	Larry Finger <Larry.Finger@...inger.net>
To:	free_beer_for_all@...oo.com
CC:	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: WLAN regression before this morning

barry bouwsma wrote:
> Servus,
> 
> Last successfully built and used kernel was 2.6.26-rc8, about
> the start of 29.Jun UTC or so.
> 
> Present build of GIT 2.6.26 during the merge window, updated
> just before 06h UTC, today, 25.Jul.
> 
> With today's kernel, I am not even able to associate with a
> WLAN less than two metres away from my ZD1211rw type USB
> adapter, to say nothing of more distant WLANs with which I
> could authenticate with the earlier code without problems --
> I don't even come near the associate stage.
> 
> The networks all show up as expected in `iwlist wlan1 scan'
> with decent strengths; while all I get from dmesg is
> [ 1016.829827] wlan1: authenticate with AP 00:1X:YZ:AB:23:45
> [ 1017.032769] wlan1: authenticate with AP 00:1X:YZ:AB:23:45
> [ 1017.234213] wlan1: authenticate with AP 00:1X:YZ:AB:23:45
> [ 1017.435402] wlan1: authentication with AP 00:1X:YZ:AB:23:45 timed out
> 
> 
> If I've hosed myself with a new .config option, I'll be kicking
> meself where it hurts most.  Else, back to -rc8 to both send
> this message and to regain 'net access to do other needed so-
> called `work', so sorry I haven't narrowed this down further...
> 
> And I'll feel me a fool if the failure is because I went from
> a different (BSD) OS into 2.6.26-merge, while going from that
> into -rc8 I promptly associate as desired.

I too have a problem with wireless in the current 2.6.26-gitX kernels. If you 
have done the git pull, you can try bisecting to find the problem. Use 'git 
bisect good v2.6.26' to mark a known good point. If you don't wish to take the 
time bisecting, then issue a 'git checkout v2.6.26'. That should give you a 
kernel that works.

Larry
--
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/