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

Issue 607919 link

Starred by 1 user
Status: Assigned
Owner:
snanda@chromium.org
Cc:
█ matt.c...@intel.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Chrome OS freezing constantly

Reported by dewayne-...@dpsnc.net, Apr 29 2016 
Chrome Version: 49.0.2623.112
Operating System: e.g., "Windows 7", "Mac OSX 10.6"

URL (if applicable) where crash occurred:

Can you reproduce this crash?

What steps will reproduce this crash? (or if it's not reproducible, what were you doing just before the crash)?

1. Freezing constanly
2.
3.

*Please note that issues filed with no information filled in above will be marked as WontFix*

****DO NOT CHANGE BELOW THIS LINE****
report_id:36fe92e200000000

Comment 1 by ssamanoori@chromium.org, May 3 2016

Labels: OS-Chrome

Comment 2 by dchan@google.com, May 18 2016

Labels: Needs-Feedback
please update with step to repoduce the crash.

Comment 3 by bmahadev@chromium.org, Jun 6 2016

Components: OS>Systems>Network UI
Seems related to the wifi driver :

2016-04-27T10:51:46.757874-04:00 NOTICE kernel: [ 4164.460802] Call Trace:
2016-04-27T10:51:46.757885-04:00 NOTICE kernel: [ 4164.460816]  [<ffffffffb4119b43>] dump_stack+0x19/0x1b
2016-04-27T10:51:46.757896-04:00 NOTICE kernel: [ 4164.460830]  [<ffffffffb3c320ad>] warn_slowpath_common+0x65/0x7d
2016-04-27T10:51:46.757905-04:00 NOTICE kernel: [ 4164.460842]  [<ffffffffb3c321be>] warn_slowpath_null+0x1a/0x1c
2016-04-27T10:51:46.757915-04:00 NOTICE kernel: [ 4164.460858]  [<ffffffffc00bab43>] iwl_trans_pcie_unref+0x23ee/0x24fc [iwlwifi]
2016-04-27T10:51:46.757925-04:00 NOTICE kernel: [ 4164.460873]  [<ffffffffb3c5b107>] ? finish_task_switch+0x69/0xa5
2016-04-27T10:51:46.757934-04:00 NOTICE kernel: [ 4164.460889]  [<ffffffffc016682b>] iwl_mvm_rx_mfuart_notif+0x39b/0x2578 [iwlmvm]
2016-04-27T10:51:46.757945-04:00 NOTICE kernel: [ 4164.460906]  [<ffffffffc01688eb>] iwl_mvm_rx_mfuart_notif+0x245b/0x2578 [iwlmvm]
2016-04-27T10:51:46.757956-04:00 NOTICE kernel: [ 4164.460927]  [<ffffffffc0104363>] __ieee80211_flush_queues+0xc8/0x118 [iwl7000_mac80211]
2016-04-27T10:51:46.757966-04:00 NOTICE kernel: [ 4164.460948]  [<ffffffffc01043c6>] ieee80211_flush_queues+0x13/0x15 [iwl7000_mac80211]
2016-04-27T10:51:46.757977-04:00 NOTICE kernel: [ 4164.460968]  [<ffffffffc011c278>] ieee80211_recalc_ps_vif+0x183/0x125f [iwl7000_mac80211]
2016-04-27T10:51:46.757987-04:00 NOTICE kernel: [ 4164.460988]  [<ffffffffc012084f>] ieee80211_mgd_deauth+0x151/0x192 [iwl7000_mac80211]
2016-04-27T10:51:46.757998-04:00 NOTICE kernel: [ 4164.461008]  [<ffffffffc00f3a7a>] __iwl7000_ieee80211_csa_finish+0x260/0x3987 [iwl7000_mac80211]
2016-04-27T10:51:46.758008-04:00 NOTICE kernel: [ 4164.461028]  [<ffffffffc0065b04>] __cfg80211_mlme_deauth+0x97/0xc6 [cfg80211]
2016-04-27T10:51:46.758017-04:00 NOTICE kernel: [ 4164.461046]  [<ffffffffc0065b96>] cfg80211_mlme_deauth+0x63/0x7c [cfg80211]
2016-04-27T10:51:46.758027-04:00 NOTICE kernel: [ 4164.461082]  [<ffffffffc005635b>] cfg80211_testmode_reply+0x9cd/0xafc [cfg80211]

Can you add the repro' steps and probably upload more data with alt+shift+i if you see the freeze again ?

Comment 4 by abodenha@chromium.org, Jun 7 2016

Cc: snanda@chromium.org
Labels: -Pri-3 Pri-2

Comment 5 by tbuck...@chromium.org, Jun 9 2016

Cc: -snanda@chromium.org
Owner: snanda@chromium.org
Status: Assigned (was: Unconfirmed)
Summary: Chrome OS freezing constantly (was: it needs to be fixed)

Comment 6 by snanda@chromium.org, Jun 9 2016 

My feedback reports search skills are failing me since I can't look up report id 36fe92e200000000.

bmahadev, could you please add a link to the feedback report here since you were able to look it up?

Comment 7 by kirtika@google.com, Dec 19 2016

Cc: matt.c...@intel.com
Labels: -Restrict-View-EditIssue

Comment 8 by matt.c...@intel.com, Dec 19 2016 

What is the entire system log ?
I am afraid of partial of the dump stack does not help because the the driver is built optimizely. Can't trace back in the code correctly.

At the least the log before the stack dump would tell something helpful. :)

Comment 9 by afakhry@chromium.org, Jul 29 2017

Components: -UI
►

Sign in to add a comment