From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Cc: Alexander Barinov <alex.barinov@gmail.com>
Subject: Re: BUG REPORT: libertas causing kernel lockups
Date: Tue, 7 Jul 2009 08:59:39 +0200 [thread overview]
Message-ID: <200907070859.39413.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <20090704130346.01b2e869@dream>
> 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".
--
http://www.holgerschurig.de
next prev parent reply other threads:[~2009-07-07 6:59 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 [this message]
2009-07-07 8:56 ` Johannes Berg
2009-07-08 7:42 ` Holger Schurig
2009-07-07 20:37 ` Alexander Barinov
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=200907070859.39413.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=alex.barinov@gmail.com \
--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).