linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Jens Axboe <axboe@kernel.dk>
Cc: sara.sharon@intel.com, liad.kaufman@intel.com,
	linux-wireless@vger.kernel.org
Subject: Re: WARNING: CPU: 1 PID: 23668 at drivers/net/wireless/intel/iwlwifi/mvm/sta.c:1539 iwl_mvm_rm_sta+0x3ce/0x450
Date: Fri, 10 Mar 2017 17:36:04 +0200	[thread overview]
Message-ID: <1489160164.22435.18.camel@coelho.fi> (raw)
In-Reply-To: <aceb734b-8e2c-e5b6-300d-172f8d28f471@kernel.dk>

On Fri, 2017-03-10 at 08:23 -0700, Jens Axboe wrote:
> On 03/10/2017 05:01 AM, Luca Coelho wrote:
> > Hi Jens,
> > 
> > On Thu, 2017-03-09 at 21:41 -0700, Jens Axboe wrote:
> > > On 03/01/2017 09:10 PM, Jens Axboe wrote:
> > > > On 03/01/2017 08:33 PM, Luca Coelho wrote:
> > > > > Hi Jens,
> > > > > 
> > > > > On Mar 1, 2017 20:25, Jens Axboe <axboe@kernel.dk> wrote:
> > > > > 
> > > > >     Not that folks have been jumping all over this, but in case someone is
> > > > >     curious, it triggered twice here today. For those two times, the value
> > > > >     of mvm->pending_frames[sta_id] was 80 and 39, respectively.
> > > > > 
> > > > > Sorry for the delay, I'm on vacation now with limited internet access.
> > > > > But we'll take a look into this early next week at the latest.
> > > > > 
> > > > > Thanks a lot for the detailed report!
> > > > 
> > > > No worries, thanks for responding. I just wanted to ensure this wasn't
> > > > dropped on the floor.
> > > > 
> > > > BTW, a few more values of ->pending_frames[sta_id]:
> > > > 
> > > > $ dmesg | grep "ret="
> > > > [ 2334.308254] ret=39
> > > > [ 7915.311828] ret=80
> > > > [31602.317204] ret=41
> > > > [32139.510993] ret=54
> > > > [33292.917759] ret=96
> > > > 
> > > > it seems to often happen around resume.
> > > 
> > > This is still happening all the time in current -git.
> > 
> > Could you collect traces with trace-cmd, as explained in our wiki[1]?
> > This will probably help point out the problem.  I know it's a bit
> > difficult because it appears to happen randomly for you, but it's worth
> > trying.
> 
> Sure I can, but honestly I'm a little puzzled that nobody else can
> reproduce this, it happens every time I resume of switch access points.
> Is anyone trying to reproduce this?
> 
> I'll have to recompile with iwlwifi tracing enabled, then I'll send a trace
> when it happens.

Are you using 4.11-rc1? Or linus' master? Or...?

--
Luca.

  reply	other threads:[~2017-03-10 15:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f2bedfee-e74f-47d6-9088-94171f0e5538@email.android.com>
2017-03-02  4:10 ` WARNING: CPU: 1 PID: 23668 at drivers/net/wireless/intel/iwlwifi/mvm/sta.c:1539 iwl_mvm_rm_sta+0x3ce/0x450 Jens Axboe
2017-03-10  4:41   ` Jens Axboe
2017-03-10 12:01     ` Luca Coelho
2017-03-10 12:02       ` Coelho, Luciano
2017-03-10 15:23       ` Jens Axboe
2017-03-10 15:36         ` Luca Coelho [this message]
2017-03-10 15:41           ` Jens Axboe
2017-03-13 13:00             ` Luca Coelho
2017-03-13 13:14               ` [PATCH] iwlwifi: mvm: cleanup pending frames in DQA mode Luca Coelho
2017-03-13 14:24                 ` Jens Axboe
2017-03-13 15:08                   ` Luca Coelho
2017-03-13 14:23               ` WARNING: CPU: 1 PID: 23668 at drivers/net/wireless/intel/iwlwifi/mvm/sta.c:1539 iwl_mvm_rm_sta+0x3ce/0x450 Jens Axboe
2017-03-14  7:50               ` [RESEND PATCH 4.11] iwlwifi: mvm: cleanup pending frames in DQA mode Luca Coelho
2017-03-15  9:52                 ` Kalle Valo
2017-03-15  9:54                   ` Coelho, Luciano
2017-03-16  7:54                 ` [RESEND,4.11] " Kalle Valo
     [not found]         ` <eeb29124-0955-c2df-e39b-3981d76740a7@kernel.dk>
2017-03-10 15:42           ` WARNING: CPU: 1 PID: 23668 at drivers/net/wireless/intel/iwlwifi/mvm/sta.c:1539 iwl_mvm_rm_sta+0x3ce/0x450 Luca Coelho
2017-02-28 18:02 Jens Axboe
2017-02-28 20:41 ` Jens Axboe
2017-03-01 23:25   ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1489160164.22435.18.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=axboe@kernel.dk \
    --cc=liad.kaufman@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sara.sharon@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).