linux-kernel - Re: iwlagn is getting even worse with 3.3-rc1

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]

Date:	Wed, 22 Feb 2012 10:40:43 +0200
From:	Pekka Enberg <penberg@...nel.org>
To:	Norbert Preining <preining@...ic.at>
Cc:	Emmanuel Grumbach <egrumbach@...il.com>,
	linux-kernel@...r.kernel.org, ipw3945-devel@...ts.sourceforge.net,
	"Guy, Wey-Yi" <wey-yi.w.guy@...el.com>,
	Johannes Berg <johannes@...solutions.net>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
	Dave Jones <davej@...hat.com>
Subject: Re: iwlagn is getting even worse with 3.3-rc1

On Wed, Feb 22, 2012 at 2:37 AM, Norbert Preining <preining@...ic.at> wrote:
> I still see that, on 3.3-rc4, and it is the same as usual. The interface
> believes it is up and connected, but nothing works.
>
> I am *100%* sure that this is related to the driver, because in old
> revisions (somewhen around 2.6.27 or so) it was working without
> any problem, and when it started I reported it long time ago.

It's definitely a kernel regression, no question about it. Was 3.3-rc1
already broken for you? It shouldn't be that difficult to find the
offending commit with git bisect if it's that easy to reproduce for
you.

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