On Mon, 2010-05-10 at 11:36 -0700, Nils Radtke wrote: > Today weather was fine again, finally. So testing with .33.3 w/ the patch applied: > > http://marc.info/?l=linux-wireless&m=127290931304496&w=2 > > The kernel kernel .32 was still running before it crashed immediately on wireless activation. > The crash log showed again at least two messages, the last was as already described in my first > message, bug from 2010-04-30: I think even the 0x2030 was the same: > > EIP rs_tx_status +x8f/x2030 You report an issue on 2.6.32 ... > > W/ .33.3 and the above patch applied: ... but then test the patch with 2.6.33. Which kernel are you focused on? > Linux mypole 2.6.33.3 #18 SMP PREEMPT Thu May 6 21:51:37 CEST 2010 i686 GNU/Linux > > May 10 19:14:11 [ 80.586637] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now > May 10 19:23:17 [ 626.476078] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now > May 10 19:23:30 [ 638.913740] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now > May 10 19:23:32 [ 641.232425] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now > May 10 19:23:54 [ 663.392697] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now > May 10 19:23:58 [ 666.980247] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now > May 10 19:24:02 [ 671.121826] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now Can you see any impact on your connection speed that can be connected to these messages? > Additionally these were logged, could you tell why they're there and what to do? (also .33.3 w/ patch) > > May 10 19:24:16 [ 685.079617] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:12:23:25 tid = 0 > May 10 19:24:22 [ 691.026737] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:12:23:25 tid = 0 > May 10 19:28:02 [ 911.406162] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:12:23:25 tid = 0 > May 10 19:35:38 [ 1367.251240] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:12:23:25 tid = 0 > > The above "iwl_tx_agg_start" lines happen when connecting - again to a Cisco AP - and the connection gets > dropped the exact moment when a download is started. It even often drops when dhcp is still negotiating, has > got it's IP but the nego isn't finished yet. Conn drops, same procedure again and again. This happens only > with this Cisco AP (which is BTW another one from the "expected_tpt should have been calculated by now" > problem). It could be that some of the queues get stuck. Can you try with the patches in http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2037#c113 ? They are based on 2.6.33. Reinette -- 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
