10ec:8176 No Wi-Fi at startup; disabling and enabling wireless fixes it -- Realtek RTL8188CE rtl8192ce

[YannUbuntu]

Ubuntu12.04.1

1) Shutdown the PC
2) reboot the PC, start the Ubuntu session

Expected result: Wi-Fi networks are detected in the Network applet

Observed result: sometimes no networks appear in the Network applet. Disabling and enabling wireless fixes it.

May be linked to Bug #1051084
Maybe partially/totally due to bad WiFi signal/provider.

Below are the Apport files before disabling/enabling wireless.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic x86_64
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
CRDA:
 country EC:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 20), (3, 17)
  (5250 - 5330 @ 20), (3, 23), DFS
  (5735 - 5835 @ 20), (3, 30)
Date: Mon Sep 17 08:36:50 2012
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IpRoute:

NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 Wired connection 1 68688f58-1e37-4cf1-8716-ab2423525464 802-3-ethernet 1347863714 lun. 17 sept. 2012 08:35:14 CEST yes no /org/freedesktop/NetworkManager/Settings/1
 NUMERICABLE-BDB7 6285f33d-ba83-4866-8ace-b67ed4ca4485 802-11-wireless 1347841081 lun. 17 sept. 2012 02:18:01 CEST yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/1
 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.4.0 disconnected enabled enabled enabled enabled disabled
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: yyy 1648 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e00000 irq 43'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,15584140,00100100 HDA:80862805,15584140,00100000'
   Controls : 27
   Simple ctrls : 13
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=56eb9210-7151-425c-93dd-b92af2e792ba
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IpRoute:
 default via 192.168.0.1 dev wlan0 proto static
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.14 metric 2
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
MachineType: CLEVO CO. W240HU/W250HUQ
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
Package: network-manager 0.9.4.0-0ubuntu4.1
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic root=UUID=789016b1-f3f0-4b76-be92-afa2dbb36c5e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-31-generic N/A
 linux-backports-modules-3.2.0-31-generic N/A
 linux-firmware 1.79.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
StagingDrivers: mei
Tags: precise running-unity staging precise running-unity
Uname: Linux 3.2.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 08/09/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: Tag 12345
dmi.board.name: W240HU/W250HUQ
dmi.board.vendor: CLEVO CO.
dmi.board.version: D02A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnCLEVOCO.:pnW240HU/W250HUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240HU/W250HUQ:rvrD02A:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: W240HU/W250HUQ
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO CO.
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 Connexion filaire 1 c8eee114-f9a2-4973-823d-1e954e5cd2c0 802-3-ethernet 1350075757 ven. 12 oct. 2012 23:02:37 CEST yes no /org/freedesktop/NetworkManager/Settings/1
 NUMERICABLE-BDB7 6285f33d-ba83-4866-8ace-b67ed4ca4485 802-11-wireless 1350076356 ven. 12 oct. 2012 23:12:36 CEST yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/1
 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.4.0 connected enabled enabled enabled enabled disabled

[Mathieu Trudel-Lapierre (cyphermox)]

This sounds a lot like a kernel issue to me.

What happens after resume, does the iwconfig command still list the wifi device? Are killswitches listed in 'rfkill list'?

This is relevant because there is some chance that this is in fact caused by a memory bug that gets more easily triggered through suspend/resume.

[YannUbuntu (yannubuntu)]

************ AFTER RESUME (NO CONNECTION IN NM APPLET):

$ iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11bgn ESSID:off/any
          Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
          Retry long limit:7 RTS thr=2347 B Fragment thr:off
          Power Management:off

eth0 no wireless extensions.

$ rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

***************** AFTER RESUME, AFTER WAITING 1~2MINUTES, WIFI IS CONNECTED:
$ iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11bgn ESSID:"NUMERICABLE-BDB7"
          Mode:Managed Frequency:2.467 GHz Access Point: 00:1F:33:3F:05:34
          Bit Rate=54 Mb/s Tx-Power=20 dBm
          Retry long limit:7 RTS thr=2347 B Fragment thr:off
          Power Management:off
          Link Quality=54/70 Signal level=-56 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

$ rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

[Mathieu Trudel-Lapierre (cyphermox)]

Indeed, I think the driver itself needs to be investigated: there's at least one indication of issues with reloading the firmware:

Sep 16 23:03:42 yyy-W240HU-W250HUQ kernel: [16829.885737] rtl8192c_common:rtl92c_firmware_selfreset(): 8051 reset fail.
Sep 16 23:03:46 yyy-W240HU-W250HUQ kernel: [16834.773964] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin
Sep 16 23:03:53 yyy-W240HU-W250HUQ kernel: [16840.968894] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cfw.bin

We don't have logs for a suspend/resume cycle. Could you run through the process of suspending your computer, resuming, and attaching /var/log/syslog? It would be important to see clearly if there are other relevant messages from the kernel during the resume, either for a firmware reset or when the card goes into ready state.

Adding a task for 'linux' since it's pretty likely to be a kernel issue.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1051816

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

apport information

[YannUbuntu (yannubuntu)]

Previous attached files are the result of apport-collect 1051816, from a cold boot (not resume).

[YannUbuntu (yannubuntu)]

@mathieu-tl: thanks for your interest.
I will attach /var/log/syslog before and after suspend.

[penalvch (penalvch)]

YannUbuntu, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

[gene (eugenios)]

Hello all,
It might be related too
I am helping a friend with this laptop running Ubuntu 12.04
uname -a:
linux 3.2.0-32-generic-pae #51-Ubuntu SMP Wed Sep 26 21:54:23 UTC 2012 i686 athlon i386 GNU/Linux
lshw:
    product: Satellite C655D (PSC0YU-03G02C)
    vendor: TOSHIBA
    version: PSC0YU-03G02C
    serial: 9B197259Q
    width: 32 bits
    capabilities: smbios-2.7 dmi-2.7
    configuration: boot=normal chassis=notebook family=Type1Family sku=PSC0YU-03G02C uuid=B52B24F0-DDA9-11E0-A412-00266CDB1E20
It also uses the infamous rtl8193ce driver. My friend complained about frequent loss of connections and sudden system freezes. AMOF, Windows 7 was even worse to constantly shutdown by itself. So I suspected some hardware problem...
 When I got a hold of it I saw the freezes with 3.2.0-23 kernel and spurious output of the rlt driver flooding the logs. After the upgrade to 0-30 and 0-32 freezes (due to the networking) stopped. However, what I found was that networking is lost completely when after resume from suspend. It was weird, that both wireless and wired interfaces just never worked. I tried to restart networking, network-manager services, rmomodding and modprobbing all modules related to rtl8193ce in many different orders. Nothing seemed to work, before I realizes that networking must be stopped before any other service prior to suspend and then started after every other service on resume. So here's a weird but working pm sleep hook /etc/pm/sleep.d/00_netwokmanager:

#!/bin/bash
# prior to the suspend-to-ram the weird rtl8192ce driver wants to be unloaded early on and be loaded back late after resume. Say without both sleeps and waiting some time networking won't be recovered at all
case $1 in
        suspend)
    /etc/init.d/network-manager stop
    #it's weird, but it won't recover without this
    sleep 3
        ;;
     resume)
# capricious rtl8192ce needs more time
    sleep 10
    /etc/init.d/network-manager start
    ;;
    *) ;;
esac

Let me know what you think about this
Thanks
--

#This message was sent with Mutt and composed in the GNU Emacs

[penalvch (penalvch)]

gene, with your friends laptop, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding.

[gene (eugenios)]

Thanks, Christopher,
I will certainly file a separate bug report.
--

#This message was sent with Mutt and composed in the GNU Emacs

[HywC (hywelc)]

This bug also affects me and I'm very keen to help resolve it.

I got both 3.7.0-030700rc2-generic 3.7.0-030700rc3-generic (the latter was marked as being for raring, so wasn't sure if it was worth trying).

I was unable to see if this problem is fixed because larger problems got in the way. The kernel wasn't recognising I even had wifi. I didn't do too much digging, but `ifconfig` showed only eth0 and loopback.

Let me know if there's anything else I can do to help sort this out.

[penalvch (penalvch)]

HywC, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]