From: Mateusz Kulikowski <mateusz.kulikowski@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
gilbertdion@gmail.com, wlanfae@realtek.com,
chaoming_li@realsil.com.cn
Cc: linux-wireless@vger.kernel.org
Subject: Re: Fwd: 8192 WiFi Realtek 8192E disconnects after a while and fails to reconnect
Date: Mon, 18 Jan 2016 20:59:39 +0100 [thread overview]
Message-ID: <569D442B.8090105@gmail.com> (raw)
In-Reply-To: <569C39D0.4060909@lwfinger.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Larry,
On 18.01.2016 02:03, Larry Finger wrote:
> On 01/17/2016 04:07 PM, Mateusz Kulikowski wrote:
[...]
>> System: Ubuntu 15.04 (from usb stick), kernel 3.19.0-15-generic,
>> x86_64 Machine: MSI AM1I, Sempron 2650, PCIe to mini-pcie "wifi"
>> bridge (with antenna connector and proper RFKILL wiring).
>>
>>
>> Are you able to do more troubleshooting?
>>
>> Perhaps try different AP/Channel/mode, (dis)connect power cable
>> from laptop etc.
>>
>> I'll try to make another reproduction attempt, as without being
>> able to reproduce it I will probably not be able to fix it.
>
> Did you see lots of messages regarding the TX rings in the dmesg
> output? If so, those are errors.
Nope, It was pretty silent (just EAPOL notifications), but I tested
that on old (distro) kernel.
More error messages on recent kernels may be my fault, as during
driver cleanups, I converted a lot of RT_TRACE messages to (mostly)
debug printks that should never get into log.
In some places though I upgraded it to a higher log level -
in places where error condition was "obvious", perhaps in one or two
such places we can downgrade message back to dbg level to avoid
syslog spamming.
For example this message will appear only on more recent kernels:
No more TX desc@7, ring->idx = 12, idx = 12, skblen = 0x18 queuelen=64
Like I said - I'll try to play with most recent kernel
later this week (probably during weekend) and hopefully will
figure something out.
Regards,
Mateusz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWnUQnAAoJELvtohmVtQzBSgkIAI6SLDNzj2u/OdLGGSkKlwWY
ejSWH2qY1ygFIUEocPxEw9cxfxiGaoOGtqC2xAOR4J9RBAcNziRPVbGP1L9rdOZ2
nXo4dLEtRB+YEhgyfSmbtCkRCrAFeCXW9Kw5GKCZv3LKVPRmTMouiMLPGsgEzI+L
tuu2SWZGQEfwqreglPT/TkBcDcAr9+cx4Zkd4sU/2yw13Upyo2Vbfpx/rqPVFd88
Av6/NeUf+oEOeq0IG6k4eBexv3ufQ1x+v7rMT1Eh3A4obLROYWuLoLFuXRQS7Mx8
bmqpPV8W2PwOyozvvvJfx90hriDSNT+W7DSjFZyTZA+esLFFWHxL1WMutbog1F4=
=1QFR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-01-18 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKQFV0H+K46CO62w=9yNRvVaOpwmDj3UKXD0QOmF1XPs54GwnQ@mail.gmail.com>
2016-01-07 20:34 ` Fwd: 8192 WiFi Realtek 8192E disconnects after a while and fails to reconnect Gilbert Dion
2016-01-07 22:05 ` Mateusz Kulikowski
2016-01-17 22:07 ` Mateusz Kulikowski
2016-01-18 1:03 ` Larry Finger
2016-01-18 19:59 ` Mateusz Kulikowski [this message]
2016-01-18 20:30 ` Larry Finger
2016-01-09 14:14 ` Larry Finger
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=569D442B.8090105@gmail.com \
--to=mateusz.kulikowski@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=gilbertdion@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wlanfae@realtek.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).