WiFi disconnects randomly and needs restart to reconnect
Reported by
ferra...@gmail.com,
Apr 2 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 7978.36.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.57 Safari/537.36 Platform: 7978.36.0 (Official Build) beta-channel kip Example URL: Steps to reproduce the problem: 1. Happens randomly on all access points 2. 3. What is the expected behavior? WiFi adapter shows "Not Connected". No available access points are visible. Once restarted, network works normally. What went wrong? Note: I tried to submit this last night but they WiFi disconnected and I am not sure if it went through so I am trying again. Quick overview: The WiFi disconnects from access points and does not reconnect. Viewing the available networks shows zero available. Disabling and re-enabling the adapter does nothing. Restarting the computer fixes the issue, at least until it happens again. I have experienced this issue on every access point that I have used the computer on. It seems random, attempts to reproduce the issue have failed. Happens most often when computer returns from sleep but also happens while using it. The access point is 15 feet away so low received signal strength isn't the problem. I have attached all logs files I collected when the problem happened yesterday. Links to other reports I have made on this issue are below as well. HP has already replaced the WiFi adapter and claim it is software issue at this point. HP still told, as of last week, that Google will have fix ready April 19th but I have my doubts since they never provided me with emails or bug tracker number. If provided attachments are not enough, please let me know what logs are needed and I will get them the next time this issue occurs. Current Setup: Version 50.0.2661.57 beta (64-bit) Platform 7978.36.0 (Official Build) beta-channel kip Firmware Google_Kip.5216.227.25 Google Chromebook forum original post detailing the problem: https://productforums.google.com/forum/#!topic/chromebook-central/JXkiG3uPzY0;context-place=topicsearchin/chromebook-central/hp$20chromebook$2014 Comment made on Chrome Bug tracker: (Comment 57) https://bugs.chromium.org/p/chromium/issues/detail?id=578694&q=wifi%20disconnect&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified Did this work before? No Chrome version: 50.0.2661.57 Channel: beta OS Version: 7978.36.0 Flash Version: Shockwave Flash 21.0 r0 While I did make a comment about this problem on Issue 578694 , I do not know if it is the same problem, if so, I apologize.
,
Apr 2 2016
#CBC-RS/TC-watchlist
,
Apr 2 2016
Chromebook lost WiFi connectivity and I was able to capture more network logging information. I've attached the chrome://system "netlog" from the time the WiFi went offline. Scrolling through it, the following section seemed most relevant: 2016-04-02T19:01:13.852128-04:00 ERR shill[838]: [ERROR:chromeos_supplicant_interface_proxy.cc(261)] Failed to reattach: fi.w1.wpa_supplicant1.NotConnected This interface is not connected 2016-04-02T19:01:13.852220-04:00 ERR shill[838]: [ERROR:wifi.cc(1765)] In OnLinkMonitorFailure(): failed to call Reattach(). 2016-04-02T19:01:13.859795-04:00 ERR shill[838]: [ERROR:wifi.cc(968)] Disconnected due to inability to connect to the service. 2016-04-02T19:01:13.859885-04:00 INFO shill[838]: [INFO:service.cc(411)] Service 5: state Online -> Failure 2016-04-02T19:01:13.859951-04:00 INFO shill[838]: [INFO:service.cc(1001)] Noting an unexpected connection drop. 2016-04-02T19:01:13.860077-04:00 INFO shill[838]: [INFO:manager.cc(1439)] Service 5 updated; state: Failure failure out-of-range 2016-04-02T19:01:13.860741-04:00 INFO shill[838]: [INFO:service.cc(411)] Service 5: state Failure -> Idle 2016-04-02T19:01:13.860911-04:00 INFO shill[838]: [INFO:manager.cc(1439)] Service 5 updated; state: Idle failure Unknown 2016-04-02T19:01:13.861906-04:00 INFO shill[838]: [INFO:dhcp_config.cc(223)] Stopping 4319 (ReleaseIP) 2016-04-02T19:01:13.862694-04:00 INFO dhcpcd[4319]: received SIGTERM, stopping 2016-04-02T19:01:13.862734-04:00 INFO dhcpcd[4319]: wlan0: removing interface 2016-04-02T19:01:13.862752-04:00 INFO dhcpcd[4319]: status changed to Release 2016-04-02T19:01:13.862770-04:00 INFO dhcpcd[4319]: dhcpcd exited 2016-04-02T19:01:13.869321-04:00 INFO shill[838]: [INFO:wifi.cc(357)] Scan [full] on wlan0 (progressive scan DISABLED) from CurrentBSSChanged 2016-04-02T19:01:13.871282-04:00 INFO shill[838]: [INFO:wifi.cc(1577)] WiFi wlan0 StateChanged completed -> disconnected 2016-04-02T19:01:13.871494-04:00 INFO shill[838]: [INFO:wifi.cc(1577)] WiFi wlan0 StateChanged disconnected -> interface_disabled 2016-04-02T19:01:13.873737-04:00 INFO shill[838]: [INFO:service.cc(316)] Auto-connecting to service 5 2016-04-02T19:01:13.873851-04:00 INFO shill[838]: [INFO:service.cc(332)] Connect to service 5: AutoConnect 2016-04-02T19:01:13.879542-04:00 DEBUG wpa_supplicant[487]: Fast associate: Old scan results 2016-04-02T19:01:13.879564-04:00 DEBUG wpa_supplicant[487]: wlan0: Rescheduling scan request: 0.000000 sec 2016-04-02T19:01:13.879576-04:00 DEBUG wpa_supplicant[487]: wlan0: Skip scan - interface disabled
,
Apr 3 2016
Lost connectivity again. I had the log levels turned up to the following: ff_debug +wifi ff_debug --level -2 wpa_debug excessive netlog attached spanning the disconnect event.
,
Apr 4 2016
,
Apr 11 2016
I was providing weekly updates to HP but since they said it is a software problem, not hardware, and they are no longer looking into the issue, I figured this was the best place for updates. Over the last week, I lost connectivity 9 times, 5 when resuming from sleep, 4 times while activity using computer. Version remained the same at: 50.0.2661.57 beta (64-bit)
,
Apr 11 2016
,
Apr 16 2016
Disconnected again, shortly after updating to latest beta channel. Version 50.0.2661.79 beta (64-bit) Platform 7978.57.0 (Official Build) beta-channel kip Firmware Google_Kip.5216.227.25 Attached it the netlog file spanning the disconnect event. I did not have log levels turned up at the time. Log levels have been turned up should it happen again.
,
Apr 16 2016
Just my luck...happened again 20 minutes later. Wifi disconnected, tried to reconnect 3-4 times before disconnecting one last time. Again, at this final time, the wifi shows "No networks available" and disabling, re-enabling the wifi adapter does nothing. Reboot is required to re-establish the connection. Attached are the system/netlog with log levels set as follows: ff_debug +wifi ff_debug --level -2 wpa_debug excessive As well at the net-internals-log.json file. I started this after wifi disconnected so I am not sure how helpful it will be. I did try disabling/re-enabling the wifi adapter while it was running, hopefully something useful would be caught.
,
Apr 16 2016
Today just must be a really bad day for me or the 50.0.2661.79 beta update changed something. Had the logs set to the following levels: ff_debug +wifi ff_debug --level -4 wpa_debug excessive I can keep posting these or other updates. Just let me know what would be most helpful. Net-internals-log is 22.8 MB so I had to zip it to 2.1 MB. I started it immediately upon the last restart so it covers the entire event.
,
Apr 18 2016
ferralli@gmail.com: when you see the issue again, could you please grab the logs by choosing "ChromeOS" from chrome://net-internals?
,
Apr 18 2016
There may be something wrong with the kernel driver or the NIC itself. I found this in the first set of kernel logs, on resume: 2016-04-01T20:22:50.969187-04:00 ERR kernel: [ 1452.639040] iwlwifi 0000:01:00.0: Failed to wake NIC for hcmd 2016-04-01T20:22:50.969253-04:00 ERR kernel: [ 1452.639152] iwlwifi 0000:01:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5 2016-04-01T20:22:59.576339-04:00 ERR kernel: [ 1460.419463] iwlwifi 0000:01:00.0: Queue 2 stuck for 10000 ms. 2016-04-01T20:22:59.576393-04:00 ERR kernel: [ 1460.419533] iwlwifi 0000:01:00.0: Current SW read_ptr 166 write_ptr 193 followed by a spew of warnings, all in the same place (iwl_pcie_isr at iwl-trans.h:1085): 2016-04-01T20:22:59.576408-04:00 WARNING kernel: [ 1460.437333] ------------[ cut here ]------------ 2016-04-01T20:22:59.576427-04:00 WARNING kernel: [ 1460.437383] WARNING: at /mnt/host/source/src/third_party/kernel/v3.10/drivers/net/wireless-3.8/iwl7000/iwlwifi/pcie/trans.c:1669 iwl_trans_pcie_unref+0xff2/0x24fc [iwlwifi]() 2016-04-01T20:22:59.576440-04:00 NOTICE kernel: [ 1460.437413] Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff) 2016-04-01T20:22:59.576489-04:00 NOTICE kernel: [ 1460.437432] Modules linked in: ctr ccm rfcomm i2c_dev uinput snd_soc_sst_byt_max98090_mach isl29018(C) industrialio snd_soc_sst_baytrail_pcm snd_hda_codec_hdmi memconsole snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep dptf_acpi zram(C) snd_soc_max98090 snd_soc_sst_dsp esif_lf_driver snd_soc_sst_acpi fuse nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables iwlmvm iwl7000_mac80211 iwlwifi cfg80211 btusb btrtl btbcm btintel bluetooth uvcvideo joydev videobuf2_vmalloc videobuf2_memops videobuf2_core videodev snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device ppp_async ppp_generic slhc tun 2016-04-01T20:22:59.576501-04:00 NOTICE kernel: [ 1460.437796] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 3.10.18 #1 2016-04-01T20:22:59.576514-04:00 NOTICE kernel: [ 1460.437817] Hardware name: Hewlett-Packard kip, BIOS Google_Kip.5216.227.25 07/06/2015 2016-04-01T20:22:59.576526-04:00 NOTICE kernel: [ 1460.437840] 0000000000000009 58133dd486590c39 ffff88017fc03cc0 ffffffff9111a553 2016-04-01T20:22:59.576537-04:00 NOTICE kernel: [ 1460.437881] ffff88017fc03cf8 ffffffff90c320ad ffff88017fc03d08 ffff880176528000 2016-04-01T20:22:59.576548-04:00 NOTICE kernel: [ 1460.437920] 000000000080b900 ffff88017652c048 ffff88017fc03db0 ffff88017fc03d68 2016-04-01T20:22:59.576555-04:00 NOTICE kernel: [ 1460.437960] Call Trace: 2016-04-01T20:22:59.576569-04:00 NOTICE kernel: [ 1460.437976] <IRQ> [<ffffffff9111a553>] dump_stack+0x19/0x1b 2016-04-01T20:22:59.576581-04:00 NOTICE kernel: [ 1460.438033] [<ffffffff90c320ad>] warn_slowpath_common+0x65/0x7d 2016-04-01T20:22:59.576593-04:00 NOTICE kernel: [ 1460.438064] [<ffffffff90c3211c>] warn_slowpath_fmt+0x57/0x73 2016-04-01T20:22:59.576605-04:00 NOTICE kernel: [ 1460.438108] [<ffffffffc0188053>] ? iwl_trans_pcie_tx+0x796/0xe2d [iwlwifi] 2016-04-01T20:22:59.576618-04:00 NOTICE kernel: [ 1460.438149] [<ffffffffc0189747>] iwl_trans_pcie_unref+0xff2/0x24fc [iwlwifi] 2016-04-01T20:22:59.576701-04:00 NOTICE kernel: [ 1460.438190] [<ffffffffc01894b0>] iwl_trans_pcie_unref+0xd5b/0x24fc [iwlwifi] 2016-04-01T20:22:59.576719-04:00 NOTICE kernel: [ 1460.438231] [<ffffffffc01853e4>] iwl_pcie_isr+0x83b/0x129b [iwlwifi] 2016-04-01T20:22:59.576732-04:00 NOTICE kernel: [ 1460.438262] [<ffffffff90c3fcef>] ? mod_timer_pinned+0x26/0x28 2016-04-01T20:22:59.576744-04:00 NOTICE kernel: [ 1460.438294] [<ffffffff90fdc59d>] ? intel_pstate_timer_func+0x1da/0x1e9 2016-04-01T20:22:59.576756-04:00 NOTICE kernel: [ 1460.438334] [<ffffffffc0185308>] ? iwl_pcie_isr+0x75f/0x129b [iwlwifi] 2016-04-01T20:22:59.576768-04:00 NOTICE kernel: [ 1460.438364] [<ffffffff90c3ec08>] call_timer_fn+0x3d/0x105 2016-04-01T20:22:59.576780-04:00 NOTICE kernel: [ 1460.438403] [<ffffffffc0185308>] ? iwl_pcie_isr+0x75f/0x129b [iwlwifi] 2016-04-01T20:22:59.576791-04:00 NOTICE kernel: [ 1460.438433] [<ffffffff90c3f1a9>] run_timer_softirq+0x1c4/0x204 2016-04-01T20:22:59.576803-04:00 NOTICE kernel: [ 1460.438465] [<ffffffff90c39235>] __do_softirq+0x108/0x23e 2016-04-01T20:22:59.576813-04:00 NOTICE kernel: [ 1460.438499] [<ffffffff911201bc>] call_softirq+0x1c/0x30 2016-04-01T20:22:59.576824-04:00 NOTICE kernel: [ 1460.438528] [<ffffffff90c03916>] do_softirq+0x33/0x6e 2016-04-01T20:22:59.576835-04:00 NOTICE kernel: [ 1460.438556] [<ffffffff90c3944c>] irq_exit+0x4c/0x99 2016-04-01T20:22:59.576846-04:00 NOTICE kernel: [ 1460.438583] [<ffffffff9112079d>] smp_apic_timer_interrupt+0x7c/0x8a 2016-04-01T20:22:59.576858-04:00 NOTICE kernel: [ 1460.438614] [<ffffffff9111fb4a>] apic_timer_interrupt+0x6a/0x70 2016-04-01T20:22:59.576870-04:00 NOTICE kernel: [ 1460.438634] <EOI> [<ffffffff90fdcaaf>] ? cpuidle_enter_state+0x44/0x99 2016-04-01T20:22:59.576881-04:00 NOTICE kernel: [ 1460.438686] [<ffffffff90fdcbe1>] cpuidle_idle_call+0xdd/0x152 2016-04-01T20:22:59.576892-04:00 NOTICE kernel: [ 1460.438719] [<ffffffff90c09b92>] arch_cpu_idle+0xe/0x1d 2016-04-01T20:22:59.576903-04:00 NOTICE kernel: [ 1460.438749] [<ffffffff90c6cd85>] cpu_startup_entry+0x13a/0x196 2016-04-01T20:22:59.576914-04:00 NOTICE kernel: [ 1460.438778] [<ffffffff9110c79e>] rest_init+0x72/0x74 2016-04-01T20:22:59.576925-04:00 NOTICE kernel: [ 1460.438806] [<ffffffff916dbce6>] start_kernel+0x3a1/0x3c2 2016-04-01T20:22:59.576937-04:00 NOTICE kernel: [ 1460.438836] [<ffffffff916db47e>] x86_64_start_reservations+0x2a/0x2c 2016-04-01T20:22:59.576948-04:00 NOTICE kernel: [ 1460.438865] [<ffffffff916db54c>] x86_64_start_kernel+0xcc/0xcf 2016-04-01T20:22:59.576958-04:00 WARNING kernel: [ 1460.438886] ---[ end trace 959d66e3d6d5d08d ]--- 2016-04-01T20:22:59.576970-04:00 ERR kernel: [ 1460.438956] iwl data: 00000000: 9d c5 fd 90 ff ff ff ff 00 22 c1 7f 01 88 ff ff ........."......
,
Apr 18 2016
Ah, thanks for digging that up, Luigi. Reminds me of crosbug.com/p/47314. There is a BIOS fix that will get rolled out in M51 I believe.
,
Apr 18 2016
Aha you found it, thank you Sameer. Thank you ferralli. It looks like this can be fixed in software, and a fix is ready but unfortunately it won't be pushed out until R51, which is still several weeks away. You can speed that up by moving to the Dev channel (already out I think) or Beta (one or two weeks). Thank you for your help. Marking as fixed, adding a note at crosbug.com/p/47314.
,
Apr 18 2016
Thank you for the time and work put into fixing it. I have been dealing with the issue for over 5 months and I am glad to see a light at the end of the tunnel. I am running R50 now and will update it to the Dev channel in the next week or so. Should I continue to have issues (crossing my fingers I won't) I will post back here. Thank you.
,
Apr 18 2016
We're very sorry you had to deal with this for 5 months!
,
May 10 2016
ferralli@, please let us know if the fix worked for you. chrome://version should be 8085.0.0 or later. Thank you!
,
May 11 2016
tienchang: The beta version I have is "8172.25.0 (Official Build) beta-channel kip". It looked like the last update did update the firmware from "Google_Kip.5216.227.25" to "Google_Kip.5216.227.58". I haven't had any issues since, so I am thinking it might my fixed! I know information on the bug is probably posted at "crosbug.com/p/47314" but I do not have access to the site. If it isn't too much trouble, can I ask what the issue was? Was it the wireless driver? The BIOS for the Chromebook 14? I was dealing with this problem for so long and I am curious to the solution. Thanks!
,
May 11 2016
ferralli: the crosbug.com/p tracker is for bugs that may contain confidential communication between Google and the hardware partners. There are a lot of comments in there and I don't know what's confidential (if anything), so I am very sorry but we may be unable to satisfy your curiosity beyond what's discussed here.
,
May 23 2016
,
May 25 2016
Closing this as verified. @ferralli please reopen this, if you see any issue. |
||||||||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||||||||
Comment 1 by lmcart...@gmail.com
, Apr 2 2016