On Wed, Jul 21, 2010 at 10:37 PM, Guy, Wey-Yi <wey-yi.w.guy@xxxxxxxxx> wrote: > Hi drago, > On Wed, 2010-07-21 at 12:59 -0700, drago01 wrote: >> On Tue, Jul 20, 2010 at 1:56 AM, Guy, Wey-Yi <wey-yi.w.guy@xxxxxxxxx> wrote: >> > Hi drago, >> > >> > >> > Are you using 5350? here I attach a "RFC patch", could you give a try to >> > see if it help? >> >> Not quite I am on 5300; your patch seem to only touch the 5350 code >> ... should I try the same change for 5300? > > Yes, please Hi, As there is no such field in .34 I patched the .35 driver which seems to be fine with the change ... I couldn't trigger it using the close lid (no suspend) and wait a bit trick ... but I have not used it for long enough to say for certain that its gone. But unfortunately the driver has a different issue it spams my log with tons of: iwlagn 0000:02:00.0: BA scd_flow 0 does not match txq_id 10 iwlagn 0000:02:00.0: BA scd_flow 0 does not match txq_id 10 iwlagn 0000:02:00.0: BA scd_flow 0 does not match txq_id 10 iwlagn 0000:02:00.0: BA scd_flow 0 does not match txq_id 10 iwlagn 0000:02:00.0: BA scd_flow 0 does not match txq_id 10 iwlagn 0000:02:00.0: BA scd_flow 0 does not match txq_id 10 iwlagn 0000:02:00.0: BA scd_flow 0 does not match txq_id 10 iwlagn 0000:02:00.0: BA scd_flow 0 does not match txq_id 10 iwlagn 0000:02:00.0: BA scd_flow 0 does not match txq_id 10 messages. -- 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
