Linux wireless drivers development
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: Robby Workman <rworkman@slackware.com>
Cc: "ilw@linux.intel.com" <ilw@linux.intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Ilw] iwlagn crash on 2.6.29.4
Date: Fri, 12 Jun 2009 09:55:49 -0700	[thread overview]
Message-ID: <1244825750.20900.468.camel@rc-desk> (raw)
In-Reply-To: <alpine.LNX.1.10.0906112246330.23960@bob.slackware.com>

Hi,

On Thu, 2009-06-11 at 22:51 -0700, Robby Workman wrote:
> On 2.6.29.4, I just got a crash in iwlagn under heavy network
> throughput.  I was transferring a dvd iso from one box in my
> lan to another, and the following occurred:
> 
>    http://slackware.com/~rworkman/OOPS
> 
> It didn't bring the entire system to a halt (thankfully);
> removing and reloading the iwlagn module made everything
> just fine. :-)
> 
> If any more information is needed, let me know.  I'm more than
> willing to test patches and such...

Which hardware are you using?

We released new ucode for 4965, 5100, 5300, and 5350 that address this
issue. The new 4965 ucode should work fine with your driver. If you are
using later hardware then you need a more recent driver to be able to
use its new ucode.

You can download the new ucode from:
http://intellinuxwireless.org/?n=Downloads

Reinette


  reply	other threads:[~2009-06-12 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  5:51 iwlagn crash on 2.6.29.4 Robby Workman
2009-06-12 16:55 ` reinette chatre [this message]
2009-06-15  3:28   ` [Ilw] " Robby Workman

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=1244825750.20900.468.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rworkman@slackware.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