linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>,
	Intel Linux Wireless <ilw@linux.intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Microcode SW error detected on current wireless-testing
Date: Tue, 30 Nov 2010 15:09:38 +0100	[thread overview]
Message-ID: <1291126178.3624.19.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20101130134903.GB3074@redhat.com>

On Tue, 2010-11-30 at 14:49 +0100, Stanislaw Gruszka wrote:

> > > iwlagn 0000:40:00.0: Microcode SW error detected.  Restarting 0x82000000.
> > > iwlagn 0000:40:00.0: Loaded firmware version: 228.61.2.24
> > 
> > > Is Intel aware of that problem? Should I bisect it?
> > 
> > I haven't seen it, but 4965 ... we can't really test that on an ongoing
> > basis any more... I'd guess dbbf1755b09eef8ff6dd21c8dafe1606f051ce12 is
> > the problem, seems the only recent thing that actually changed 4965.
> 
> Yes, it is dbbf1755, after revert that commit microcode error disappears.

Can you revert only the iwl-4965.c bit of it and try that?

johannes


  reply	other threads:[~2010-11-30 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 13:01 Microcode SW error detected on current wireless-testing Stanislaw Gruszka
2010-11-30 13:16 ` Johannes Berg
2010-11-30 13:49   ` Stanislaw Gruszka
2010-11-30 14:09     ` Johannes Berg [this message]
2010-11-30 14:33       ` [PATCH w-t] iwlagn: fix microcode error on 4965 Stanislaw Gruszka
2010-11-30 14:36         ` Johannes Berg
2010-11-30 15:38         ` Guy, Wey-Yi

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=1291126178.3624.19.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ilw@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.com \
    --cc=wey-yi.w.guy@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).