Jonathan Nieder wrote:
> Arend van Spriel wrote:
>> I guess the behaviour improved due to the last two patches listed above,
>> but I also suspect that it is only an improvement and the root cause
>> still exists.
>
> I think you're right. Camaleón tried with all patches except the last
> one and still got the unwanted reconnects.
>
> Would 6b8da423315b and 94a2ca311cf4 be good candidates for stable@ in
> the meantime (for symptom relief and saner regulatory code) until the
> root cause is found?
To answer my own question: I guess not, at least not on the basis of
Camaleón's experience.
Results so far:
* mainline >= 3.4.y: seemed to be ok for a few days, never showed the
problem.
* 3.2.19 + the 23 patches discussed in this thread: worked fine for about
a week, never showed the problem.
* 3.2.18: failed quickly.
* 3.2.19 + first patch: failed quickly.
* 3.2.2: worked ok for a while, then acted up again. Affected.
* 3.2.21 + 10 patches: failed quickly.
* 3.2.21 + all 23 patches: worked ok-ish (?) for a week ("only a
couple reconnects in 7 days, but when that happened gnome-shell was
not segfaulting at least..."). I should have paid more attention:
that meant it was affected!
* 3.2.21 + 17 patches: failed quickly.
* 3.2.21 + 19 patches: failed quickly.
* 3.2.22 + 22 patches: failed quickly.
* 3.2.21 + patch #23 alone: failed quickly.
* 3.2.21 + all 23 patches: failed quickly.
Arend, you're very good at this guessing game. ;-)
I imagine the problem is still present in mainline. Camaleón, the
next useful test would probably be mainline or wireless-testing, and
we should probably stop being so lazy and try to figure out _what_ is
happening when it reconnects and whether it is even a kernel bug. It
might be something normal (like rekeying) not being handled well by
userspace.
Whatever it is, it seems that the kernel can help, since the
proprietary Broadcom wl driver works better if I have understood
Camaleón correctly.
Thanks,
Jonathan
--
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
