linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Deuce <the_deuce@yahoo.com>
To: Samuel Ortiz <samuel@sortiz.org>
Cc: reinette chatre <reinette.chatre@intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: kernel BUG at drivers/net/wireless/iwlwifi/iwl3945-base.c:3127!
Date: Mon, 12 Jan 2009 19:12:59 -0800 (PST)	[thread overview]
Message-ID: <614533.26753.qm@web57611.mail.re1.yahoo.com> (raw)
In-Reply-To: 20090112183808.GA8485@sortiz.org





----- Original Message ----
> From: Samuel Ortiz <samuel@sortiz.org>
> To: Deuce <the_deuce@yahoo.com>
> Cc: reinette chatre <reinette.chatre@intel.com>; "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
> Sent: Monday, January 12, 2009 1:38:08 PM
> Subject: Re: kernel BUG at drivers/net/wireless/iwlwifi/iwl3945-base.c:3127!
> 
> Hi Jason,
> 
> On Fri, Jan 09, 2009 at 03:07:01PM -0800, Deuce wrote:
> > > From: reinette chatre 
> > 
> > > On Thu, 2009-01-08 at 19:28 -0800, Deuce wrote:
> > > > Kernel BUG in iwl3945 with 20090107 wireless-testing and firmware 
> 15.28.2.8  
> > > The Microcode SW error detected seems to be the beginning of the end.  An 
> > > attempt with Ubuntu's distributed iwlwifi-3945-1.ucode firmware was not 
> > > successful either (I do not know the version).
> > > > 
> > > > The BUG happens a short period after logging in when Netmanager starts to 
> scan 
> > > and attempt to associate.  Association never completes.
> > > > 
> > > > Curiously, the bug was not triggered the first time I finally booted up 
> with 
> > > iwl3945 debug=0x43fff and netconsole functioning.  However it was 
> immediately 
> > > triggered on a subsequent reboot.  The first try may have been a warm reboot 
> vs. 
> > > a cold reboot.
> > > > 
> > > > Below is the dmesg output without debug.  Attached is a full dmesg output 
> with 
> > > debug=0x43fff.
> > > 
> > > There appears to be a few things going on here. I am still investigating
> > > the firmware error, but we could start with something that will not let
> > > your machine crash and get us some more information about one of the
> > > issues.
> > > 
> > > Could you please try with this patch? Please do run your test with
> > > debugging enabled as you have done before. Thank you very much.
> > > 
> > > diff --git a/drivers/net/wireless/iwlwifi/iwl3945-base.c 
> > > b/drivers/net/wireless/iwlwifi/iwl3945-base.c
> > > index a23d51d..09c1c8d 100644
> > > --- a/drivers/net/wireless/iwlwifi/iwl3945-base.c
> > > +++ b/drivers/net/wireless/iwlwifi/iwl3945-base.c
> > > @@ -3118,7 +3118,14 @@ static void iwl3945_tx_cmd_complete(struct iwl_priv 
> > > *priv,
> > >     int cmd_index;
> > >     struct iwl_cmd *cmd;
> > > 
> > > -    BUG_ON(txq_id != IWL_CMD_QUEUE_NUM);
> > > +    if (WARN(txq_id != IWL_CMD_QUEUE_NUM,
> > > +         "wrong command queue %d, sequence 0x%X readp=%d writep=%d\n",
> > > +          txq_id, sequence,
> > > +          priv->txq[IWL_CMD_QUEUE_NUM].q.read_ptr,
> > > +          priv->txq[IWL_CMD_QUEUE_NUM].q.write_ptr)) {
> > > +        iwl_print_hex_dump(priv, IWL_DL_INFO , rxb, 32);
> > > +        return;
> > > +    }
> > > 
> > >     cmd_index = get_cmd_index(&priv->txq[IWL_CMD_QUEUE_NUM].q, index, huge);
> > >     cmd = priv->txq[IWL_CMD_QUEUE_NUM].cmd[cmd_index];
> > 
> > New log attached.  Only the above patch was applied to the previous code base.
> It seems you can easily reproduce this bug, but unfortunately we can't.
> Would you be able to run a code bisection on this one ? Can you try if commit
> cbd8b90ffd8a321ffb2a705733729f0d5ebb20f9 is working for you ? If that's so,
> that should let you bisect quite quickly.

First off, cbd8b90ffd8a321ffb2a705733729f0d5ebb20f9 worked fine.

I ran through the git bisect as you can see below.  However, the original BUG_ON was not triggered.  Instead, I encountered authentication time outs with my unencrypted AP.  This made the nominally straightforward good/bad bisect question a little more interesting.  When the BUG_ON was triggered, authentication did not complete either, so take for what it's worth.

Was the restriction of git bisect to drivers/net/wireless/iwlwifi a bad idea?

I'll look into actually triggering the BUG_ON proper.

Jason

$ git bisect log 
# bad: [10bc72100559eae0e27f111be96b5e4afd07a1dc] p54: power save management
# good: [cbd8b90ffd8a321ffb2a705733729f0d5ebb20f9] iwl3945: iwl3945_queue and iwl3945_channel_info replacement
git-bisect start 'master-2009-01-06' 'cbd8b90ffd8a321ffb2a705733729f0d5ebb20f9' '--' 'drivers/net/wireless/iwlwifi/'
# good: [a0dedce20b4db9e6a7200eacb4d10fc3ee4c1b6b] iwlwifi: replace IWL_ERROR with IWL_ERR
git-bisect good a0dedce20b4db9e6a7200eacb4d10fc3ee4c1b6b
# skip: [9bfb965e2826a3cc2f6abbefe59b9c3e8f0a8294] iwl3945: use iwl_get_hw_mode
# ***  authentication timed out
git-bisect skip 9bfb965e2826a3cc2f6abbefe59b9c3e8f0a8294
# bad: [ba95810656873203d14f6274f1aa73ad0b42cffe] iwl3945: release resources before shutting down
# ***  authentication timed out
git-bisect bad ba95810656873203d14f6274f1aa73ad0b42cffe
# bad: [b5e33e433937e7525c6e6102ff9b2c47c0bf8d5a] iwl3945: add load ucode op
# ***  authentication timed out
git-bisect bad b5e33e433937e7525c6e6102ff9b2c47c0bf8d5a
# bad: [259fc66b6afeb2f10bb86c7fbef541981a3216c9] iwl3945: use iwl_mod_params for 3945
# ***  authentication timed out
git-bisect bad 259fc66b6afeb2f10bb86c7fbef541981a3216c9
# good: [bb64785ad94d575fe4f5f9e69f4f6c0b24e9905d] iwlwifi: use iwl_cmd instead of iwl3945_cmd
git-bisect good bb64785ad94d575fe4f5f9e69f4f6c0b24e9905d


259fc66b6afeb2f10bb86c7fbef541981a3216c9 is first bad commit
commit 259fc66b6afeb2f10bb86c7fbef541981a3216c9
Author: Kolekar, Abhijeet <abhijeet.kolekar@intel.com>
Date:   Fri Dec 19 10:37:35 2008 +0800

    iwl3945: use iwl_mod_params for 3945
    
    Use iwl_mod_params for 3945.
    
    Signed-off-by: Abhijeet Kolekar <abhijeet.kolekar@intel.com>
    Signed-off-by: Zhu Yi <yi.zhu@intel.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

:040000 040000 13a738ff0a9b89db4838c70937f32a6434a0384f 32eabfca375a07a548cf3b4323d1edb550474d4f M    drivers


      

  reply	other threads:[~2009-01-13  3:13 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09  3:28 kernel BUG at drivers/net/wireless/iwlwifi/iwl3945-base.c:3127! Deuce
2009-01-09 19:12 ` reinette chatre
2009-01-09 23:07   ` Deuce
2009-01-12 18:38     ` Samuel Ortiz
2009-01-13  3:12       ` Deuce [this message]
2009-01-13  4:37         ` Deuce
  -- strict thread matches above, loose matches on Subject: below --
2009-01-18  0:06 Deuce
2009-01-18 17:41 ` Deuce
2009-01-26 11:44 ` Samuel Ortiz
2009-01-27  3:13   ` Jason Andryuk
2009-01-27  3:35     ` Jason Andryuk
2009-01-27 16:24       ` Samuel Ortiz
2009-01-27 23:31         ` Jason Andryuk
2009-01-28  7:12           ` Tomas Winkler
2009-01-28 11:37             ` Samuel Ortiz
2009-01-28 11:52               ` Tomas Winkler
2009-01-28 12:12                 ` Samuel Ortiz
2009-02-20  4:17                   ` Jason Andryuk
2009-02-20 19:49                     ` reinette chatre
2009-02-23  0:10                       ` Jason Andryuk
2009-02-23  4:37                         ` Jason Andryuk
2009-02-23 19:21                           ` reinette chatre
2009-02-23 22:28                           ` reinette chatre
2009-02-24  3:02                             ` Jason Andryuk
2009-02-24  0:15                           ` reinette chatre
2009-02-24  2:47                             ` Jason Andryuk
2009-03-02  3:37               ` Jason Andryuk
2009-03-04  4:32                 ` Jason Andryuk
2009-03-04 19:19                   ` reinette chatre
2009-03-04 19:47                     ` Jason Andryuk
2009-03-05  0:04                       ` reinette chatre
2009-03-05 23:50                         ` Jason Andryuk
2009-03-06  0:24                           ` reinette chatre
2009-03-06  4:12                             ` Jason Andryuk
2009-03-06  5:39                               ` reinette chatre
2009-03-10  1:40                                 ` Jason Andryuk
2009-03-10  3:32                                   ` Jason Andryuk
2009-03-10  5:04                                   ` reinette chatre
2009-03-10 13:10                                     ` Jason Andryuk
2009-03-10 18:22                                       ` Abhijeet Kolekar
2009-03-11  3:11                                         ` Jason Andryuk
2009-03-11  2:57                                       ` Jason Andryuk
2009-03-11  3:40                                     ` Jason Andryuk
2009-03-13  3:31                                       ` Jason Andryuk
2009-03-16 12:10                                         ` Jason Andryuk
2009-03-17  1:44                                           ` Jason Andryuk
2009-03-19  1:52                                             ` Jason Andryuk
2009-03-20  1:22                                               ` Jason Andryuk
2009-03-20 20:39                                                 ` Abhijeet Kolekar
2009-03-22 17:29                                                   ` Jason Andryuk
2009-03-23  0:37                                                     ` Jason Andryuk
2009-03-27 16:28                                                       ` reinette chatre
2009-03-31 22:22                                                       ` reinette chatre
2009-04-01  1:28                                                         ` Jason Andryuk
2009-04-21  1:41                                                         ` Jason Andryuk
2009-04-21 15:42                                                           ` 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=614533.26753.qm@web57611.mail.re1.yahoo.com \
    --to=the_deuce@yahoo.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=samuel@sortiz.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).