public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Zhu, Yi" <yi.zhu@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: mmotm 2009-04-27-15-45 uploaded - iwl3945 oops
Date: Tue, 28 Apr 2009 16:38:05 -0400	[thread overview]
Message-ID: <20090428203805.GB3321@tuxdriver.com> (raw)
In-Reply-To: <1240951184.1207.11.camel@rc-desk>

On Tue, Apr 28, 2009 at 01:39:44PM -0700, reinette chatre wrote:
> On Tue, 2009-04-28 at 10:14 -0700, Valdis.Kletnieks@vt.edu wrote:
> > On Mon, 27 Apr 2009 15:46:07 PDT, akpm@linux-foundation.org said:
> > > The mm-of-the-moment snapshot 2009-04-27-15-45 has been uploaded to
> > > 
> > >    http://userweb.kernel.org/~akpm/mmotm/
> > 
> > Saw this while booting at home, out of range of any access points I was
> > configured to associate with (there *are* 4 APs owned by neighbors that I can
> > see via kismet, but wpa_supplicant isn't configured to use them).  Didn't
> > happen this morning at my office, when there's APs in range.
> > 
> > This didn't happen in mmotm-0424, so it's something new in the last few days.
> 
> A recent patch that is related is ...
> 
> commit 4583f7455c6b668a4e9cab154b5a7b6c583b288a
> Author: Johannes Berg <johannes@sipsolutions.net>
> Date:   Thu Apr 23 10:45:04 2009 +0200
> 
>     iwlwifi: notify on scan completion even when shutting down
> 
>     Under certain circumstances iwlwifi can get stuck and will no
>     longer accept scan requests, because the core code (cfg80211)
>     thinks that it's still processing one. This fixes one of the
>     points where it can happen, but I've still seen it (although
>     only with my radio-off-when-idle patch).
>     
>     Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
>     Acked-by: Reinette Chatre <reinette.chatre@intel.com>
>     Signed-off-by: John W. Linville <linville@tuxdriver.com>
> 
> 
> Could you please revert this and test again?

I doubt if that will help -- I just put it into wireless-2.6 and
wireless-testing today.

> If this does not help, could you please bisect?

Better bet...unless you meant "apply" instead of "revert"...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-04-28 20:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200904272305.n3RN51mu031395@imap1.linux-foundation.org>
2009-04-28  4:24 ` [PATCH -mmotm] ecryptfs: fix printk format warning Randy Dunlap
2009-04-28 17:14 ` mmotm 2009-04-27-15-45 uploaded - iwl3945 oops Valdis.Kletnieks
2009-04-28 20:39   ` reinette chatre
2009-04-28 20:38     ` John W. Linville [this message]
2009-04-28 20:55       ` reinette chatre
2009-04-29 15:56     ` Valdis.Kletnieks
2009-04-30 22:46       ` reinette chatre

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=20090428203805.GB3321@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=yi.zhu@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