public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ipw3945-devel@lists.sourceforge.net"
	<ipw3945-devel@lists.sourceforge.net>
Subject: Re: iwlwifi 4965 uCode available
Date: Mon, 13 Jul 2009 08:46:19 -0700	[thread overview]
Message-ID: <1247499979.17896.1556.camel@rc-desk> (raw)
In-Reply-To: <200907121445.42289.helmut.schaa@gmail.com>

Hi Helmut,

On Sun, 2009-07-12 at 05:45 -0700, Helmut Schaa wrote:
> Am Donnerstag, 9. Juli 2009 schrieb reinette chatre:
> > Version 228.61.2.24 of uCode for Intel Wireless WiFi Link 4965AGN is now
> > available for download from
> > http://intellinuxwireless.org/?n=Downloads
> 
> The new ucode seems to cause fw restarts every now and then (together
> with wireless-testing).

oh no ...

> 
> iwlagn 0000:10:00.0: Microcode SW error detected.  Restarting 0x82000000.

What is the status when such an error occurs? Can it recover on its own
or do you need to take action? What action is needed?

> 
> I couldn't figure out how to reproduce this but it happened a few times
> now since I switched to the new ucode.
> 
> Should I load iwlagn with some special debug flags?

If your driver is compiled with CONFIG_IWLWIFI_DEBUG then you can pass a
debug flag to the module that will print a ucode event log when it
encounters a problem like this. As it will only print out the event log
when this error occurs you can safely turn this debugging on permanently
without risking a clutter of your logs. Later, if you know how to
reproduce is you can increase debugging to get more details about what
the driver is actually doing. The debug flag for _just_ the ucode event
log is 0x40000 (like "modprobe iwlagn debug=0x40000"). The 0x43fff is a
more general debug flag that helps with obtaining more information.

When you have this data - could you please submit a bug at
intellinuxwireless.org/bugzilla for us to be able to track it?

Thank you very much

Reinette



  reply	other threads:[~2009-07-13 15:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 21:21 iwlwifi 4965 uCode available reinette chatre
2009-07-09 23:13 ` [ipw3945-devel] " Rafał Miłecki
2009-07-09 23:26   ` reinette chatre
2009-07-13 20:30     ` Rafał Miłecki
2009-07-13 20:32       ` Rafał Miłecki
2009-07-13 20:38         ` reinette chatre
2009-07-13 20:43           ` Rafał Miłecki
2009-07-13 20:48             ` reinette chatre
2009-07-13 21:12               ` Rafał Miłecki
2009-07-12 12:45 ` Helmut Schaa
2009-07-13 15:46   ` reinette chatre [this message]
2009-07-13 18:29     ` Helmut Schaa
2009-07-13 18:43     ` [ipw3945-devel] " John Ranson
2009-07-13 18:56       ` reinette chatre
2009-07-13 19:52         ` John Ranson
2009-07-13 21: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=1247499979.17896.1556.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=helmut.schaa@googlemail.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