From: Jean Delvare <jdelvare@suse.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Chaoming Li <chaoming_li@realsil.com.cn>, linux-wireless@vger.kernel.org
Subject: Re: rtl8192ce:rtl92ce_get_hw_reg():<0-0> switch case not processed
Date: Sat, 24 Sep 2016 17:25:18 +0200 [thread overview]
Message-ID: <20160924172518.55787ec7@endymion> (raw)
In-Reply-To: <6feb0feb-eb53-8b6b-4c50-e6ace0cc854a@lwfinger.net>
Hi Larry,
On Fri, 23 Sep 2016 13:10:28 -0500, Larry Finger wrote:
> As the RTL8192CE does not support WOWLAN, the correct response is to ignore that
> call. Clearly, it has nothing to do with your network drops. One thing you might
> do is add the appropriate file in /etc/modprobe.d/ so that the module is loaded
> with the "ips=0" option to see if power save is messing up.
OK, we have just added the option, I'll let you know if it makes a
difference.
There are other messages logged, by the way. I did not mention them
before because they don't look like errors and "switch case not
processed" was my prime suspect, but maybe they would be useful to you:
wlp3s0: AP 94:a7:b7:xx:xx:xx changed bandwidth, new config is 2427 MHz, width 2 (2437/0 MHz)
wlp3s0: AP 94:a7:b7:xx:xx:xx changed bandwidth, new config is 2427 MHz, width 1 (2427/0 MHz)
wlp3s0: AP 94:a7:b7:xx:xx:xx changed bandwidth, new config is 2427 MHz, width 2 (2437/0 MHz)
It oscillates between both values. There doesn't seem to be a
correlation with the failures. The timing doesn't appear to be fully
random, for example these are the timestamps for this morning:
[Sat. sept. 24 09:17:16 2016]
[Sat. sept. 24 09:32:11 2016]
[Sat. sept. 24 10:27:15 2016]
[Sat. sept. 24 10:52:11 2016]
[Sat. sept. 24 12:07:16 2016]
[Sat. sept. 24 12:44:22 2016]
15 minutes, 55 minutes, 25 minutes, 75 minutes... Looks like something
is checking adjusting the configuration every 5 minutes? Last one
doesn't follow the pattern though (37 minutes.)
> I am in the process of fixing all the instances where the log entry for the
> default case does not output the switch variable. With these patches, I will
> also handle the HAL_DEF_WOWLAN case.
Great, thanks.
> I'm sorry about my original comments regarding patching the kernel. I sent that
> E-mail before I even read your name and address. As a long-time openSUSE user, I
> certainly recognize your name and your abilities.
No worry :-)
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2016-09-24 15:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 9:51 rtl8192ce:rtl92ce_get_hw_reg():<0-0> switch case not processed Jean Delvare
2016-09-22 15:09 ` Larry Finger
2016-09-22 17:05 ` Jean Delvare
2016-09-22 21:01 ` Jean Delvare
2016-09-23 12:16 ` Jean Delvare
2016-09-23 18:10 ` Larry Finger
2016-09-24 15:25 ` Jean Delvare [this message]
2016-09-23 18:12 ` Joe Perches
2016-09-23 18:27 ` [PATCH] realtek: Add switch variable to 'switch case not processed' messages Joe Perches
2016-09-23 18:59 ` Larry Finger
2016-09-23 19:02 ` Joe Perches
2016-09-24 15:55 ` Jean Delvare
2016-09-24 16:15 ` Joe Perches
2016-09-24 16:35 ` Larry Finger
2016-09-24 17:32 ` Joe Perches
2016-09-24 19:06 ` Larry Finger
2016-09-24 20:02 ` Jes Sorensen
2016-09-24 20:29 ` Joe Perches
2016-09-24 20:35 ` Jes Sorensen
2016-09-26 9:33 ` David Laight
2016-09-23 19:07 ` Larry Finger
2016-09-27 15:45 ` rtlwifi: " Kalle Valo
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=20160924172518.55787ec7@endymion \
--to=jdelvare@suse.de \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--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).