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
