From: Zhu Yi <yi.zhu@intel.com>
To: "Cahill, Ben M" <ben.m.cahill@intel.com>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
iwlwifi maling list <ipw3945-devel@lists.sourceforge.net>
Subject: RE: [ipw3945-devel] Panic in iwl3945 driver
Date: Wed, 06 Jan 2010 11:57:05 +0800 [thread overview]
Message-ID: <1262750225.15653.113.camel@debian> (raw)
In-Reply-To: <02B3067C068D0549A8CCFCB17D4D318B5D15133F@orsmsx502.amr.corp.intel.com>
On Wed, 2010-01-06 at 06:26 +0800, Cahill, Ben M wrote:
> >><3>[ 330.762510] iwl3945 0000:06:00.0: 1035963222
> >>0x04dc0018 0401
> >
> >Last good command 0x18, with (driver provided) header
> >indicating sent via queue 4, queue index 0xdc
> >
> >><3>[ 330.762547] iwl3945 0000:06:00.0: 1035963229
> >>0x00000000 0401
> >
> >This shows command "0" (non-existant/unsupported/bad command)
> >with (driver provided) header indicating sent via queue "0",
> >index "0"; obviously bad data in command queue.
>
> Or index ("pointer") is getting out of sync. (Reminder to self; never
> use the word "obviously").
Ben, does it smell like driver issue or firmware bug?
Thanks,
-yi
next prev parent reply other threads:[~2010-01-06 3:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 16:49 Panic in iwl3945 driver Maxim Levitsky
2009-11-27 0:00 ` Maxim Levitsky
2009-11-30 15:55 ` Maxim Levitsky
2009-11-30 21:42 ` reinette chatre
2009-11-30 22:35 ` Maxim Levitsky
2009-12-01 9:28 ` Zhu Yi
2009-12-01 18:52 ` reinette chatre
2009-12-02 2:06 ` Zhu Yi
2009-12-02 5:42 ` Zhu Yi
2009-12-02 17:17 ` Maxim Levitsky
2009-12-21 16:40 ` Maxim Levitsky
2009-12-22 8:57 ` Zhu Yi
2010-01-05 16:56 ` Maxim Levitsky
2010-01-05 22:16 ` [ipw3945-devel] " Cahill, Ben M
2010-01-05 22:26 ` Cahill, Ben M
2010-01-06 3:57 ` Zhu Yi [this message]
2010-01-06 5:23 ` Cahill, Ben M
2010-01-06 3:55 ` Zhu Yi
2009-12-02 19:18 ` [ipw3945-devel] " Cahill, Ben M
2009-12-02 19:40 ` 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=1262750225.15653.113.camel@debian \
--to=yi.zhu@intel.com \
--cc=ben.m.cahill@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=reinette.chatre@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.