linux-kernel - Re: 2.6.30-rc3: iwlagn probe timeouts (regression)

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: <1240852777.29221.6.camel@rc-desk>
Date:	Mon, 27 Apr 2009 10:19:37 -0700
From:	reinette chatre <reinette.chatre@...el.com>
To:	Niel Lambrechts <niel.lambrechts@...il.com>
Cc:	"linux.kernel" <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: 2.6.30-rc3: iwlagn probe timeouts (regression)

Hi Niel,

On Sun, 2009-04-26 at 17:00 -0700, Niel Lambrechts wrote:
> Hi,
> 
> In earlier 2.6.30 (rc1 and 2) kernel tests I suffered the "beacon loss,
> sending probe request" problem, during which my connection would
> intermittently fail and reconnect. With the latest git kernel which
> seems to include a patch (ad935687dbe7307f5abd9e3f610a965a287324a9) for
> at least some of this, my card (Intel 5300AGN REV=0x24) completely fails
> to associate and I get:
> 
> Apr 27 01:32:36 linux-7vph kernel: Registered led device: iwl-phy0::radio
> Apr 27 01:32:36 linux-7vph kernel: Registered led device: iwl-phy0::assoc
> Apr 27 01:32:36 linux-7vph kernel: Registered led device: iwl-phy0::RX
> Apr 27 01:32:36 linux-7vph kernel: Registered led device: iwl-phy0::TX
> Apr 27 01:32:36 linux-7vph kernel: ADDRCONF(NETDEV_UP): wlan0: link is
> not ready
> Apr 27 01:32:40 linux-7vph sudo:   niella : TTY=pts/2 ; PWD=/home/niella
> ; USER=root ; COMMAND=/usr/bin/tail -f /var/log/messages
> Apr 27 01:33:16 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e try 1
> Apr 27 01:33:16 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e try 2
> Apr 27 01:33:16 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e try 3
> Apr 27 01:33:16 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e timed out
> Apr 27 01:33:29 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e try 1
> Apr 27 01:33:29 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e try 1
> Apr 27 01:33:29 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e try 2
> Apr 27 01:33:29 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e try 3
> Apr 27 01:33:29 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e timed out
> Apr 27 01:33:42 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e try 1
> Apr 27 01:33:42 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e try 1
> Apr 27 01:33:42 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e try 2
> Apr 27 01:33:42 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e try 3
> Apr 27 01:33:43 linux-7vph kernel: wlan0: direct probe to AP
> 00:1d:92:1d:1e:8e timed out
> 
> I do not have any similar problems with 2.6.29 or 2.6.28 at the exact
> same physical location.
> 
> I can try to bisect in a day or two if need be.

>>From what I can tell we did not send any iwlagn patches to 2.6.30 that
are related to this behavior. Please do try a bisect. 

Thank you

Reinette


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