From: "John W. Linville" <linville@tuxdriver.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-wireless@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: iwl3945 dies (oops) in post 2.6.34 kernels
Date: Tue, 25 May 2010 12:55:24 -0400 [thread overview]
Message-ID: <20100525165524.GD31753@tuxdriver.com> (raw)
In-Reply-To: <20100525163920.GA2730@core.coreip.homeip.net>
On Tue, May 25, 2010 at 09:39:20AM -0700, Dmitry Torokhov wrote:
> Hi,
>
> I am getting the following crashers in iwl3945 after updating to
> post-2.6.34 kernels. This is with the pull from Linus's tree as of last
> night (the taint is from nvidia module):
Linus doesn't have this one yet:
commit 073d5eab6fc85b6c278d507a5633b759a85dc878
Author: Reinette Chatre <reinette.chatre@intel.com>
Date: Thu May 13 14:49:44 2010 -0700
iwlwifi: fix internal scan race
It is possible for internal scan to race against itself if the device is
not returning the scan results from first requests. What happens in this
case is the cleanup done during the abort of the first internal scan also
cleans up part of the new scan, causing it to access memory it shouldn't.
...
I suspect it might be related.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-05-25 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 16:39 iwl3945 dies (oops) in post 2.6.34 kernels Dmitry Torokhov
2010-05-25 16:55 ` John W. Linville [this message]
2010-05-25 17:01 ` Johannes Berg
2010-05-25 17:08 ` Abhijeet Kolekar
2010-05-25 17:27 ` Dmitry Torokhov
2010-05-25 22:34 ` Sedat Dilek
2010-06-04 5:08 ` Dmitry Torokhov
2010-06-04 5:08 ` Abhijeet Kolekar
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=20100525165524.GD31753@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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).