linux-kernel - Re: 3.4-rc2, ilwagn still most of the time completely unusable

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: <20120411200105.GA22002@redhat.com>
Date:	Wed, 11 Apr 2012 16:01:05 -0400
From:	Dave Jones <davej@...hat.com>
To:	"Ted Ts'o" <tytso@....edu>, David Miller <davem@...emloft.net>,
	preining@...ic.at, egrumbach@...il.com,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
	ipw3945-devel@...ts.sourceforge.net, ilw@...ux.intel.com
Subject: Re: 3.4-rc2, ilwagn still most of the time completely unusable

On Wed, Apr 11, 2012 at 02:40:47PM -0400, Ted Ts'o wrote:

 > I'll note that I've been having troubles with my iwlagn driver losing
 > the ability to connect to WPA2 authenticated AP's at work (Google
 > Cambridge).  This has been true for since sometime around 3.0; my
 > excuse for why I haven't tried bisecting it is that it can take
 > several hours for the bug to manifest itself, and when it does, it's
 > much simpler to either (a) reboot, or (b) rmmod iwlagn and then
 > modprobe iwlagn.
 > 
 > I also don't know if it's a problem with (a) the iwlagn driver, (b) my
 > hardware, (c) the network-manager WPA code, or (d) the enterprise AP
 > that we are using, or some combination of the four.  On my todo list
 > is to get a completely different 802.11abn wireless PC Card, and then
 > try to see if the problem reproduces itself there, and then see if I
 > can at some point try to set aside a full week where I'd do nothing
 > else with my laptop but git bisects full-time.
 > 
 > Sometimes, git bisects are not terribly useful ways of trying to find
 > the problem commits --- and I've tried doing them before to debug
 > iwlagn problems twice before, and past experience tells me it's a
 > minimum of 1, and usually more like 2 or 3 days of lost productivity
 > while I try to debug it --- and that's when the problem is obvious
 > within 10 or 20 minutes of the reboot.  :-(

iwlwifi has a debug module option which generates a ton of spew, but
the Intel developers have managed to diagnose several iwlwifi problems
I've had by staring at the dumps. Starting there is probably going to
be faster than bisecting. (Especially when you're in a situation like I was
where it was just 'differently broken' at various points in time).

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