* iwlagn and many firmware restarts with Fedora kernel @ 2010-07-19 18:43 Marcel Holtmann 2010-07-19 22:23 ` Guy, Wey-Yi W 2010-07-19 22:33 ` drago01 0 siblings, 2 replies; 13+ messages in thread From: Marcel Holtmann @ 2010-07-19 18:43 UTC (permalink / raw) To: linux-wireless Hi, so during the last few weeks, I have seen a huge amount of firmware restarts with my Intel 5350 card and Fedora 13 kernel (2.6.33.6-147). iwlagn 0000:03:00.0: low ack count detected, restart firmware iwlagn 0000:03:00.0: On demand firmware reload iwlagn 0000:03:00.0: Stopping AGG while state not ON or starting iwlagn 0000:03:00.0: queue number out of range: 0, must be 10 to 19 If this happens then I don't see it once, I normally see this 10-20 times and the connectivity is stalled until the cards comes back to life. I have seen patches that should have fixed this symptom, but they might be also send to -stable since this is a major hassle. The time without connectivity is something around 4-5 minutes or longer when this happens. Not really funny. Regards Marcel ^ permalink raw reply [flat|nested] 13+ messages in thread
* RE: iwlagn and many firmware restarts with Fedora kernel 2010-07-19 18:43 iwlagn and many firmware restarts with Fedora kernel Marcel Holtmann @ 2010-07-19 22:23 ` Guy, Wey-Yi W 2010-07-19 23:28 ` Marcel Holtmann 2010-07-19 22:33 ` drago01 1 sibling, 1 reply; 13+ messages in thread From: Guy, Wey-Yi W @ 2010-07-19 22:23 UTC (permalink / raw) To: Marcel Holtmann, linux-wireless@vger.kernel.org SGkgTWFyY2VsLA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogbGludXgtd2ly ZWxlc3Mtb3duZXJAdmdlci5rZXJuZWwub3JnIFttYWlsdG86bGludXgtd2lyZWxlc3Mtb3duZXJA dmdlci5rZXJuZWwub3JnXSBPbiBCZWhhbGYgT2YgTWFyY2VsIEhvbHRtYW5uDQpTZW50OiBNb25k YXksIEp1bHkgMTksIDIwMTAgMTE6NDQgQU0NClRvOiBsaW51eC13aXJlbGVzc0B2Z2VyLmtlcm5l bC5vcmcNClN1YmplY3Q6IGl3bGFnbiBhbmQgbWFueSBmaXJtd2FyZSByZXN0YXJ0cyB3aXRoIEZl ZG9yYSBrZXJuZWwNCg0KSGksDQoNCnNvIGR1cmluZyB0aGUgbGFzdCBmZXcgd2Vla3MsIEkgaGF2 ZSBzZWVuIGEgaHVnZSBhbW91bnQgb2YgZmlybXdhcmUNCnJlc3RhcnRzIHdpdGggbXkgSW50ZWwg NTM1MCBjYXJkIGFuZCBGZWRvcmEgMTMga2VybmVsICgyLjYuMzMuNi0xNDcpLg0KDQppd2xhZ24g MDAwMDowMzowMC4wOiBsb3cgYWNrIGNvdW50IGRldGVjdGVkLCByZXN0YXJ0IGZpcm13YXJlDQpp d2xhZ24gMDAwMDowMzowMC4wOiBPbiBkZW1hbmQgZmlybXdhcmUgcmVsb2FkDQppd2xhZ24gMDAw MDowMzowMC4wOiBTdG9wcGluZyBBR0cgd2hpbGUgc3RhdGUgbm90IE9OIG9yIHN0YXJ0aW5nDQpp d2xhZ24gMDAwMDowMzowMC4wOiBxdWV1ZSBudW1iZXIgb3V0IG9mIHJhbmdlOiAwLCBtdXN0IGJl IDEwIHRvIDE5DQoNCklmIHRoaXMgaGFwcGVucyB0aGVuIEkgZG9uJ3Qgc2VlIGl0IG9uY2UsIEkg bm9ybWFsbHkgc2VlIHRoaXMgMTAtMjANCnRpbWVzIGFuZCB0aGUgY29ubmVjdGl2aXR5IGlzIHN0 YWxsZWQgdW50aWwgdGhlIGNhcmRzIGNvbWVzIGJhY2sgdG8NCmxpZmUuIEkgaGF2ZSBzZWVuIHBh dGNoZXMgdGhhdCBzaG91bGQgaGF2ZSBmaXhlZCB0aGlzIHN5bXB0b20sIGJ1dCB0aGV5DQptaWdo dCBiZSBhbHNvIHNlbmQgdG8gLXN0YWJsZSBzaW5jZSB0aGlzIGlzIGEgbWFqb3IgaGFzc2xlLg0K DQpUaGUgdGltZSB3aXRob3V0IGNvbm5lY3Rpdml0eSBpcyBzb21ldGhpbmcgYXJvdW5kIDQtNSBt aW51dGVzIG9yIGxvbmdlcg0Kd2hlbiB0aGlzIGhhcHBlbnMuIE5vdCByZWFsbHkgZnVubnkuDQoN CldoaWNoIHBhdGNoIHlvdSByZWZlcnJpbmcgdG8/IEkgd2lsbCB0cnkgdG8gd29yayBvbiBzdWJt aXQgaXQgdG8gc3RhYmxlLg0KDQpUaGFua3MNCldleQ0K ^ permalink raw reply [flat|nested] 13+ messages in thread
* RE: iwlagn and many firmware restarts with Fedora kernel 2010-07-19 22:23 ` Guy, Wey-Yi W @ 2010-07-19 23:28 ` Marcel Holtmann 0 siblings, 0 replies; 13+ messages in thread From: Marcel Holtmann @ 2010-07-19 23:28 UTC (permalink / raw) To: Guy, Wey-Yi W; +Cc: linux-wireless@vger.kernel.org Hi Wey, > so during the last few weeks, I have seen a huge amount of firmware > restarts with my Intel 5350 card and Fedora 13 kernel (2.6.33.6-147). > > iwlagn 0000:03:00.0: low ack count detected, restart firmware > iwlagn 0000:03:00.0: On demand firmware reload > iwlagn 0000:03:00.0: Stopping AGG while state not ON or starting > iwlagn 0000:03:00.0: queue number out of range: 0, must be 10 to 19 > > If this happens then I don't see it once, I normally see this 10-20 > times and the connectivity is stalled until the cards comes back to > life. I have seen patches that should have fixed this symptom, but they > might be also send to -stable since this is a major hassle. > > The time without connectivity is something around 4-5 minutes or longer > when this happens. Not really funny. > > Which patch you referring to? I will try to work on submit it to stable. no patch in particular, I just have seen some commit messages that would be indicating this got fixed. Regards Marcel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: iwlagn and many firmware restarts with Fedora kernel 2010-07-19 18:43 iwlagn and many firmware restarts with Fedora kernel Marcel Holtmann 2010-07-19 22:23 ` Guy, Wey-Yi W @ 2010-07-19 22:33 ` drago01 2010-07-19 23:29 ` Marcel Holtmann 1 sibling, 1 reply; 13+ messages in thread From: drago01 @ 2010-07-19 22:33 UTC (permalink / raw) To: Marcel Holtmann; +Cc: linux-wireless On Mon, Jul 19, 2010 at 8:43 PM, Marcel Holtmann <marcel@holtmann.org> wrote: > Hi, > > so during the last few weeks, I have seen a huge amount of firmware > restarts with my Intel 5350 card and Fedora 13 kernel (2.6.33.6-147). > > iwlagn 0000:03:00.0: low ack count detected, restart firmware > iwlagn 0000:03:00.0: On demand firmware reload > iwlagn 0000:03:00.0: Stopping AGG while state not ON or starting > iwlagn 0000:03:00.0: queue number out of range: 0, must be 10 to 19 > > If this happens then I don't see it once, I normally see this 10-20 > times and the connectivity is stalled until the cards comes back to > life. I have seen patches that should have fixed this symptom, but they > might be also send to -stable since this is a major hassle. > > The time without connectivity is something around 4-5 minutes or longer > when this happens. Not really funny. This happens here too even with the 2.6.34.1-9.fc13.x86_64 kernel; when this happens reloading the iwlagn module seems to be the only (quick) way to get it back to life. ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: iwlagn and many firmware restarts with Fedora kernel 2010-07-19 22:33 ` drago01 @ 2010-07-19 23:29 ` Marcel Holtmann 2010-07-19 23:56 ` Guy, Wey-Yi 0 siblings, 1 reply; 13+ messages in thread From: Marcel Holtmann @ 2010-07-19 23:29 UTC (permalink / raw) To: drago01; +Cc: linux-wireless Hi, > > so during the last few weeks, I have seen a huge amount of firmware > > restarts with my Intel 5350 card and Fedora 13 kernel (2.6.33.6-147). > > > > iwlagn 0000:03:00.0: low ack count detected, restart firmware > > iwlagn 0000:03:00.0: On demand firmware reload > > iwlagn 0000:03:00.0: Stopping AGG while state not ON or starting > > iwlagn 0000:03:00.0: queue number out of range: 0, must be 10 to 19 > > > > If this happens then I don't see it once, I normally see this 10-20 > > times and the connectivity is stalled until the cards comes back to > > life. I have seen patches that should have fixed this symptom, but they > > might be also send to -stable since this is a major hassle. > > > > The time without connectivity is something around 4-5 minutes or longer > > when this happens. Not really funny. > > This happens here too even with the 2.6.34.1-9.fc13.x86_64 kernel; > when this happens reloading the iwlagn module seems to be the only > (quick) way to get it back to life. the quick way is re-loading the module, that is true. Otherwise you have to sit it out. It always comes back nicely and starts working again. Regards Marcel ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: iwlagn and many firmware restarts with Fedora kernel 2010-07-19 23:29 ` Marcel Holtmann @ 2010-07-19 23:56 ` Guy, Wey-Yi 2010-07-21 19:59 ` drago01 0 siblings, 1 reply; 13+ messages in thread From: Guy, Wey-Yi @ 2010-07-19 23:56 UTC (permalink / raw) To: Marcel Holtmann; +Cc: drago01, linux-wireless@vger.kernel.org [-- Attachment #1: Type: text/plain, Size: 1366 bytes --] Hi drago, On Mon, 2010-07-19 at 16:29 -0700, Marcel Holtmann wrote: > Hi, > > > > so during the last few weeks, I have seen a huge amount of firmware > > > restarts with my Intel 5350 card and Fedora 13 kernel (2.6.33.6-147). > > > > > > iwlagn 0000:03:00.0: low ack count detected, restart firmware > > > iwlagn 0000:03:00.0: On demand firmware reload > > > iwlagn 0000:03:00.0: Stopping AGG while state not ON or starting > > > iwlagn 0000:03:00.0: queue number out of range: 0, must be 10 to 19 > > > > > > If this happens then I don't see it once, I normally see this 10-20 > > > times and the connectivity is stalled until the cards comes back to > > > life. I have seen patches that should have fixed this symptom, but they > > > might be also send to -stable since this is a major hassle. > > > > > > The time without connectivity is something around 4-5 minutes or longer > > > when this happens. Not really funny. > > > > This happens here too even with the 2.6.34.1-9.fc13.x86_64 kernel; > > when this happens reloading the iwlagn module seems to be the only > > (quick) way to get it back to life. > > the quick way is re-loading the module, that is true. Otherwise you have > to sit it out. It always comes back nicely and starts working again. > Are you using 5350? here I attach a "RFC patch", could you give a try to see if it help? Regards Wey [-- Attachment #2: 0001-iwlwifi-extend-the-stuck-queue-monitor-timer-for-53.patch --] [-- Type: text/x-patch, Size: 1715 bytes --] >From d399851898df57fc03d513c2a336d3f3745b0d10 Mon Sep 17 00:00:00 2001 From: Wey-Yi Guy <wey-yi.w.guy@intel.com> Date: Mon, 19 Jul 2010 16:38:19 -0700 Subject: [PATCH 1/1] iwlwifi: extend the stuck queue monitor timer for 5350 device Different hardware has differnet behavior, extend the monitor period timer from 1 second to 5 seconds to avoid the un-necessary firmware reload Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com> --- drivers/net/wireless/iwlwifi/iwl-5000.c | 2 +- drivers/net/wireless/iwlwifi/iwl-dev.h | 1 + 2 files changed, 2 insertions(+), 1 deletions(-) diff --git a/drivers/net/wireless/iwlwifi/iwl-5000.c b/drivers/net/wireless/iwlwifi/iwl-5000.c index 68e282b..4325a53 100644 --- a/drivers/net/wireless/iwlwifi/iwl-5000.c +++ b/drivers/net/wireless/iwlwifi/iwl-5000.c @@ -642,7 +642,7 @@ struct iwl_cfg iwl5350_agn_cfg = { .chain_noise_num_beacons = IWL_CAL_NUM_BEACONS, .plcp_delta_threshold = IWL_MAX_PLCP_ERR_LONG_THRESHOLD_DEF, .chain_noise_scale = 1000, - .monitor_recover_period = IWL_MONITORING_PERIOD, + .monitor_recover_period = IWL_LONG_MONITORING_PERIOD, .max_event_log_size = 512, .ucode_tracing = true, .sensitivity_calib_by_driver = true, diff --git a/drivers/net/wireless/iwlwifi/iwl-dev.h b/drivers/net/wireless/iwlwifi/iwl-dev.h index 30853c8..d439b80 100644 --- a/drivers/net/wireless/iwlwifi/iwl-dev.h +++ b/drivers/net/wireless/iwlwifi/iwl-dev.h @@ -1051,6 +1051,7 @@ struct iwl_event_log { /* timer constants use to monitor and recover stuck tx queues in mSecs */ #define IWL_MONITORING_PERIOD (1000) +#define IWL_LONG_MONITORING_PERIOD (5000) #define IWL_ONE_HUNDRED_MSECS (100) #define IWL_SIXTY_SECS (60000) -- 1.5.6.3 ^ permalink raw reply related [flat|nested] 13+ messages in thread
* Re: iwlagn and many firmware restarts with Fedora kernel 2010-07-19 23:56 ` Guy, Wey-Yi @ 2010-07-21 19:59 ` drago01 2010-07-21 20:37 ` Guy, Wey-Yi 0 siblings, 1 reply; 13+ messages in thread From: drago01 @ 2010-07-21 19:59 UTC (permalink / raw) To: Guy, Wey-Yi; +Cc: Marcel Holtmann, linux-wireless@vger.kernel.org On Tue, Jul 20, 2010 at 1:56 AM, Guy, Wey-Yi <wey-yi.w.guy@intel.com> 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? ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: iwlagn and many firmware restarts with Fedora kernel 2010-07-21 19:59 ` drago01 @ 2010-07-21 20:37 ` Guy, Wey-Yi 2010-07-21 21:00 ` drago01 0 siblings, 1 reply; 13+ messages in thread From: Guy, Wey-Yi @ 2010-07-21 20:37 UTC (permalink / raw) To: drago01; +Cc: Marcel Holtmann, linux-wireless@vger.kernel.org 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@intel.com> 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 Thanks Wey ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: iwlagn and many firmware restarts with Fedora kernel 2010-07-21 20:37 ` Guy, Wey-Yi @ 2010-07-21 21:00 ` drago01 2010-07-22 18:37 ` Guy, Wey-Yi 0 siblings, 1 reply; 13+ messages in thread From: drago01 @ 2010-07-21 21:00 UTC (permalink / raw) To: Guy, Wey-Yi; +Cc: Marcel Holtmann, linux-wireless@vger.kernel.org On Wed, Jul 21, 2010 at 10:37 PM, Guy, Wey-Yi <wey-yi.w.guy@intel.com> 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@intel.com> 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. ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: iwlagn and many firmware restarts with Fedora kernel 2010-07-21 21:00 ` drago01 @ 2010-07-22 18:37 ` Guy, Wey-Yi 2010-07-23 22:32 ` drago01 0 siblings, 1 reply; 13+ messages in thread From: Guy, Wey-Yi @ 2010-07-22 18:37 UTC (permalink / raw) To: drago01; +Cc: Marcel Holtmann, linux-wireless@vger.kernel.org Hi drago, On Wed, 2010-07-21 at 14:00 -0700, drago01 wrote: > On Wed, Jul 21, 2010 at 10:37 PM, Guy, Wey-Yi <wey-yi.w.guy@intel.com> 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@intel.com> 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 > Yes, I aware of this, this is introduced by a recent patch commit d9763a384216336e180399b69461eae37f6c4f54 I will work on a new patch to help address this. Thanks Wey ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: iwlagn and many firmware restarts with Fedora kernel 2010-07-22 18:37 ` Guy, Wey-Yi @ 2010-07-23 22:32 ` drago01 2010-07-24 4:34 ` Guy, Wey-Yi W 0 siblings, 1 reply; 13+ messages in thread From: drago01 @ 2010-07-23 22:32 UTC (permalink / raw) To: Guy, Wey-Yi; +Cc: Marcel Holtmann, linux-wireless@vger.kernel.org On Thu, Jul 22, 2010 at 8:37 PM, Guy, Wey-Yi <wey-yi.w.guy@intel.com> wrote: > Hi drago, > > > On Wed, 2010-07-21 at 14:00 -0700, drago01 wrote: >> On Wed, Jul 21, 2010 at 10:37 PM, Guy, Wey-Yi <wey-yi.w.guy@intel.com> 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@intel.com> 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 >> > Yes, I aware of this, this is introduced by a recent patch > commit d9763a384216336e180399b69461eae37f6c4f54 > > I will work on a new patch to help address this. OK, as for the other patch after a day in use I could not trigger the problem so it does indeed fix it. Thanks ^ permalink raw reply [flat|nested] 13+ messages in thread
* RE: iwlagn and many firmware restarts with Fedora kernel 2010-07-23 22:32 ` drago01 @ 2010-07-24 4:34 ` Guy, Wey-Yi W 2010-07-25 21:25 ` drago01 0 siblings, 1 reply; 13+ messages in thread From: Guy, Wey-Yi W @ 2010-07-24 4:34 UTC (permalink / raw) To: drago01; +Cc: Marcel Holtmann, linux-wireless@vger.kernel.org Hi drago, -----Original Message----- From: drago01 [mailto:drago01@gmail.com] Sent: Friday, July 23, 2010 3:32 PM To: Guy, Wey-Yi W Cc: Marcel Holtmann; linux-wireless@vger.kernel.org Subject: Re: iwlagn and many firmware restarts with Fedora kernel On Thu, Jul 22, 2010 at 8:37 PM, Guy, Wey-Yi <wey-yi.w.guy@intel.com> wrote: > Hi drago, > > > On Wed, 2010-07-21 at 14:00 -0700, drago01 wrote: >> On Wed, Jul 21, 2010 at 10:37 PM, Guy, Wey-Yi <wey-yi.w.guy@intel.com> 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@intel.com> 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 >> > Yes, I aware of this, this is introduced by a recent patch > commit d9763a384216336e180399b69461eae37f6c4f54 > > I will work on a new patch to help address this. OK, as for the other patch after a day in use I could not trigger the problem so it does indeed fix it. Great, thank you very much for testing it. I will prepare the patch for upstream. Btw, I also have patch to help the other problem you encounter. Wey ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: iwlagn and many firmware restarts with Fedora kernel 2010-07-24 4:34 ` Guy, Wey-Yi W @ 2010-07-25 21:25 ` drago01 0 siblings, 0 replies; 13+ messages in thread From: drago01 @ 2010-07-25 21:25 UTC (permalink / raw) To: Guy, Wey-Yi W; +Cc: Marcel Holtmann, linux-wireless@vger.kernel.org On Sat, Jul 24, 2010 at 6:34 AM, Guy, Wey-Yi W <wey-yi.w.guy@intel.com> wrote: > > Great, thank you very much for testing it. I will prepare the patch for upstream. OK, thanks please don't forgot about stable as it seems that both .33 and .34 are affected too. > Btw, I also have patch to help the other problem you encounter. OK, thanks I'll test it once it shows up. ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2010-07-25 21:25 UTC | newest] Thread overview: 13+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2010-07-19 18:43 iwlagn and many firmware restarts with Fedora kernel Marcel Holtmann 2010-07-19 22:23 ` Guy, Wey-Yi W 2010-07-19 23:28 ` Marcel Holtmann 2010-07-19 22:33 ` drago01 2010-07-19 23:29 ` Marcel Holtmann 2010-07-19 23:56 ` Guy, Wey-Yi 2010-07-21 19:59 ` drago01 2010-07-21 20:37 ` Guy, Wey-Yi 2010-07-21 21:00 ` drago01 2010-07-22 18:37 ` Guy, Wey-Yi 2010-07-23 22:32 ` drago01 2010-07-24 4:34 ` Guy, Wey-Yi W 2010-07-25 21:25 ` drago01
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).