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

Issue 688944 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ wnhuang@chromium.org
briannorris@chromium.org
snanda@chromium.org
█ kirtika@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

ChromeOS: kernel warning %__cfg80211_connect_result+% since 9086.0.0

Project Member Reported by djkurtz@google.com, Feb 6 2017 
Looking at the crash server, this appears to be a relatively recent regression.

Oldest reports are from 2016/12/17 (9086.0.0): https://crash.corp.google.com/browse?q=ReportID='df44468080000000'


PRODUCT VERSION
9211.0.0	0.60%	2	
9202.12.0	4.17%	14	
9202.7.0	4.46%	15	
9202.1.0	4.17%	14	
9169.0.0	0.30%	1	
9166.0.0	0.30%	1	
9150.0.0	9.23%	31	
9129.0.0	0.30%	1	
9111.0.0	0.30%	1	
9089.0.0	0.60%	2	
9086.0.0	74.11%	249	
9085.0.0	0.30%	1	
9081.0.0	0.30%	1	
9068.0.0	0.30%	1	
9065.0.0	0.30%	1	
9061.0.0	0.30%	1	
Total:	100.00%	336

335/336 reports are from ARM devices (there is just one exception, from a clapper): https://crash.corp.google.com/browse?q=ReportID='e1abd2c880000000'

I see reports from many different ARM devices on several kernels:
  3.8: snow, spring, pi
 3.10: blaze
 3.14: mickey, minnie, speedy
 3.18: elm, hana

70% (235/336) of reports are from minnie.

Example report: https://crash.corp.google.com/browse?q=ReportID='5261d65580000000'
upload_file_kcrash:

e5e6bb8e-__cfg80211_connect_result+0x2b0/0x398 [cfg80211]()
/mnt/host/source/src/third_party/kernel/v3.18/net/wireless/sme.c:655 __cfg80211_connect_result+0x2b0/0x398 [cfg80211]()
2017-02-03T13:27:18.213495+01:00 WARNING kernel: [ 8565.728235] Modules linked in: tun xt_TCPMSS ip6table_mangle veth uinput rfcomm uvcvideo videobuf2_vmalloc mwifiex_sdio mwifiex btmrvl_sdio btmrvl i2c_dev ip6t_REJECT nf_reject_ipv6 ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat bluetooth xt_mark bridge fuse stp llc zram cfg80211 ip6table_filter snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device joydev
2017-02-03T13:27:18.213502+01:00 WARNING kernel: [ 8565.728315] CPU: 2 PID: 18656 Comm: kworker/u8:2 Not tainted 3.18.0-13739-gbf5e73b #1
2017-02-03T13:27:18.213507+01:00 WARNING kernel: [ 8565.728319] Hardware name: Mediatek Elm rev3 board (DT)
2017-02-03T13:27:18.213511+01:00 WARNING kernel: [ 8565.728328] Workqueue: cfg80211 0xffffffbffc053128
2017-02-03T13:27:18.213516+01:00 EMERG kernel: [ 8565.728334] Call trace:
2017-02-03T13:27:18.213520+01:00 WARNING kernel: [ 8565.728351] [<ffffffc000208f0c>] dump_backtrace+0x0/0x160
2017-02-03T13:27:18.213526+01:00 WARNING kernel: [ 8565.728360] [<ffffffc000209088>] show_stack+0x1c/0x28
2017-02-03T13:27:18.213531+01:00 WARNING kernel: [ 8565.728369] [<ffffffc0008e6bd0>] dump_stack+0x80/0xc4
2017-02-03T13:27:18.213536+01:00 WARNING kernel: [ 8565.728376] [<ffffffc000222a40>] warn_slowpath_common+0x90/0xb8
2017-02-03T13:27:18.213540+01:00 WARNING kernel: [ 8565.728381] [<ffffffc000222bf4>] warn_slowpath_null+0x34/0x44
2017-02-03T13:27:18.213545+01:00 WARNING kernel: [ 8565.728389] [<ffffffbffc07d59c>] __cfg80211_connect_result+0x2ac/0x398 [cfg80211]
2017-02-03T13:27:18.213549+01:00 WARNING kernel: [ 8565.728397] [<ffffffbffc058344>] cfg80211_process_wdev_events+0xe4/0x1e0 [cfg80211]
2017-02-03T13:27:18.213554+01:00 WARNING kernel: [ 8565.728405] [<ffffffbffc05848c>] cfg80211_process_rdev_events+0x4c/0x78 [cfg80211]
2017-02-03T13:27:18.213558+01:00 WARNING kernel: [ 8565.728410] [<ffffffbffc053148>] 0xffffffbffc053148
2017-02-03T13:27:18.213562+01:00 WARNING kernel: [ 8565.728423] [<ffffffc00023a984>] process_one_work+0x248/0x3fc
2017-02-03T13:27:18.213567+01:00 WARNING kernel: [ 8565.728428] [<ffffffc00023bc28>] worker_thread+0x330/0x450
2017-02-03T13:27:18.213571+01:00 WARNING kernel: [ 8565.728433] [<ffffffc000240cc8>] kthread+0xf4/0x100
2017-02-03T13:27:18.213575+01:00 WARNING kernel: [ 8565.728437] ---[ end trace 5183d2a62452c3b2 ]---

Comment 1 by djkurtz@chromium.org, Feb 6 2017

Cc: wnhuang@chromium.org briannorris@chromium.org snanda@chromium.org
Components: OS>Systems>Network
Labels: -Pri-3 OS-Chrome Pri-2
Status: Available (was: Unconfirmed)

Comment 2 by anakmanj...@gmail.com, Feb 6 2017

Comment 3 by briannorris@chromium.org, Feb 6 2017

Cc: kirtika@chromium.org
I don't see any relevant changes in (e.g.) the 3.14 kernel looking at a range like 9040.0.0..9086.0.0. Are you sure this is the actual regression timing, or is it just an increase in testing? I know that, for instance, minnie gets a lot of beta/dev testing, since people moved there to get ARC++ early. That could skew the data a bit.

You note mid-December for some reports: how far back does the crash reporter even track?

Comment 4 by kirtika@chromium.org, Feb 6 2017 

Keep in mind that the stable signatures on crash/ shift around, so the 9086.0.0 is only for this incarnation of the stable signature. 
I've seen crash/ go back as far 75XX.X.X. 

That said, looking into the warning now.
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 27 2017

Labels: Hotlist-Google
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 27

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by marcuskoehler@chromium.org, Jan 15

Labels: Enterprise-Triaged
►

Sign in to add a comment