On Thu, Mar 12, 2009 at 06:10:48AM +0000, Sitsofe Wheeler wrote: > On Mon, Mar 09, 2009 at 08:43:44PM -0400, Bob Copeland wrote: > > > > Ok, here's a patch, it survived a few hours of testing with 3 rx buffers. > > Sitsofe, it's worth a try applying this one, even though it probably > > isn't it :) > > I applied it yesterday and all seemed well for a few hours (suspending > and resuming a fair bit too) so I left it overnight but when I looked > this morning this is what I found: > > Just a quick heads up - I will probably lose the ability to "easily" > test this problem by the end of this month...
OK I left things overnight and this happened again with the again with the patch installed. This time I had an ftrace filter in place and I think the function trace goes back around 27 minutes. The dmesg doesn't report any jumbo frame errors but it does mention ath5k phy0: noise floor calibration timeout about two hours before the poison is overwritten. The dmesg and trace can be found on http://sucs.org/~sits/test/eeepc-debug/20090313/ . The one I'll note is that every time this issue has occurred I've been connected to encrypted networks (both WPA and WEP). -- Sitsofe | http://sucs.org/~sits/ _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
