On Wed, 2012-07-04 at 13:40 +0200, Stanislaw Gruszka wrote: > On Wed, Jul 04, 2012 at 02:33:48PM +0300, Emmanuel Grumbach wrote: > > Ok, but doest it solve the bug ? > > CCing Poul. Well I didn't see the queue-2-is-stuck error while testing that patch for a few days (mostly by disconnecting and reconnecting to my wlan through clicking a GUI applet). That being said, since a day or two I'm again running without that patch and also haven't noticed that error. So perhaps the jury's still out on this patch ... Maybe I should again try suspending and resuming in a loop. But that raises the chance of suspend/resume bugs influencing the results. Testing bugs like these (in network code, only triggered every now and then) apparently isn't easy. > But even if not, we still probably need that patch, right? Or is > possible that 4965 firmware do not corrupt memory when we provide > wrong key offset to it? Or maybe for 4965 key offset 0xff is something > that is expected and needed to invalidate the key? Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
