mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [3.2-rc3] 100% CPU usage while in del_timer_sync from iwl3945_rs_free_sta
Date: Wed, 30 Nov 2011 11:10:28 +0100	[thread overview]
Message-ID: <20111130101028.GA2906@tiehlicka.suse.cz> (raw)
In-Reply-To: <20111129113906.GA7299@redhat.com>

On Tue 29-11-11 12:39:07, Stanislaw Gruszka wrote:
> Hi Michal
> 
> On Tue, Nov 29, 2011 at 11:07:27AM +0100, Michal Hocko wrote:
> > [I am not sure whether this is ieee80211 or iwl3945 issue so put both
> > maintainers into loop]
> The only changed we had in iwlegacy between 3.1 and 3.2-rc, was only 
> adjustment to mac80211 changes. However I think this is iwlegacy issue,
> just for some reason bug did not trigger before.

I have double checked 3.1 and cannot reproduce it.
Anyway, I have put:

diff --git a/drivers/net/wireless/iwlegacy/iwl-3945-rs.c b/drivers/net/wireless/iwlegacy/iwl-3945-rs.c
index 8faeaf2..9221ed4 100644
--- a/drivers/net/wireless/iwlegacy/iwl-3945-rs.c
+++ b/drivers/net/wireless/iwlegacy/iwl-3945-rs.c
@@ -432,6 +432,7 @@ static void iwl3945_rs_free_sta(void *iwl_priv, struct ieee80211_sta *sta,
 	 * to use iwl_priv to print out debugging) since it may not be fully
 	 * initialized at this point.
 	 */
+	printk("XXX: deleting time: %x\n", rs_sta->rate_scale_flush.base);
 	del_timer_sync(&rs_sta->rate_scale_flush);
 }
 
And the timer base is really NULL when the issue happens. So, somebody
probably removed the timer already?

> Is this problem 100% reproducible for you ? 

Yes, it seems to be sufficient to suspend to RAM while associated and
turn off the AP before waking up the machine.
I wasn't able to reproduce just by turning of the AP while associated
without suspend.

> If so I'll try to reproduce it locally, otherwise I'll review related
> code to find reason of that problem.
> 
> Thanks
> Stanislaw 

Thanks

-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

  reply	other threads:[~2011-11-30 10:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 10:07 Michal Hocko
2011-11-29 11:39 ` Stanislaw Gruszka
2011-11-30 10:10   ` Michal Hocko [this message]
2011-11-30 14:23     ` Stanislaw Gruszka
2011-11-30 14:03       ` Michal Hocko
2011-11-30 15:39         ` Stanislaw Gruszka
2011-12-01  8:58           ` Michal Hocko
2011-12-01 10:55             ` Michal Hocko
2011-12-01 11:59               ` Stanislaw Gruszka
2011-12-01 12:44                 ` Michal Hocko
2011-12-01 12:55                   ` Stanislaw Gruszka
2011-12-01 13:13                     ` Eliad Peller
2011-12-01 13:31                       ` Stanislaw Gruszka
2011-12-01 13:37                       ` Sedat Dilek
2011-12-01 14:05                   ` Michal Hocko
2011-12-01 14:23                     ` Eliad Peller
2011-12-01 15:45                       ` John W. Linville
2011-12-01 12:04               ` Yong Zhang
2011-12-01 12:42                 ` Michal Hocko
2011-12-01  2:09 ` Yong Zhang

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=20111130101028.GA2906@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sgruszka@redhat.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

all inboxes | Powered by JetHome®