On Mon, Jul 26, 2010 at 4:02 PM, Andrew Lutomirski [off-list ref] wrote:

There's a regression in 2.6.35 where the connection breaks and iwlagn
writes a bunch of:

iwlagn 0000:03:00.0: BA scd_flow 0 does not match txq_id 10

This is confirmed [1] and a patch supposedly exists.  Since this
breaks at least two people's wireless and 2.6.35 is about to be
released, can we see the patches?

Thanks,
Andy

[1] http://article.gmane.org/gmane.linux.kernel.wireless.general/53552

This regression was reported on July 21 and confirmed, supposedly with
a patch available, on July 24 (or maybe July 23).  On July 26 I pinged
the list because I'm affected as well.

It's now August 10 and both 2.6.35 and 2.5.35.1 have been released and
the bug is still there.  WTF happened?  (I admit I haven't actually
tested 2.6.35.1 because it's still compiling, but I see nothing to
suggest that it's been fixed.)

Thanks,
Andy

P.S.  iwlagn malfunctions for me *all the time*.  I'd love to help
debug but it's hard when no one pays attention and when the bugs are
all hard to trigger.  Any volunteers to help?