New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 877114 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Aug 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

(ChromeOS WiFi) WiFi keeps dropping with ChromeOS version 67

Project Member Reported by aashuto...@chromium.org, Aug 23

Issue description

Copying the description from https://b.corp.google.com/issues/113085668

My customer, AirAsia, is rolling out Pixelbook devices for their employees. They are now running ChromeOS ver 67 and they noticed that WiFi signal is weaker in general, and many users have been complaining about wifi drops.

Is this a common issue in ver 67? if yes, will it be fixed in ver 68?

Thanks.


I have requested esatio@google.com to share logs. Also to note, maybe this issue is similar to one tracked at https://bugs.chromium.org/p/chromium/issues/detail?id=843416
 
Owner: kirtika@chromium.org
Status: Fixed (was: Untriaged)
Fixed in 10952.0.0. Fix is cherry-picked back to R69 and R68, but it was just cp-ed today
and its not clear if there will be anymore R68 stable pushes.
See https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1162876 for details. 
Root-caused at https://b.corp.google.com/issues/79233533
We added an autotest to catch this issue in the future, tracking bug is https://bugs.chromium.org/p/chromium/issues/detail?id=876920

When you get the logs, please check for the following signature: 
2018-04-18T09:27:31.626904-07:00 ERR kernel: [  872.779734] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
2018-04-18T09:27:31.626905-07:00 ERR kernel: [  872.779737] iwlwifi 0000:01:00.0: Status: 0x00000110, count: 6
2018-04-18T09:27:31.626906-07:00 ERR kernel: [  872.779740] iwlwifi 0000:01:00.0: Loaded firmware version: 29.610311.0
2018-04-18T09:27:31.626907-07:00 ERR kernel: [  872.779743] iwlwifi 0000:01:00.0: 0x00000034 | NMI_INTERRUPT_WDG           
2018-04-18T09:27:31.626908-07:00 ERR kernel: [  872.779745] iwlwifi 0000:01:00.0: 0x000002F0 | trm_hw_status0
2018-04-18T09:27:31.626909-07:00 ERR kernel: [  872.779747] iwlwifi 0000:01:00.0: 0x00000000 | trm_hw_status1
2018-04-18T09:27:31.626910-07:00 ERR kernel: [  872.779749] iwlwifi 0000:01:00.0: 0x00041706 | branchlink2
2018-04-18T09:27:31.626911-07:00 ERR kernel: [  872.779751] iwlwifi 0000:01:00.0: 0x000446D2 | interruptlink1
2018-04-18T09:27:31.626911-07:00 ERR kernel: [  872.779753] iwlwifi 0000:01:00.0: 0x0000C6B8 | interruptlink2
2018-04-18T09:27:31.626912-07:00 ERR kernel: [  872.779755] iwlwifi 0000:01:00.0: 0x00000000 | data1
2018-04-18T09:27:31.626913-07:00 ERR kernel: [  872.779756] iwlwifi 0000:01:00.0: 0x00000002 | data2
2018-04-18T09:27:31.626914-07:00 ERR kernel: [  872.779758] iwlwifi 0000:01:00.0: 0x07030000 | data3
2018-04-18T09:27:31.626915-07:00 ERR kernel: [  872.779760] iwlwifi 0000:01:00.0: 0x00000000 | beacon time
2018-04-18T09:27:31.626916-07:00 ERR kernel: [  872.779762] iwlwifi 0000:01:00.0: 0x00034C73 | tsf low
2018-04-18T09:27:31.626917-07:00 ERR kernel: [  872.779764] iwlwifi 0000:01:00.0: 0x00000000 | tsf hi
2018-04-18T09:27:31.626918-07:00 ERR kernel: [  872.779766] iwlwifi 0000:01:00.0: 0x00000000 | time gp1
2018-04-18T09:27:31.626919-07:00 ERR kernel: [  872.779768] iwlwifi 0000:01:00.0: 0x00034C73 | time gp2
2018-04-18T09:27:31.626920-07:00 ERR kernel: [  872.779770] iwlwifi 0000:01:00.0: 0x00000009 | uCode revision type
2018-04-18T09:27:31.626921-07:00 ERR kernel: [  872.779772] iwlwifi 0000:01:00.0: 0x0000001D | uCode version major
2018-04-18T09:27:31.626921-07:00 ERR kernel: [  872.779774] iwlwifi 0000:01:00.0: 0x00095007 | uCode version minor
2018-04-18T09:27:31.626923-07:00 ERR kernel: [  872.779776] iwlwifi 0000:01:00.0: 0x00000210 | hw version
2018-04-18T09:27:31.626923-07:00 ERR kernel: [  872.779778] iwlwifi 0000:01:00.0: 0x00C89200 | board version
2018-04-18T09:27:31.626924-07:00 ERR kernel: [  872.779780] iwlwifi 0000:01:00.0: 0x0002016A | hcmd
2018-04-18T09:27:31.626925-07:00 ERR kernel: [  872.779782] iwlwifi 0000:01:00.0: 0x02023080 | isr0
2018-04-18T09:27:31.626926-07:00 ERR kernel: [  872.779784] iwlwifi 0000:01:00.0: 0x00000000 | isr1
2018-04-18T09:27:31.626927-07:00 ERR kernel: [  872.779786] iwlwifi 0000:01:00.0: 0x00000002 | isr2
2018-04-18T09:27:31.626928-07:00 ERR kernel: [  872.779788] iwlwifi 0000:01:00.0: 0x004000C0 | isr3
2018-04-18T09:27:31.626929-07:00 ERR kernel: [  872.779790] iwlwifi 0000:01:00.0: 0x00000080 | isr4
2018-04-18T09:27:31.626930-07:00 ERR kernel: [  872.779792] iwlwifi 0000:01:00.0: 0x0002016A | last cmd Id
2018-04-18T09:27:31.626931-07:00 ERR kernel: [  872.779794] iwlwifi 0000:01:00.0: 0x00000000 | wait_event
2018-04-18T09:27:31.626932-07:00 ERR kernel: [  872.779796] iwlwifi 0000:01:00.0: 0x00000000 | l2p_control
2018-04-18T09:27:31.626933-07:00 ERR kernel: [  872.779798] iwlwifi 0000:01:00.0: 0x00000000 | l2p_duration
2018-04-18T09:27:31.626934-07:00 ERR kernel: [  872.779800] iwlwifi 0000:01:00.0: 0x00000000 | l2p_mhvalid
2018-04-18T09:27:31.626935-07:00 ERR kernel: [  872.779802] iwlwifi 0000:01:00.0: 0x00000000 | l2p_addr_match
2018-04-18T09:27:31.626935-07:00 ERR kernel: [  872.779804] iwlwifi 0000:01:00.0: 0x00000007 | lmpm_pmg_sel
2018-04-18T09:27:31.626936-07:00 ERR kernel: [  872.779806] iwlwifi 0000:01:00.0: 0x29102230 | timestamp
2018-04-18T09:27:31.626937-07:00 ERR kernel: [  872.779808] iwlwifi 0000:01:00.0: 0x00340010 | flow_handler
2018-04-18T09:27:31.626938-07:00 ERR kernel: [  872.779813] iwlwifi 0000:01:00.0: Firmware error during reconfiguration - reprobe!
2018-04-18T09:27:31.626939-07:00 ERR kernel: [  872.779821] iwlwifi 0000:01:00.0: Failed to run INIT calibrations: -5
2018-04-18T09:27:31.626940-07:00 ERR kernel: [  872.779823] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -5
2018-04-18T09:27:31.626941-07:00 ERR kernel: [  872.779825] iwlwifi 0000:01:00.0: Failed to start RT ucode: -5

If you don't see this signature, the root cause is different, and reopen this assigning to me. 


Hi Kirtika,

How to collect the log from the Chromebook? Please advise and I will ask my client to collect it and check if the signature is similar.

Thanks.
To collect logs locally, 
1)Navigate to "chrome://net-internals/#chromeos" on the Chromebook
2)Click on "Store Debug Logs" button. The log file should get created in the Downloads folder. 
The failure signature, if present should be in net.log* file.

Also, users can report feedback by pressing Alt+Ctrl+i. More info @https://support.google.com/chromebook/answer/2982029?hl=en
Status: Verified (was: Fixed)
Closing this as Verified. Re-open if you continue to see this issue. 

Sign in to add a comment