mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Fengguang Wu <fengguang.wu@intel.com>
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 15:20:40 +0200	[thread overview]
Message-ID: <1339593640.4519.39.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20120613131725.GA2052@localhost> (sfid-20120613_151753_455745_D624F0E8)

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


johannes


  reply	other threads:[~2012-06-13 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 13:17 Fengguang Wu
2012-06-13 13:20 ` Johannes Berg [this message]
2012-06-13 13:32   ` Fengguang Wu

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=1339593640.4519.39.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=emmanuel.grumbach@intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=ilw@linux.intel.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

all inboxes | Powered by JetHome®