public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Cahill, Ben M" <ben.m.cahill@intel.com>
Cc: iwlwifi maling list <ipw3945-devel@lists.sourceforge.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: RE: [ipw3945-devel] iwl3945 microcode errors
Date: Sat, 07 Nov 2009 00:12:38 +0200	[thread overview]
Message-ID: <1257545558.4048.4.camel@maxim-laptop> (raw)
In-Reply-To: <02B3067C068D0549A8CCFCB17D4D318B4B095E52@orsmsx502.amr.corp.intel.com>

On Mon, 2009-11-02 at 18:07 -0800, Cahill, Ben M wrote: 
> Thanks for the report; disappointing news.
Oops. I reported a bug I introduced....
http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2113

I take a look at the issue.

Sorry.
Best regards,
Maxim Levitsky

> 
> Don't forget to load driver with debug=0x43fff, to get Error and Event logs.
> 
> -- Ben -- 
> 
> >-----Original Message-----
> >From: Maxim Levitsky [mailto:maximlevitsky@gmail.com] 
> >Sent: Monday, November 02, 2009 7:40 PM
> >To: iwlwifi maling list; linux-wireless
> >Subject: [ipw3945-devel] iwl3945 microcode errors
> >
> >I see that iwl3945 began to show some microcode errors like that:
> >
> >[   18.259947] iwl3945 0000:06:00.0: firmware: requesting 
> >iwlwifi-3945-2.ucode
> >[   18.766225] iwl3945 0000:06:00.0: loaded firmware version 15.32.2.9
> >[   18.817952] iwl3945 0000:06:00.0: Microcode SW error 
> >detected. Restarting 0x82000008.
> >[   18.817971] iwl3945 0000:06:00.0: Error Reply type 
> >0x00000000 cmd UNKNOWN (0x88) seq 0xDB3B ser 0x00880000
> >[   18.822468] iwl3945 0000:06:00.0: Can't stop Rx DMA.
> >[   20.790058] iwl3945 0000:06:00.0: Wait for START_ALIVE 
> >timeout after 2000ms.
> >
> >Now it still works, but there were cases it didn't.
> >
> >I post more detailed info soon.
> >
> >Best regards,
> >	Maxim Levitsky
> >
> >
> >---------------------------------------------------------------
> >---------------
> >Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> >is the only developer event you need to attend this year. 
> >Jumpstart your
> >developing skills, take BlackBerry mobile applications to 
> >market and stay 
> >ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> >http://p.sf.net/sfu/devconference
> >_______________________________________________
> >Ipw3945-devel mailing list
> >Ipw3945-devel@lists.sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/ipw3945-devel
> >



      reply	other threads:[~2009-11-06 22:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  0:39 iwl3945 microcode errors Maxim Levitsky
2009-11-03  2:07 ` [ipw3945-devel] " Cahill, Ben M
2009-11-06 22:12   ` Maxim Levitsky [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=1257545558.4048.4.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=ben.m.cahill@intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --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