linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helmut Schaa <helmut.schaa@googlemail.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: linux-wireless@vger.kernel.org, ipw3945-devel@lists.sourceforge.net
Subject: Re: iwlwifi 4965 uCode available
Date: Sun, 12 Jul 2009 14:45:40 +0200	[thread overview]
Message-ID: <200907121445.42289.helmut.schaa@gmail.com> (raw)
In-Reply-To: <1247174482.17896.1304.camel@rc-desk>

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).

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

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?

Helmut

  parent reply	other threads:[~2009-07-12 12:45 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 [this message]
2009-07-13 15:46   ` reinette chatre
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=200907121445.42289.helmut.schaa@gmail.com \
    --to=helmut.schaa@googlemail.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --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 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).