From: "John W. Linville" <linville@tuxdriver.com>
To: Pauli Nieminen <suokkos@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: RTL8180L is hitting WARN_ON in net/wireless/scan.c:575
Date: Mon, 19 Jul 2010 16:48:07 -0400 [thread overview]
Message-ID: <20100719204806.GB6115@tuxdriver.com> (raw)
In-Reply-To: <AANLkTiknLRzt2bdhcin5WRzwPXSWqEs8dIUe5imlN0I9@mail.gmail.com>
On Sat, Jul 17, 2010 at 10:30:49AM +0300, Pauli Nieminen wrote:
> Hi,
>
> I'm testing 2.6.35-rc4+, I have problem that warning is spamming dmesg
> when I have my wifi on. Actual problem caused y that problem is that I
> can't scan/connect to any network with 2.6.35.
>
> When I looked the code in warning it might be related to problem that
> my wifi reports all signal strength to be 175 or 178 (if I remember
> correctly). I'm now using 2.6.35 so I can't check the reported values
> from scan results.
I just sent "rtl8180: improve signal reporting for rtl8185 hardware"
as a reply to this email. Can you try that patch?
Thanks!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-07-19 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-17 7:30 RTL8180L is hitting WARN_ON in net/wireless/scan.c:575 Pauli Nieminen
2010-07-19 20:47 ` [PATCH] rtl8180: improve signal reporting for rtl8185 hardware John W. Linville
2010-07-20 20:56 ` [PATCH v2] " John W. Linville
2010-07-21 5:08 ` [PATCH] " Pauli Nieminen
2010-07-21 13:33 ` John W. Linville
2010-07-21 17:07 ` Pauli Nieminen
2010-07-21 17:19 ` John W. Linville
2010-07-21 17:44 ` Pauli Nieminen
2010-07-21 20:30 ` [RFT] rtl8180: improve signal reporting for actual rtl8180 hardware John W. Linville
2010-07-22 6:07 ` Pauli Nieminen
2010-07-21 17:22 ` [PATCH] rtl8180: improve signal reporting for rtl8185 hardware Pauli Nieminen
2010-07-19 20:48 ` John W. Linville [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=20100719204806.GB6115@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=suokkos@gmail.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).