From: Alexander Barinov <alex.barinov@gmail.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: BUG REPORT: libertas causing kernel lockups
Date: Wed, 8 Jul 2009 00:37:34 +0400 [thread overview]
Message-ID: <20090708003734.0d57b389@dream> (raw)
In-Reply-To: <200907070859.39413.hs4233@mail.mn-solutions.de>
On Tue, 7 Jul 2009 08:59:39 +0200
Holger Schurig <hs4233@mail.mn-solutions.de> wrote:
> > By executing 'cat /proc/net/wireless' I get the same bug:
>
> I haven't tested your exact but, but I've the following in my
> mind, back from about 1 year ago when I did lots of libertas and
> libertas_cs work:
>
> Access wireless stats made the libertas driver (in wext.c) issue
> a command towards the firmware in the hardware. I think it was
> the command to get the current SNR/RSSI/whatever.
>
> The libertas command-response-cycle does sleep, so you could
> trigger a bug. I once had a patch (and I think I posted that
> patch). The patch lied, by providing the last SNR/RSSI/whatever,
> and issueing a "get SNR/RSSI/whatever" in the background, just
> storing the result. So just one "cat /proc/net/wireless" returns
> bogus, but a continues command returns "valid" info, e.g. when
> doing "watch iwconfig eth1".
Sorry for asking a potentially stupid question as I am no way a
wireless hardware expert, but can this bug be caused by wrong firmware
version?
BTW, it is really hard to find a patch you are talking about in the
archive. Could you please give some clues on the key words to search
(besides your name and "patch", of cause)?
next prev parent reply other threads:[~2009-07-07 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-04 9:03 BUG REPORT: libertas causing kernel lockups Alexander Barinov
2009-07-04 10:41 ` Johannes Berg
2009-07-05 8:59 ` Alexander Barinov
2009-07-06 17:29 ` Dan Williams
2009-07-06 19:23 ` Alexander Barinov
2009-07-07 6:59 ` Holger Schurig
2009-07-07 8:56 ` Johannes Berg
2009-07-08 7:42 ` Holger Schurig
2009-07-07 20:37 ` Alexander Barinov [this message]
2009-07-08 7:32 ` Holger Schurig
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=20090708003734.0d57b389@dream \
--to=alex.barinov@gmail.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=linux-wireless@vger.kernel.org \
/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).