From: reinette chatre <reinette.chatre@intel.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: Samuel Ortiz <samuel@sortiz.org>,
Tomas Winkler <tomasw@gmail.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: Thu, 05 Mar 2009 16:24:45 -0800 [thread overview]
Message-ID: <1236299085.6612.229.camel@rc-desk> (raw)
In-Reply-To: <1236297052.6153.4.camel@rainbow>
On Thu, 2009-03-05 at 15:50 -0800, Jason Andryuk wrote:
> On Wed, 2009-03-04 at 16:04 -0800, reinette chatre wrote:
> > On Wed, 2009-03-04 at 11:47 -0800, Jason Andryuk wrote:
> > > On Wed, Mar 4, 2009 at 2:19 PM, reinette chatre
> > > <reinette.chatre@intel.com> wrote:
> > > > On Tue, 2009-03-03 at 20:32 -0800, Jason Andryuk wrote:
> > > >> On Sun, Mar 1, 2009 at 10:37 PM, Jason Andryuk <jandryuk@gmail.com> wrote:
> > > >> > I tested c2a0aa3cb733452e749727680e380dca6cc10a68 "iwl3945: use
> > > >> > iwl_rb_status" with the additional patches to initialize rb_stts
> > > >> > (copied from iwl_rx_queue_alloc) and to convert the BUG_ON to a
> > > >> > WARN_ON.
> > > >> >
> > > >> > The driver runs without segfaulting. So far the WARN_ON has not been
> > > >> > triggered, but the driver fails to finish authentication with the AP.
> > > >> > I receive "wlan0: authentication with AP 00:30:bd:c0:90:24 timed out"
> > > >>
> > > >> Ok, I started poking around with manually checking interesting commits instead of git bisect.
> > > >>
> > > >> 55b3e21... iwl3945: use iwl-io.h and delete iwl-3945-io.h with BUG->WARN patch works.
> > > >>
> > > >> bb64785... iwlwifi: use iwl_cmd instead of iwl3945_cmd
> > > >> fails to authenticate to the AP. It generates a Microcode SW Error attached below.
> > > >>
> > > >> The previous revision:
> > > >> a0dedce... iwlwifi: replace IWL_ERROR with IWL_ERR
> > > >> Authenticates to the AP and works just fine.
> > > >>
> > > >> I keep looking over commitdiff bb64785... but I cannot see what is causing problems. I even tried modifying iwl3945_cmd in various ways from a0dedce... but those attempts kept working.
> > > >>
> > > >> During testing, I saw a lot of UNKNOWN 0x1b
> > > >> [ 8892.625374] ieee80211 phy0: I iwl3945_rx_handle r = 162, i = 160, UNKNOWN, 0x1b
> > > >> Currently in the logs for commit a0dedce... it shows up as REPLY_3945_RX.
> > > >>
> > > >> Any ideas?
> > > >
> > > > Thank you very much for this digging.
> > > >
> > > > Are you running on 64bit?
> > >
> > > Yes, 64bit.
> >
> > could you please try this patch on top of latest wireless-testing?
> >
> > Thanks
> >
> > Reinette
> >
> >
> > diff --git a/drivers/net/wireless/iwlwifi/iwl-3945.c b/drivers/net/wireless/iwlwifi/iwl-3945.c
> > index 0a75053..00b25a8 100644
> > --- a/drivers/net/wireless/iwlwifi/iwl-3945.c
> > +++ b/drivers/net/wireless/iwlwifi/iwl-3945.c
> > @@ -743,6 +743,7 @@ void iwl3945_hw_txq_free_tfd(struct iwl_priv *priv, struct iwl_tx_queue *txq)
> > struct iwl3945_tfd *tfd_tmp = (struct iwl3945_tfd *)txq->tfds;
> > struct iwl3945_tfd *tfd = &tfd_tmp[txq->q.read_ptr];
> > struct pci_dev *dev = priv->pci_dev;
> > + int index = txq->q.read_ptr;
> > int i;
> > int counter;
> >
> > @@ -759,6 +760,13 @@ void iwl3945_hw_txq_free_tfd(struct iwl_priv *priv, struct iwl_tx_queue *txq)
> > return;
> > }
> >
> > + /* Unmap tx_cmd */
> > + if (counter)
> > + pci_unmap_single(dev,
> > + pci_unmap_addr(&txq->cmd[index]->meta, mapping),
> > + pci_unmap_len(&txq->cmd[index]->meta, len),
> > + PCI_DMA_TODEVICE);
> > +
> > /* unmap chunks if any */
> >
> > for (i = 1; i < counter; i++) {
>
> Reinette,
>
> I applied the patch, but iwl3945 did not authenticate with my AP
>
oh no.
I will install a 64bit system here to try and reproduce this ...
Reinette
next prev parent reply other threads:[~2009-03-06 0:19 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 0:06 kernel BUG at drivers/net/wireless/iwlwifi/iwl3945-base.c:3127! 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-01-09 3:28 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
2009-01-13 4:37 ` Deuce
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=1236299085.6612.229.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=jandryuk@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=samuel@sortiz.org \
--cc=tomasw@gmail.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;
as well as URLs for NNTP newsgroup(s).