On Tue, 2012-01-10 at 13:49 -0500, Dave Jones wrote: > For the last few releases, iwlwifi has been getting consistently worse > wrt reliability for me. The failure mode has varied, from the chip just > locking up with no tx/rx of packets with nothing being logged, to > microcode warnings, and spewing 'Tx aggregation enabled' messages over and over. You might want to CC linux-wireless@vger too... > The merge post 3.2 has made these problems a lot worse. Before, these > lock-ups were happening once or twice a day. Now they happen several times an hour > (and after the first one, they seem more frequent). When they happen, > unloading and reloading the module is the only way for me to get working wireless again. > They may happen more frequently when the laptop is not idle. > > I did a bisect of the changes since 3.2, which pointed at 76bc10fcd128ad028cf77c62e179cd20dc2ffecf > as being the culprit, but to be honest I'm not 100% convinced. > > Because every step of the way during the bisect, I saw different failure modes, > so when I marked something as 'good', it meant "doesn't lock up in the same way", > even though it may be symptomatic of the same problem. > > The specific chip I'm using is a 5300 in a Dell Adamo, connecting to > an Apple airport extreme (current model) in N mode. > > Dave > > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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
