linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Bernhard Schmidt <bschmidt@freebsd.org>, linux-wireless@vger.kernel.org
Subject: Re: [iwl4965] Microcode SW error detected
Date: Mon, 15 Oct 2012 17:17:14 +0200	[thread overview]
Message-ID: <20121015151712.GB12560@redhat.com> (raw)
In-Reply-To: <1350312660.1516.34.camel@x61.thuisdomein>

On Mon, Oct 15, 2012 at 04:51:00PM +0200, Paul Bolle wrote:
> On Fri, 2012-09-14 at 14:17 +0200, Paul Bolle wrote:
> > 0) It's one year later now and this Microcode SW error again showed up
> > in the logs. I recently upgraded and I haven't kept any logs, but my
> > guess would be that I have run into that error once every week. (This
> > laptop is now running a v3.5.3 based kernel as shipped for Fedora 17.)
> > 
> > 1) Would you have any suggestions how to pinpoint the cause of this
> > error? It is mainly annoying, and I managed to ignore it since my
> > previous message, but I still would like to free the logs from the noise
> > it makes.
> 
> 0) I ported the "iwlegacy_tracing" patch from
> https://bugzilla.kernel.org/show_bug.cgi?id=42766 to v3.6-rc7 and to
> iwl4965. I've been running iwl4965 with tracing enabled ever since (that
> is on: v3.6-rc7, v3.6, v3.6.1, and v3.6.2). Finally, after only three
> weeks I hit our Microcode SW error again.
> 
> 1) So now I've got a 600+k line (or 65 MB) trace dump. What should I do
> with it?

Just post me privately let say last 10MB of it...

Stanislaw

      reply	other threads:[~2012-10-15 15:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 11:45 [iwl4965] Microcode SW error detected Paul Bolle
2011-05-24  7:09 ` Stanislaw Gruszka
2011-05-24 15:54   ` Paul Bolle
2011-05-24 16:03     ` Stanislaw Gruszka
2011-05-24 16:50   ` Paul Bolle
2011-05-25 13:11     ` Stanislaw Gruszka
2011-05-25 13:31       ` Paul Bolle
2011-05-31 13:37         ` Stanislaw Gruszka
2011-06-06  8:58           ` Paul Bolle
2011-06-06 11:36             ` Stanislaw Gruszka
2011-06-06 18:29               ` Paul Bolle
2011-05-26 17:26       ` Dan Williams
2011-06-07  6:32 ` Bernhard Schmidt
2011-06-07 14:54   ` Stanislaw Gruszka
2011-06-07 19:23     ` Paul Bolle
2011-06-08 13:47       ` Stanislaw Gruszka
2011-08-15 10:51         ` Paul Bolle
2011-09-04  8:28     ` Paul Bolle
2011-09-05  9:33       ` Stanislaw Gruszka
2011-09-05 10:32         ` Paul Bolle
2012-09-14 12:17         ` Paul Bolle
2012-10-15 14:51           ` Paul Bolle
2012-10-15 15:17             ` Stanislaw Gruszka [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=20121015151712.GB12560@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=bschmidt@freebsd.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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).