From: Fengguang Wu <fengguang.wu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] iwldvm lock oops
Date: Wed, 13 Jun 2012 21:32:17 +0800 [thread overview]
Message-ID: <20120613133217.GA2170@localhost> (raw)
In-Reply-To: <1339593640.4519.39.camel@jlt3.sipsolutions.net>
Hi Johannes,
On Wed, Jun 13, 2012 at 03:20:40PM +0200, Johannes Berg wrote:
> Hi Fengguang,
>
> > The kernel compiled from commit b35032f ("iwlwifi: don't configure a
> > txq that is being disabled") in
> >
> > git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi.git master
> >
> > triggers a kernel oops below.
> >
> > That particular commit may well not be the root cause. I'm just hoping
> > you may have better idea which recent change may be relevant.
>
> Thanks for the report. This particular problem is due to the fact that
> we have the objects linked into the kernel in the wrong order, we have a
> fix pending for it. git.kernel.org is down right now so I can't link to
> it, but it's in the iwlwifi/iwlwifi-next.git tree:
>
> commit 65fe593a519c4d7c62289d3b0a17ca412e95b037
> Author: Brandon Misemer <brandon.misemer@intel.com>
> Date: Fri Jun 8 14:59:27 2012 -0700
>
> iwlwifi: Fix Makefile build order for built-in driver
Good to know this. Thank you for the quick feedback!
Thanks,
Fengguang
prev parent reply other threads:[~2012-06-13 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 13:17 [BUG] iwldvm lock oops Fengguang Wu
2012-06-13 13:20 ` Johannes Berg
2012-06-13 13:32 ` Fengguang Wu [this message]
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=20120613133217.GA2170@localhost \
--to=fengguang.wu@intel.com \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--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).