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

Issue 616125 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

HP Chromebook 14 - WiFi dies intermittently and requires a full restart to recover

Project Member Reported by lukasza@chromium.org, May 31 2016

Issue description

Version:
Google Chrome 50.0.2661.103 (Official Build) (64-bit)
Platform 7978.74.0 (Official Build) stable-channel falco

What steps will reproduce the problem?
(1) Wait for 5-10 minutes after booting

What is the expected output?
WiFi keeps working + keeps seeing all nearby WiFi networks

What do you see instead?
WiFi stops working + shows zero networks + dmesg says that it cannot wake the phy0 device.


In dmesg run from crosh I see lots of:
[  331.609937] ath: phy0: Failed to wakeup in 500us
[  331.629944] ath: phy0: Failed to wakeup in 500us
and:
[  336.178774] ath: phy0: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
[  336.178778] ath: phy0: Chip reset failed
[  336.178787] ath: phy0: Unable to reset channel, reset status -22
[  336.178925] ath: phy0: Unable to set channel
[  336.190149] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
[  336.190180] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
[  336.251761] ath: phy0: Failed to stop TX DMA, queues=0x10f!

 
Cc: ovanieva@chromium.org jleong@chromium.org kirtika@chromium.org agoode@chromium.org snanda@chromium.org
This might be a hardware problem, but at least one other user noticed similar, recent WiFi flakiness, so we might want to double-check if this is a more wide-spread issue.

Do we know if Falco wifi problem reports have increased recently?
Cc: semenzato@chromium.org
Status: WontFix (was: Untriaged)
Marking as WontFix - this probably was a hardware issue + I've returned the ChromeBook so there is probably nothing more that can be done about this bug.

Sign in to add a comment