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: Wed, 8 Jun 2011 15:47:22 +0200 [thread overview]
Message-ID: <20110608134721.GA2283@redhat.com> (raw)
In-Reply-To: <1307474580.2342.7.camel@x61.thuisdomein>
On Tue, Jun 07, 2011 at 09:23:00PM +0200, Paul Bolle wrote:
> On Tue, 2011-06-07 at 16:54 +0200, Stanislaw Gruszka wrote:
> > That could be useful hint, we do not scan chan by chan, but we
> > have thing called "plcp check health", which "restart radio"
> > by requesting one channel scan. So perhaps disabling that could
> > help.
>
> At this moment I'm interested in something (a script, some sequence of
> actions, whatever) that (somewhat) reliably triggers this error. Because
> right now I have no clue what triggers it.
Having reliable reproducer will be definitely something that is
nice to have. But bug could be some kind of race condition that happen
in code flow once per 10000000000 cases ...
> Is your patch in that category or is it a (crude) fix? If it's a fix,
> I'm not sure it is of much help at this stage.
It could be possible fix. Why you can not simply patch and see if errors
are still there? If after a week or so there will be no errors, we could
consider bug fixed, otherwise well ... still will need looking around
for fix.
I just posted patch that remove these "plcp health check" and related
code on -next anyway, because I don't think this is something that we
need.
Stanislaw
next prev parent reply other threads:[~2011-06-08 13:47 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 [this message]
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
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=20110608134721.GA2283@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).