IssueTracker

I'm seeing similar problems, even since updating to Version 73.0.3683.88 (Official Build) (64-bit) on my chromebook (Platform   11647.104.0 (Official Build) stable-channel lars). I'm not entirely sure, but it seems like it may happen more often when I'm using an Android app (e.g., Miniclip 8 ball pool). Usually the wifi connection comes back within 15 or 30 seconds, but sometimes it seems like I need to resort to closing & reopening the lid. Definitely was never a problem until the update to Version 73.

See also issues 950238 and 943157. Numerous users seeing the same thing only after the Version 73 update.

devanlee18@, do you mind grabbing a feedback report for this issue with alt-shift-i the next time it happens? Also, what Chromebook are you using?

Reply#3: Please do not speculate on this being the same issue as crbug.com/948179, crbug.com/943157 or any other without logs to show that the symptoms are entirely the same.

Please file feedback with alt-shift-i when the issue occurs or follow:

1.Navigate to chrome://net-internals#chromeos in your browser.
2. Hit ‘Store debug logs’.
3. This will store a debug-logs_<timestamp>.tgz file in your Downloads folder.
Attach the tarball here.
The issue must have occurred in T-0 minutes to ~(T-3) days for the logs captured this way to still be useful.

I hope this helps! I'm certainly not all that technically-inclined, so I appreciate being walked through what needed to be done!

Hey there,

I was curious if there was any sort of status update, by chance?

Thanks!

just noticing this tonite first time. 2015 Toshiba CB2; Version 74.0.3729.159 (Official Build) (64-bit)

we are having same issue with over 60 chromebooks a few that not updated are fine

I am also facing this issue since last 5-10 day .. literally thinking to throw my chromebook .. thts supper frustrating ..
pls pls solve this  ASAP

I am also having this issue on Toshiba Chromebook 2. I can recreate just by performing a speed test and can provide logs if needed.

Any possible update on this? I've even gone so far as to do a complete powerwash in hopes of resetting whatever the issue was. Alas, I am still having the persistent disconnection issue.

Much appreciated!

This started occurring for me about three weeks ago after my Acer Chromebook was working great for 6 months. Drops wifi and acts like it's trying to reconnect but sometimes takes awhile -- I can't get it reconnected until it randomly reconnects.

it is September and still we have problem. Multiple disconnections on dell candy 3120 every 5 minutes or less. every other pc or mobile has no problem at all.
come on guys this is a chromebook how it is supposed to work online when we are constantly offline?

I am having this issue as well. Started with just a couple. Now I have about 10-15 doing the same thing. Some disconnect from wifi and then others randomly log out altogether.

We have had the same issue recently (with Acer machines) several machines disconnecting and some logging out. It seems to occur when there is a higher usage and the access point may be trying to balance the usage.
We have just upraded to chrome OS 77 and waiting to see whether there is a change.
We have also changed our AP to a specific channel and width.

Did OS77 make a difference at all? I'm going to try that tonight.

Dear all, after dissabling the Bluetooth and making my wifi as
preferred from the wifi settings, I hadn't any disconnections.

This is the only fix that works for me

Problem still occurs in Version 77.0.3865.105 (Official Build) (64-bit). Bluetooth is disabled.

If there are wifi settings, on the Chromebook or router, which might be making a difference as per comment #25, I'd be interested in the specifics.

Is this the same problem as issue 172222923, where the developers believe it's an Intel bug?

It is now 8 months later, and the problem still occurs -- even more frequently now. My Bluetooth is disabled, I've followed all suggestions as far as possible fixes go, to no avail.

I am running on Version 78.0.3904.106 (Official Build) (64-bit) and it has only gotten worse.

I can confirm that v78 does not fixed this bug. BTW i have disconnections with the bluetooth off also (older fix)!
My chromebook barely usable, maybe its time to move to windows 10?

I am the technologist in a Catholic School and we are experiencing this issue, or something like it on a daily basis.  Two Chromebooks sitting right next to each other.  one can access a website the other cannot.  Later that day it may be fine.  The unit shows that the WiFi signal is between moderate and Excellent.  I have sent the units back to the manufacture for repair and the seem to do better but not always.  I believe that our wireless network is stable as there are many units that have no issue.  It is the randomness that is very confusing.

Reply c#29: dthomasberger@, can you provide the log (instructions in c#5)? What kind of access point do you use? Does the environment have multiple APs with the same SSID?

Reply c#27: devanlee18@, sorry for taking so long. So the symptom started from R73-11647.104.0 and it kept the ill behavior until now? And it did not improve after you disable Bluetooth, right? What kind of access point do you use? Does the environment have multiple APs with the same SSID?

Extracted from #27 net.log, this is the scan-connect-disconnect pattern (from 20:34::24.639908 to 20:36:03.505155):

Probably a key part: disconnect reason=4: WLAN_REASON_DISASSOC_DUE_TO_INACTIVITY
2019-04-15T20:34:26.063290-04:00 INFO shill[1158]: [INFO:service.cc(379)] Service 0: state Connected -> Online
2019-04-15T20:34:26.063312-04:00 INFO shill[1158]: [INFO:manager.cc(1488)] Service 0 updated; state: Online failure Unknown
2019-04-15T20:36:03.399463-04:00 NOTICE wpa_supplicant[558]: wlan0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:7f:61:39 reason=4 locally_generated=1


2019-04-15T20:34:24.639908-04:00 INFO shill[1158]: [INFO:wifi.cc(385)] ScanDone
2019-04-15T20:34:24.640081-04:00 INFO shill[1158]: [INFO:wifi_service.cc(786)] Rep ep updated for 0. [SSID=Frontier6043], bssid: 80:37:73:7f:61:39, sig: -46, sec: wpa, freq: 2412
2019-04-15T20:34:24.641932-04:00 INFO shill[1158]: [INFO:service.cc(277)] Service 59 destroyed.
2019-04-15T20:34:24.643261-04:00 INFO shill[1158]: [INFO:service.cc(277)] Service 4 destroyed.
2019-04-15T20:34:24.645847-04:00 INFO shill[1158]: [INFO:service.cc(277)] Service 12 destroyed.
2019-04-15T20:34:24.646428-04:00 INFO shill[1158]: [INFO:service.cc(277)] Service 63 destroyed.
2019-04-15T20:34:24.646979-04:00 INFO shill[1158]: [INFO:service.cc(277)] Service 57 destroyed.
2019-04-15T20:34:24.647512-04:00 INFO shill[1158]: [INFO:service.cc(277)] Service 64 destroyed.
2019-04-15T20:34:24.647994-04:00 INFO shill[1158]: [INFO:service.cc(277)] Service 66 destroyed.
2019-04-15T20:34:24.649285-04:00 INFO shill[1158]: [INFO:service.cc(284)] Auto-connecting to service 0
2019-04-15T20:34:24.649415-04:00 INFO shill[1158]: [INFO:service.cc(300)] Connect to service 0: AutoConnect
2019-04-15T20:34:24.649460-04:00 INFO shill[1158]: [INFO:wifi.cc(663)] Background scan disabled -- single Endpoint for Service.
2019-04-15T20:34:24.657885-04:00 NOTICE wpa_supplicant[558]: wlan0: SME: Trying to authenticate with 80:37:73:7f:61:39 (SSID='Frontier6043' freq=2412 MHz)
2019-04-15T20:34:24.658452-04:00 INFO shill[1158]: [INFO:service.cc(379)] Service 0: state Idle -> Associating
2019-04-15T20:34:24.658510-04:00 INFO shill[1158]: [INFO:manager.cc(1488)] Service 0 updated; state: Associating failure Unknown
2019-04-15T20:34:24.665287-04:00 INFO shill[1158]: [INFO:service.cc(293)] Suppressed autoconnect to service 0 (connecting)
2019-04-15T20:34:24.665547-04:00 NOTICE wpa_supplicant[558]: wlan0: Trying to associate with 80:37:73:7f:61:39 (SSID='Frontier6043' freq=2412 MHz)
2019-04-15T20:34:24.667312-04:00 INFO shill[1158]: [INFO:wifi.cc(1681)] WiFi wlan0 StateChanged inactive -> authenticating
2019-04-15T20:34:24.667389-04:00 INFO shill[1158]: [INFO:wifi.cc(1681)] WiFi wlan0 StateChanged authenticating -> associating
2019-04-15T20:34:24.671408-04:00 NOTICE wpa_supplicant[558]: wlan0: Associated with 80:37:73:7f:61:39
2019-04-15T20:34:24.671454-04:00 NOTICE wpa_supplicant[558]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
2019-04-15T20:34:24.675264-04:00 NOTICE wpa_supplicant[558]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
2019-04-15T20:34:24.678339-04:00 INFO shill[1158]: [INFO:wifi.cc(1681)] WiFi wlan0 StateChanged associating -> associated
2019-04-15T20:34:24.719534-04:00 INFO shill[1158]: [INFO:wifi.cc(1681)] WiFi wlan0 StateChanged associated -> 4way_handshake
2019-04-15T20:34:24.731098-04:00 INFO shill[1158]: [INFO:wifi.cc(1681)] WiFi wlan0 StateChanged 4way_handshake -> group_handshake
2019-04-15T20:34:24.741176-04:00 NOTICE wpa_supplicant[558]: wlan0: WPA: Key negotiation completed with 80:37:73:7f:61:39 [PTK=CCMP GTK=CCMP]
2019-04-15T20:34:24.741255-04:00 NOTICE wpa_supplicant[558]: wlan0: CTRL-EVENT-CONNECTED - Connection to 80:37:73:7f:61:39 completed [id=0 id_str=]
2019-04-15T20:34:24.747107-04:00 INFO shill[1158]: [INFO:wifi.cc(1681)] WiFi wlan0 StateChanged group_handshake -> completed
2019-04-15T20:34:24.768360-04:00 INFO shill[1158]: [INFO:dhcp_config.cc(187)] Spawned /sbin/dhcpcd with pid: 5949
2019-04-15T20:34:24.768417-04:00 INFO shill[1158]: [INFO:wifi.cc(1736)] wlan0 is up; started L3 configuration.
2019-04-15T20:34:24.768429-04:00 INFO shill[1158]: [INFO:service.cc(379)] Service 0: state Associating -> Configuring
2019-04-15T20:34:24.768458-04:00 INFO shill[1158]: [INFO:manager.cc(1488)] Service 0 updated; state: Configuring failure Unknown
2019-04-15T20:34:24.769274-04:00 INFO shill[1158]: [INFO:service.cc(293)] Suppressed autoconnect to service 0 (connecting)
2019-04-15T20:34:24.774619-04:00 NOTICE dhcpcd[5949]: dhcpcd is running with reduced privileges
2019-04-15T20:34:24.775600-04:00 INFO dhcpcd[5949]: status changed to Init
2019-04-15T20:34:24.775812-04:00 INFO shill[1158]: [INFO:dhcp_config.cc(134)] Init DHCP Proxy: wlan0 at :1.69
2019-04-15T20:34:25.581724-04:00 INFO dhcpcd[5949]: status changed to Reboot
2019-04-15T20:34:25.582063-04:00 INFO dhcpcd[5949]: wlan0: rebinding lease of 192.168.254.41
2019-04-15T20:34:25.582322-04:00 INFO dhcpcd[5949]: wlan0: sending REQUEST (xid 0x6642a73), next in 3.4 seconds
2019-04-15T20:34:25.655609-04:00 INFO dhcpcd[5949]: wlan0: received ACK with xid 0x6642a73
2019-04-15T20:34:25.655642-04:00 INFO dhcpcd[5949]: wlan0: acknowledged 192.168.254.41 from 192.168.254.254
2019-04-15T20:34:25.664298-04:00 INFO dhcpcd[5949]: wlan0: ARP probing 192.168.254.254 (1 of 3), next in 1.4 seconds
2019-04-15T20:34:25.664545-04:00 INFO dhcpcd[5949]: status changed to ArpGateway
2019-04-15T20:34:25.671183-04:00 INFO dhcpcd[5949]: wlan0: leased 192.168.254.41 for 86400 seconds
2019-04-15T20:34:25.671595-04:00 INFO dhcpcd[5949]: event REBOOT on interface wlan0
2019-04-15T20:34:25.671972-04:00 INFO dhcpcd[5949]: status changed to Bound
2019-04-15T20:34:25.672593-04:00 INFO shill[1158]: [INFO:dhcpv4_config.cc(111)] Event reason: REBOOT
2019-04-15T20:34:25.672869-04:00 INFO shill[1158]: [INFO:connection.cc(271)] UpdateFromIPConfig: Installing with parameters: local=192.168.254.41 broadcast=192.168.254.255 peer=<unknown> gateway=192.168.254.254
2019-04-15T20:34:25.674358-04:00 INFO shill[1158]: [INFO:service.cc(379)] Service 0: state Configuring -> Connected
2019-04-15T20:34:25.686802-04:00 INFO shill[1158]: [INFO:manager.cc(1488)] Service 0 updated; state: Connected failure Unknown
2019-04-15T20:34:25.697365-04:00 INFO shill[1158]: [INFO:wifi.cc(2549)] Enabling high bitrates.
2019-04-15T20:34:25.712523-04:00 INFO shill[1158]: [INFO:manager.cc(1637)] Default physical service: 0 (connected)
2019-04-15T20:34:25.883869-04:00 INFO shill[1158]: [INFO:http_transport_curl.cc(482)] Response: 204 (No Content)
2019-04-15T20:34:26.062608-04:00 INFO shill[1158]: [INFO:http_transport_curl.cc(482)] Response: 204 (No Content)
2019-04-15T20:34:26.062884-04:00 INFO shill[1158]: [INFO:portal_detector.cc(275)] HTTPS probe succeeded, probably no portal.
2019-04-15T20:34:26.063044-04:00 INFO shill[1158]: [INFO:portal_detector.cc(321)] Portal detection completed attempt 1 with phase==Content, status==Success, failures in content==0
2019-04-15T20:34:26.063290-04:00 INFO shill[1158]: [INFO:service.cc(379)] Service 0: state Connected -> Online
2019-04-15T20:34:26.063312-04:00 INFO shill[1158]: [INFO:manager.cc(1488)] Service 0 updated; state: Online failure Unknown
2019-04-15T20:36:03.399463-04:00 NOTICE wpa_supplicant[558]: wlan0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:7f:61:39 reason=4 locally_generated=1
2019-04-15T20:36:03.400287-04:00 INFO shill[1158]: [INFO:wifi.cc(873)] WiFi wlan0 supplicant updated DisconnectReason to -4
2019-04-15T20:36:03.403526-04:00 ERR wpa_supplicant[558]: nl80211: Failed to open /proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast: No such file or directory
2019-04-15T20:36:03.403544-04:00 ERR wpa_supplicant[558]: nl80211: Failed to set IPv4 unicast in multicast filter
2019-04-15T20:36:03.405892-04:00 WARNING shill[1158]: [WARNING:wifi_service.cc(796)] Service 0 will disconnect due to no remaining endpoints.
2019-04-15T20:36:03.407878-04:00 ERR shill[1158]: [ERROR:object_proxy.cc(581)] Failed to call method: fi.w1.wpa_supplicant1.Interface.Disconnect: object_path= /fi/w1/wpa_supplicant1/Interfaces/1: fi.w1.wpa_supplicant1.NotConnected: This interface is not connected
2019-04-15T20:36:03.407909-04:00 ERR shill[1158]: [ERROR:dbus_method_invoker.h(113)] CallMethodAndBlockWithTimeout(...): Domain=dbus, Code=fi.w1.wpa_supplicant1.NotConnected, Message=This interface is not connected
2019-04-15T20:36:03.407934-04:00 ERR shill[1158]: [ERROR:chromeos_supplicant_interface_proxy.cc(184)] Failed to disconnect: fi.w1.wpa_supplicant1.NotConnected This interface is not connected
2019-04-15T20:36:03.408247-04:00 INFO shill[1158]: [INFO:dhcp_config.cc(194)] Stopping 5949 (ReleaseIP)
2019-04-15T20:36:03.408543-04:00 INFO dhcpcd[5949]: received SIGTERM, stopping
2019-04-15T20:36:03.408561-04:00 INFO dhcpcd[5949]: wlan0: removing interface
2019-04-15T20:36:03.408584-04:00 INFO dhcpcd[5949]: status changed to Release
2019-04-15T20:36:03.408856-04:00 INFO dhcpcd[5949]: dhcpcd exited
2019-04-15T20:36:03.410521-04:00 NOTICE wpa_supplicant[558]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
2019-04-15T20:36:03.414774-04:00 INFO shill[1158]: [INFO:service.cc(379)] Service 0: state Online -> Idle
2019-04-15T20:36:03.414809-04:00 INFO shill[1158]: [INFO:manager.cc(1488)] Service 0 updated; state: Idle failure Unknown
2019-04-15T20:36:03.415402-04:00 INFO shill[1158]: [INFO:manager.cc(1488)] Service 0 updated; state: Idle failure Unknown
2019-04-15T20:36:03.416514-04:00 INFO shill[1158]: [INFO:manager.cc(1633)] Default physical service: 0 (not connected)
2019-04-15T20:36:03.423906-04:00 NOTICE wpa_supplicant[558]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
2019-04-15T20:36:03.426696-04:00 INFO shill[1158]: [INFO:service.cc(293)] Suppressed autoconnect to service 0 (no endpoints)
2019-04-15T20:36:03.427500-04:00 INFO shill[1158]: [INFO:wifi.cc(1681)] WiFi wlan0 StateChanged completed -> disconnected
2019-04-15T20:36:03.505155-04:00 INFO shill[1158]: [INFO:wifi.cc(1681)] WiFi wlan0 StateChanged disconnected -> inactive

Re comment #27: devanlee18@ did you try different AP? If so, did the Chromebook behave the same in different AP?
Did you use other devices connecting to the same AP? Did they have disconnect issue?

Hello!

Thank you for looking into this problem. I have tried different access points. The problem persists, even when taking the Chromebook to work, school, etc. and using their public WiFi systems. Additionally, I have multiple devices connected to my home network, none of which exhibit similar connectivity issues.

devanlee18@ thanks for your feedback. We can rule out the AP/environment issue. Is it your only Chromebook? Did you try using it with another account or guest mode? I want to rule out issues coming from personal setting (account related).

In the mean time, can you capture a log (instruction in comment #5) again with latest ChromeOS version when you see the symptom. Thanks a lot.

Correct comment #32, the log I'm looking at is from comment #6 uploaded by devanlee18@. The device is auron_yuna R73-11647.104.0

wifi_status from comment #6 device: https://paste.googleplex.com/5466336559890432

kirtika@ said that it is abnormal that there's no beacon rx field.

iw dev wlan0 station dump:
Station 80:37:73:##:##:## (on wlan0)
        inactive time:  28 ms
        rx bytes:       45816
        rx packets:     141
        tx packets:     147
        tx retries:     47
        tx failed:      0
        beacon loss:    57
        signal:         -50 dBm
        signal avg:     -49 dBm
        tx bitrate:     144.4 MBit/s MCS 15 short GI
        rx bitrate:     144.4 MBit/s MCS 15 short GI
        authorized:     yes
        authenticated:  yes
        associated:     yes
        preamble:       long
        WMM/WME:        yes
        MFP:            no
        TDLS peer:      no
        DTIM period:    3
        beacon interval:100
        short preamble: yes
        short slot time:yes
        connected time: 2 seconds

A reason to get DISASSOC_DUE_TO_INACTIVITY locally: missing too many beacons.
Quoted from https://b.corp.google.com/issues/113622624#comment7
iwl7000 detects 8 consecutive beacon losses (800ms, assuming the beacon interval is 100ms) after the last successful RX, it informs mac80211, which then sends a 5 consecutive probe requests to the AP at 500ms intervals (2500ms).  So theoretically mac80211 will consider the connection lost and issue a disconnection with reason 4 after 3.3 seconds.

Track on bug 943157 as the symptoms are the same and on the other side it has more information.

devanlee18@,  gmporr@ and  kyriakos.bitopoulos@, if you observe the same behavior on the latest ChromeOS update, please give us the latest feedback report. Thanks. If you didn't see the issue after OS update, please also tell us.

deanliao@ - I do still see the issue with Version 79.0.3945.123 (Official Build) (64-bit). Perhaps not as frequently as I used to; not sure if that's relevant or not, as my activity online started to include a lot of Youtube Tv as of a few months ago, so maybe the different workload has an effect on how often the problem occurs. I'll do an alt-shift-i the next time I see it.

Saw the problem at 10:57 EST. Just sent feedback, including this issue number.

Report received
https://listnr.corp.google.com/product/208/report/86856358028 (yuna, 12607.81.0 / kernel 3.14 / AC7260)
https://listnr.corp.google.com/product/208/report/86856134677 (lars, 17607.82.0 / kernel 3.18 / AC7265)

Not quite sure if it is a duplicate of crbug.com/943157. Decoupling them now.

For the first report in comment 43, I did some study in https://docs.google.com/document/d/1aVWIwWXqKkzK_1jQH2B_pfNvebWMoBPoI1HAT-qZAa4/edit?usp=sharing
The user report's net.log contains 35 reason=4 event, the duration range from 13 to 249 seconds (average 53.8 seconds).
Didn't see clear clue about why it receive reason=4. Note that in this report it has only one beacon missing event:
2020-02-12T12:41:38.748231-05:00 ERR kernel: [  225.848993] iwlwifi 0000:01:00.0: No beacon heard and the time event is over already...

And the target AP (service 2 associated), the sig showed in Rep ep update message range from -37 to -54. Seems quite strong.
2020-02-12T12:15:00.169759-05:00 INFO shill[1245]: [INFO:wifi_service.cc(722)] Rep ep updated for 2. [SSID=<SSID: 1>], bssid: [MAC OUI=80:37:73 IFACE=3], sig: -40, sec: wpa, freq: 2412

For the second report in comment 43, grep "reason=4" -B 10 system_logs.txt shows no consistent messages before reason=4 take place. Sometimes it happens during association:
 2020-02-09T15:52:26.002185-05:00 INFO shill[1414]: [INFO:wifi.cc(1806)] WiFi wlan0 StateChanged inactive -> authenticating
2020-02-09T15:52:26.003694-05:00 INFO shill[1414]: [INFO:wifi.cc(1806)] WiFi wlan0 StateChanged authenticating -> associating
2020-02-09T15:52:26.006491-05:00 INFO shill[1414]: [INFO:wifi.cc(1806)] WiFi wlan0 StateChanged associating -> 4way_handshake
2020-02-09T15:52:26.007960-05:00 INFO shill[1414]: [INFO:wifi.cc(1806)] WiFi wlan0 StateChanged 4way_handshake -> completed
2020-02-09T15:52:26.036422-05:00 NOTICE wpa_supplicant[836]: wlan0: CTRL-EVENT-DISCONNECTED bssid=[MAC OUI=00:23:69 IFACE=11] reason=4 (DISASSOC_DUE_TO_INACTIVITY) locally_generated=1

Sometimes it happens long after the connection is established:
2020-02-09T15:01:21.329378-05:00 INFO shill[1414]: [INFO:wifi.cc(1806)] WiFi wlan0 StateChanged completed -> completed
2020-02-09T15:12:20.221081-05:00 WARNING shill[1414]: [WARNING:traffic_monitor.cc(218)] DNS queries failing, out-of-credits?
2020-02-09T15:38:04.883495-05:00 INFO shill[1414]: [INFO:wifi_service.cc(722)] Rep ep updated for 0. [SSID=<SSID: 1>], bssid: [MAC OUI=00:23:69 IFACE=11], sig: -53, sec: rsn, freq: 2462
2020-02-09T15:40:04.918554-05:00 INFO shill[1414]: [INFO:wifi_service.cc(722)] Rep ep updated for 0. [SSID=<SSID: 1>], bssid: [MAC OUI=00:23:69 IFACE=11], sig: -65, sec: rsn, freq: 2462
2020-02-09T15:52:16.416484-05:00 NOTICE wpa_supplicant[836]: wlan0: CTRL-EVENT-DISCONNECTED bssid=[MAC OUI=00:23:69 IFACE=11] reason=4 (DISASSOC_DUE_TO_INACTIVITY) locally_generated=1


For the second log (board lars),  only three beacon loss is observed (two recorded):
2020-02-12T04:48:02.315067-05:00 ERR kernel: [ 4923.309620] iwlwifi 0000:01:00.0: No beacon heard and the time event is over already...
2020-02-12T10:57:49.993171-05:00 ERR kernel: [   82.967696] iwlwifi 0000:01:00.0: No beacon heard and the time event is over already...
        beacon loss:    3

So it is not due to beacon loss. Summary updated.

The attached file is extracted from https://listnr.corp.google.com/product/208/report/86856134677 using
 grep "reason=4" -B 10 system_logs.txt

Have my reports helped point you in the right direction at all?

Re davanlee18@, thanks for your report. However, I didn't dig any suspect culprit from your log. The signal strength looks good. There's no AP beacon loss. It has 35 disconnect events. Time between disconnect ranges from 13 to 249 seconds with average 53.8 seconds. (I admit that's really annoying).

From the log you gave us, however, I cannot defer what really trigger the disconnect. I also get the same Chromebook from my side. I cannot observe the behavior.

Could you do me a favor to obtain a debug log?
When the symptom occurs, can you do the following:

1.Navigate to chrome://net-internals#chromeos in your browser.
2. Click Wi-Fi button in Network Debugging section to enable verbose log
3. What for 5 minutes and expect it has some repeatedly disconnect.
4. Hit ‘Store debug logs’.
5. This will store a debug-logs_<timestamp>.tgz file in your Downloads folder.  Please upload to us.

Re deanliao: Every debug log that I create ends up exceeding the maximum upload size -- they range from 44mb to 51mb, even when compressed they still exceed the upload size. Do you have any advice?

Let's try sending a feedback report (after you enable WiFi debug log) first:

1.Navigate to chrome://net-internals#chromeos in your browser.
2. Click Wi-Fi button in Network Debugging section to enable verbose log
3. What for 5 minutes and expect it has some repeatedly disconnect.
4.  Alt + Shift + i to send feedback report. Please attach the bug id 948179.

Thank you.

Dear all,

I have not disconnections any more with Chrome OS 79.
Everything is smooth as it should be.

Re devanlee18@ , did you try the report method mentioned in comment 51? We may need debug log to see detailed information. From current log, I didn't find a suspect reason that cause the frequent disconnects.

I have made multiple attempts, but I am never able to create a log that is small enough in size to fit within the size parameters. I'm at a loss for what to do now.

Is Alt+Shift+i failed when enabling verbose log?

Unfortunately, my Chromebook has been rendered completely unusable with the newest ChromeOS update. It just constantly connects and disconnects every 5-10 seconds now, meanwhile all over devices connected to the same source all remain stable.

Is there any way I can still proceed?

Seeing disconnect/reconnects on my newish i5 Slate. I thought I was "holding it wrong" but it happens sitting on a table with the keyboard attached, too. Sometimes the disconnect is long enough for the system to offer connecting to my pixel 4 for internet. This is especially problematic now that I'm remoting into work. Just had a disco/recon while typing this out. Sent feedback with debugging log per comment #51.

I just submitted an error report with an attached debug log. Hopefully something comes of it.

I saw a repeat pattern [1] in /var/log/message in comment 60 tgz file.
wlan0 successfully authenticated and associated to an AP:
2020-04-06T21:32:59.456313+00:00 INFO kernel: [  217.475523] wlan0: associated

Then within 30 seconds, it got
2020-04-06T21:33:25.835042+00:00 INFO kernel: [  243.854616] wlan0: Connection to AP $AP_MAC_ADDR lost
2020-04-06T21:33:25.884541+00:00 ERR shill[1088]: [ERROR:object_proxy.cc(594)] Failed to call method: fi.w1.wpa_supplicant1.Interface.Disconnect: object_path= /fi/w1/wpa_supplicant1/Interfaces/1: fi.w1.wpa_supplicant1.NotConnected: This interface is not connected

Its CrOS version is  auron_yuna/R80-12739.111.0
As user devanlee18@ said, others devices are unaffected so it is unlikely to be AP issue.

The kernel message "Connection to AP $AP_MAC_ADDR lost" seems to be generated from
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/chromeos-4.14/net/mac80211/mlme.c#2517
static void ieee80211_beacon_connection_loss_work(struct work_struct *work)
{
        ...
        if (ifmgd->associated)
                ifmgd->beacon_loss_count++;

        if (ifmgd->connection_loss) {
                sdata_info(sdata, "Connection to AP %pM lost\n",
                           ifmgd->bssid);
                __ieee80211_disconnect(sdata);
        }
}

I suspect it is caused by beacon loss. Then I found feedback/dmesg caught a disconnect after a consecutive beacon loss [2]
Brian, any hint to decrypt the iwlwifi debug message in dmesg?

[1] repeated pattern
2020-04-06T21:32:51.074819+00:00 NOTICE cros-machine-id-regen[6773]: Regenerated /var/lib/dbus/machine-id (reason: network).
2020-04-06T21:32:51.957537+00:00 INFO avahi-daemon[1440]: Server startup complete. Host name is 26ce9d764d9b868b71307ab65e8ba002.local. Local service cookie is 4033222928.
2020-04-06T21:32:59.435098+00:00 INFO kernel: [  217.454513] wlan0: authenticate with $AP_MAC_ADDR
2020-04-06T21:32:59.443028+00:00 INFO kernel: [  217.462767] wlan0: send auth to $AP_MAC_ADDR (try 1/3)
2020-04-06T21:32:59.448026+00:00 INFO kernel: [  217.467888] wlan0: authenticated
2020-04-06T21:32:59.450028+00:00 INFO kernel: [  217.469023] wlan0: associate with $AP_MAC_ADDR (try 1/3)
2020-04-06T21:32:59.454034+00:00 INFO kernel: [  217.473296] wlan0: RX AssocResp from $AP_MAC_ADDR (capab=0x31 status=0 aid=12)
2020-04-06T21:32:59.456313+00:00 INFO kernel: [  217.475523] wlan0: associated
2020-04-06T21:33:00.213990+00:00 INFO avahi-daemon[1440]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.254.41.
2020-04-06T21:33:00.214973+00:00 INFO avahi-daemon[1440]: New relevant interface wlan0.IPv4 for mDNS.
2020-04-06T21:33:00.215152+00:00 INFO avahi-daemon[1440]: Registering new address record for 192.168.254.41 on wlan0.IPv4.
2020-04-06T21:33:00.284148+00:00 ERR /usr/bin/shill[1094]: [warn] Epoll ADD(1) on fd 19 failed. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none): Bad file descriptor
2020-04-06T21:33:00.284226+00:00 ERR /usr/bin/shill[1094]: [warn] Epoll ADD(1) on fd 20 failed. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none): Bad file descriptor
2020-04-06T21:33:00.284269+00:00 ERR shill[1088]: [ERROR:rtnl_handler.cc(338)] sequence 161 (Add Address: AddressStatus prefix_len 24 flags 0 scope 0) received error 17 (File exists)
2020-04-06T21:33:01.378442+00:00 NOTICE dbus[434]: [system] Activating service name='org.chromium.SmbProvider' (using servicehelper)
2020-04-06T21:33:01.628489+00:00 INFO smbproviderd[6887]: NTLM protocol is disabled
2020-04-06T21:33:01.631233+00:00 NOTICE dbus[434]: [system] Successfully activated service 'org.chromium.SmbProvider'
2020-04-06T21:33:25.835042+00:00 INFO kernel: [  243.854616] wlan0: Connection to AP $AP_MAC_ADDR lost
2020-04-06T21:33:25.884541+00:00 ERR shill[1088]: [ERROR:object_proxy.cc(594)] Failed to call method: fi.w1.wpa_supplicant1.Interface.Disconnect: object_path= /fi/w1/wpa_supplicant1/Interfaces/1: fi.w1.wpa_supplicant1.NotConnected: This interface is not connected
2020-04-06T21:33:25.884646+00:00 ERR shill[1088]: [ERROR:dbus_method_invoker.h(113)] CallMethodAndBlockWithTimeout(...): Domain=dbus, Code=fi.w1.wpa_supplicant1.NotConnected, Message=This interface is not connected
2020-04-06T21:33:25.884693+00:00 ERR shill[1088]: [ERROR:supplicant_interface_proxy.cc(168)] Failed to disconnect: fi.w1.wpa_supplicant1.NotConnected This interface is not connected
2020-04-06T21:33:25.918612+00:00 INFO avahi-daemon[1440]: Withdrawing address record for 192.168.254.41 on wlan0.
2020-04-06T21:33:25.918689+00:00 INFO avahi-daemon[1440]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.254.41.
2020-04-06T21:33:25.918736+00:00 INFO avahi-daemon[1440]: Interface wlan0.IPv4 no longer relevant for mDNS.
2020-04-06T21:33:25.923516+00:00 ERR shill[1088]: [ERROR:wifi.cc(798)] Can't get endpoint for current supplicant BSS /fi/w1/wpa_supplicant1/Interfaces/1/BSSs/50
2020-04-06T21:33:26.056609+00:00 INFO avahi-daemon[1440]: Withdrawing address record for 100.115.92.1 on arcbr0.
2020-04-06T21:33:26.056697+00:00 INFO avahi-daemon[1440]: Registering new address record for 100.115.92.1 on arcbr0.IPv4.


[2] dmsg
[  678.957865] iwlwifi 0000:01:00.0: I iwl_pcie_rx_handle_rb Q 0: RB end marker at offset 64
[  678.957867] iwlwifi 0000:01:00.0: U _iwl_enable_interrupts Enabling interrupts
[  678.965644] iwlwifi 0000:01:00.0: U iwl_pcie_int_cause_ict ICT index 657 value 0x00001000
[  678.965686] iwlwifi 0000:01:00.0: U iwl_pcie_irq_handler ISR inta 0x10000000, enabled 0xba00008b(sw), enabled(hw) 0x00000000, fh 0x00000000
[  678.965741] iwlwifi 0000:01:00.0: U iwl_pcie_irq_handler inta 0x10000000, enabled 0x00000000
[  678.965742] iwlwifi 0000:01:00.0: U iwl_pcie_irq_handler Rx interrupt
[  678.965745] iwlwifi 0000:01:00.0: I iwl_pcie_rx_handle Q 0: HW = SW = 25
[  678.965748] iwlwifi 0000:01:00.0: U _iwl_enable_interrupts Enabling interrupts
[  679.057663] iwlwifi 0000:01:00.0: U iwl_pcie_int_cause_ict ICT index 658 value 0x00148000
[  679.057707] iwlwifi 0000:01:00.0: U iwl_pcie_irq_handler ISR inta 0x80000000, enabled 0xba00008b(sw), enabled(hw) 0x00000000, fh 0x00000000
[  679.057762] iwlwifi 0000:01:00.0: U iwl_pcie_irq_handler inta 0x80000000, enabled 0x00000000
[  679.057764] iwlwifi 0000:01:00.0: U iwl_pcie_irq_handler Rx interrupt
[  679.057767] iwlwifi 0000:01:00.0: I iwl_pcie_rx_handle Q 0: HW = 26, SW = 25
[  679.057771] iwlwifi 0000:01:00.0: I iwl_pcie_rx_handle_rb Q 0: cmd at offset 0: MISSED_BEACONS_NOTIFICATION (00.a2, seq 0xab88)
[  679.057775] iwlwifi 0000:01:00.0: I iwl_mvm_rx_missed_beacons_notif missed bcn mac_id=0, consecutive=17 (2, 0, 17)
[  679.057782] iwlwifi 0000:01:00.0: I iwl_pcie_rx_handle_rb Q 0: RB end marker at offset 64
[  679.057785] iwlwifi 0000:01:00.0: U _iwl_enable_interrupts Enabling interrupts
[  679.057792] wlan0: Connection to AP $AP_MAC_ADDR lost

Not sure if my problem had the same root, but recently I bought new router with two bands - 2.4GHz and 5GHz. After that I started suffering from random wifi reconnections on my pixelbook. The strange thing was - the 2.4 network was not visible at all on pixelbook, and 5GHz was visible, but always disconnected and reconnected. On all other devices everything was fine.
I have discovered that 2.4GHz network was working on channel 13 on my router, channel 13 is prohibited in the US and some other countries, but it is fine to use it in my country. Router took channel 13 automatically as all other channels are loaded at my environment. I have adjusted router settings so it would work on channels 1-12 for 2.4 network, after that network became visible on pixelbook all the time. And somehow it also affected 5GHz connection as well - now connection to 5GHz is stable and works fine also.
Hope this may help someone.

Thanks for your info, jt.pepe@. It would be helpful if you can upload a user feedback with "crbug.com/948179#c62" when your set up your AP/DUT in a repeatedly disconnect scenario. What's the brand/model of your AP? Which country code your AP is configured?

Update summary as it is related to beacon loss according to logs in comment 60.

#61:
> Brian, any hint to decrypt the iwlwifi debug message in dmesg?

I don't have anything to add right now. Those are debug messages from running chrome://net-internals#chromeos and hitting the "Wi-Fi" button (or, there's a similar `crosh` command I think?). It triggers this code [1].

To glean anything from that...well, you have to read through the driver. Or maybe ask Intel, if you think there's an actual lead in there. Often times, those logs are more noise than useful.

[1] http://cs/chromeos_public/src/platform2/debugd/src/debug_mode_tool.cc?l=69&rcl=357cf00138c37ecf858a1a9fd40c784f06b01457

Just a small update: I have noticed that whenever I use my Chromebook on my Pixel's hotspot, there aren't any connectivity issues. However, the issue still remains whenever I connect to my at-home WiFi; it is the ONLY device to have issues when connected. Any chance I could get direction on how to possibly figure out why there's a connectivity issue with one connection, but not another?

Answering to deanliao@chromium.org.
I am new to this forum and maybe doing something wrong, but I am going to send feedback from my Chromebook (if I understand correctly, this is what you meant) also, just for information here, my AP model is D-Link DIR-853, and country code is set to Ukraine - UA. Just for update, since I have set my AP to work on standard channels for 2.4GHz - 1-12, I am not having any issues with connection.

Re comment 67, good to know your issue is mitigated, jt.pepe@. So you had issue using 5G band but the issue was fixed by using 2.4G band 1-12?

Re comment 66, devanlee18@, after some deep dive into the log, the disconnect were related to consecutive beacon loss. But I cannot identify the root cause of the beacon loss. According to comment 34, you said the Chromebook had issues with different APs. Does any of your friends also use the same model? If so, do they experience the same issue? Or only your device? Maybe it is a hardware issue.
Last question, for the APs having the issue, what security protocol did you use? WPA2 or 802.1x?

My chromebook is also having issues with WIFI dropping conducted comment 5 steps  but file is to large 45 mbs do i need to comprise the file more? or do i need to modify the logs size?

The best way to provide data is to actually file a feedback report as soon as the problem is noticed (alt-shift-i) and reference this issue number in the first line of the description. If you're not connected when the report is filed that is fine, it will be sent as soon as you are able to connect the device.

Otherwise you can upload the file to Google Drive and share it with the issue owner (deanliao@chromium.org).

Thanks!

Lowering priority to P2.

I have the same issue my HP Chromebook x360 doesn't connect to the WiFi, i have turned off the Bluetooth and preferred the WiFi, but nothing happens, it shows on the settings that it's connected but on the browser it says no connection, please help i have only had this laptop for a month and a half and it's very been very annoying and frustrating.

If it helps there is an open bug ticket for this issue related to the QCA6174/ath10k wifi module in the Lenovo Duet

https://bugzilla.kernel.org/show_bug.cgi?id=202601

I am seeing same issues with
https://support.hp.com/us-en/product/hp-chromebook-11-g4/8326193/model/8326197?sku=P0B78UT

Very high density environment with 1 AP per classroom. APs average 50 devices, Chromebooks and BYOD.
Meraki MR46 Access Points.
5GHz only WPA2 SSID.

Chromebooks roam between APs regardless of SNR. Chromebook can have SNR of 55 in the same classroom as AP, but still connects to AP with 25 SNR. It will do so at least once per minute.

I’ve been having the same issue with my kids 2 cheomebooks.  It’s not just the network connectivity issue on the laptop.  Every time they use the chrome book, it takes out my whole local network.  My phone and TV all lose connection.  

I’m having this issue with my Samsung Chromebook. Originally it was in a dead zone spot in my home, but it was connected to a wifi extender. After awhile the connection on the chromebook went in and out. All other devices in my household on both techs router and wifi extender remain stable.

We moved the Chromebook to another room more close to the main router. The connection is better but it still occasionally disconnects. This is the only device  where this happens.

Even this a fairly old thread i see this on an Acer Chromebook when using 5GHz wifi
Disabling 5GHz on the router gives great stability.
Any chance to get this fixed ?

Having same issue on my Pixel Slate ChromeOS tablet, it only happens in my home wifi, not in hotels or other public networks, but of course I use it mostly at home. For no reason it disconnects and reconnects several times for like half a minute and then it is stable until next day. It can happen anytime, some days it works fine all day, some days it fails multiple times. I suspect it is channel swap from AP not well managed by chromeos, in hotels they have central wifi management and several APs visible and only one ssid, at home I only have one AP and many ssid's. So, channel changes frequently to avoid interference, but since there is no other AP broadcasting same ssid, it disconnects until it finds the ssid in the new channel. I will try to put my AP in one fixed channel and see what happens.