From: Tejun Heo <tj@kernel.org>
To: Anders Kaseorg <andersk@MIT.EDU>
Cc: Herbert Xu <herbert@gondor.hengli.com.au>,
"John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Wireless regression in workqueue: use mod_delayed_work() instead of __cancel + queue
Date: Fri, 30 Nov 2012 13:14:35 -0800 [thread overview]
Message-ID: <20121130211435.GJ3873@htj.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1211281016320.26602@dr-wily.mit.edu>
Hello, Anders.
Sorry about the delay.
On Wed, Nov 28, 2012 at 10:17:28AM -0500, Anders Kaseorg wrote:
> On Wed, 28 Nov 2012, Anders Kaseorg wrote:
> > My Intel 6250 wireless card (iwldvm) can no longer associate with a
> > WPA-Enterprise network (PEAP-MSCHAPv2). To my surprise, I bisected this
> > regression to commit e7c2f967445dd2041f0f8e3179cca22bb8bb7f79,
> > workqueue: use mod_delayed_work() instead of __cancel + queue.
I see.
> > A bunch of logs collected by Ubuntu apport are in this bug report:
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1083980
> >
> > How can I help to debug this?
> >
> > I see that someone else reported another regression with the same commit
> > last week, although this looks unrelated at first glance:
> > http://thread.gmane.org/gmane.linux.kernel/1395938
Urgh... that one was in my spam folder probably due to the mimed
content. Nothing rings a bell yet. Will keep looking into it.
Thanks.
--
tejun
next prev parent reply other threads:[~2012-11-30 21:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 15:13 Wireless regression in workqueue: use mod_delayed_work() instead of __cancel + queue Anders Kaseorg
2012-11-28 15:17 ` Anders Kaseorg
2012-11-30 21:14 ` Tejun Heo [this message]
2012-11-30 22:56 ` Tejun Heo
2012-12-01 4:15 ` Anders Kaseorg
2012-12-01 14:39 ` Tejun Heo
2012-12-01 23:53 ` Anders Kaseorg
2012-12-02 1:11 ` [PATCH] workqueue: mod_delayed_work_on() shouldn't queue timer on 0 delay Tejun Heo
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=20121130211435.GJ3873@htj.dyndns.org \
--to=tj@kernel.org \
--cc=andersk@MIT.EDU \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).