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

Issue 692753 link

Starred by 1 user
Status: Assigned
Owner:
█ kirtika@chromium.org
Last visit > 30 days ago
Cc:
snanda@chromium.org
█ keta...@chromium.org
█ cernekee@chromium.org
semenzato@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Kernel warning: da034d0f-ieee80211_enable_keys+0x90/0x153 [iwl7000_mac80211]()

Project Member Reported by keta...@chromium.org, Feb 15 2017 
Chrome Version: (copy from chrome://version)
OS: Product versionChromeOS, 9202.12.0

Report ID4806010a80000000
, 
Process type kernel-warning
Report TimeWed, 15 Feb 2017 20:23:51 GMT
Client ID466adf1acbc64ea09539d868aa0abc85


da034d0f-ieee80211_enable_keys+0x90/0x153 [iwl7000_mac80211]()

/mnt/host/source/src/third_party/kernel/v3.18/drivers/net/wireless/iwl7000/mac80211/key.c:682 ieee80211_enable_keys+0x90/0x153 [iwl7000_mac80211]()
2017-02-15T06:38:15.236018-04:00 WARNING kernel: [ 2825.283279] Modules linked in: ip6t_REJECT nf_reject_ipv6 xt_TCPMSS ip6table_mangle ccm veth uinput cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core btusb btrtl btbcm btintel ipt_MASQUERADE nf_nat_masquerade_ipv4 snd_soc_sst_cht_bsw_max98090_ti iptable_nat memconsole_x86_legacy memconsole iwlmvm nf_nat_ipv4 nf_nat snd_hda_codec_hdmi iwlwifi iwl7000_mac80211 bluetooth snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core xt_mark snd_intel_sst_acpi snd_soc_sst_acpi snd_intel_sst_core snd_soc_sst_mfld_platform snd_soc_max98090 bridge stp llc fuse zram cfg80211 ip6table_filter snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iio_trig_sysfs joydev cros_ec_sensors_ring cros_ec_sensors cros_ec_sensors_core industrialio_triggered_buffer kfifo_buf industrialio
2017-02-15T06:38:15.236020-04:00 WARNING kernel: [ 2825.283513] CPU: 0 PID: 17931 Comm: kworker/u4:13 Tainted: G        W      3.18.0-13739-gbf5e73b #1
2017-02-15T06:38:15.236022-04:00 WARNING kernel: [ 2825.283531] Hardware name: GOOGLE Cyan, BIOS Google_Cyan.7287.57.92 11/06/2016
2017-02-15T06:38:15.236027-04:00 WARNING kernel: [ 2825.283549] Workqueue: events_unbound async_run_entry_fn
2017-02-15T06:38:15.236030-04:00 WARNING kernel: [ 2825.283565]  0000000000000000 0000000094dbb28e ffff88001fa77bf8 ffffffffbd0a0b67
2017-02-15T06:38:15.236032-04:00 WARNING kernel: [ 2825.283586]  0000000000000000 0000000000000000 ffff88001fa77c38 ffffffffbca63c4c
2017-02-15T06:38:15.236034-04:00 WARNING kernel: [ 2825.283606]  ffff88001fa77c28 ffffffffc03d72d2 ffff880169aa4900 0000000000000001
2017-02-15T06:38:15.236035-04:00 WARNING kernel: [ 2825.283627] Call Trace:
2017-02-15T06:38:15.236037-04:00 WARNING kernel: [ 2825.283640]  [<ffffffffbd0a0b67>] dump_stack+0x4e/0x71
2017-02-15T06:38:15.236042-04:00 WARNING kernel: [ 2825.283658]  [<ffffffffbca63c4c>] warn_slowpath_common+0x81/0x9b
2017-02-15T06:38:15.236045-04:00 WARNING kernel: [ 2825.283683]  [<ffffffffc03d72d2>] ? ieee80211_enable_keys+0x90/0x153 [iwl7000_mac80211]
2017-02-15T06:38:15.236047-04:00 WARNING kernel: [ 2825.283705]  [<ffffffffbca63d4f>] warn_slowpath_null+0x1a/0x1c
2017-02-15T06:38:15.236048-04:00 WARNING kernel: [ 2825.283724]  [<ffffffffc03d72d2>] ieee80211_enable_keys+0x90/0x153 [iwl7000_mac80211]
2017-02-15T06:38:15.236050-04:00 WARNING kernel: [ 2825.283755]  [<ffffffffc03da65e>] ieee80211_reconfig+0x794/0xad3 [iwl7000_mac80211]
2017-02-15T06:38:15.236052-04:00 WARNING kernel: [ 2825.283782]  [<ffffffffc03c883c>] __iwl7000_ieee80211_csa_finish+0x127d/0x3284 [iwl7000_mac80211]
2017-02-15T06:38:15.236054-04:00 WARNING kernel: [ 2825.283808]  [<ffffffffc0252104>] cfg80211_leave+0x735/0x90b [cfg80211]
2017-02-15T06:38:15.236059-04:00 WARNING kernel: [ 2825.283830]  [<ffffffffc0252086>] ? cfg80211_leave+0x6b7/0x90b [cfg80211]
2017-02-15T06:38:15.236061-04:00 WARNING kernel: [ 2825.283849]  [<ffffffffbce0730a>] dpm_run_callback+0x4a/0xae
2017-02-15T06:38:15.236063-04:00 WARNING kernel: [ 2825.283861]  [<ffffffffbce07874>] device_resume+0x184/0x1c6
2017-02-15T06:38:15.236065-04:00 WARNING kernel: [ 2825.283877]  [<ffffffffbce078d4>] async_resume+0x1e/0x45
2017-02-15T06:38:15.236067-04:00 WARNING kernel: [ 2825.283897]  [<ffffffffbca7fda3>] async_run_entry_fn+0x38/0xcf
2017-02-15T06:38:15.236069-04:00 WARNING kernel: [ 2825.283910]  [<ffffffffbca78993>] process_one_work+0x176/0x2d4
2017-02-15T06:38:15.236070-04:00 WARNING kernel: [ 2825.283927]  [<ffffffffbca79318>] worker_thread+0x1ec/0x2bf
2017-02-15T06:38:15.236081-04:00 WARNING kernel: [ 2825.283939]  [<ffffffffbca7912c>] ? rescuer_thread+0x2db/0x2db
2017-02-15T06:38:15.236083-04:00 WARNING kernel: [ 2825.283955]  [<ffffffffbca7d3e2>] kthread+0x10e/0x116
2017-02-15T06:38:15.236085-04:00 WARNING kernel: [ 2825.283972]  [<ffffffffbca7d2d4>] ? __kthread_parkme+0x67/0x67
2017-02-15T06:38:15.236087-04:00 WARNING kernel: [ 2825.283984]  [<ffffffffbd0a5cec>] ret_from_fork+0x7c/0xb0
2017-02-15T06:38:15.236089-04:00 WARNING kernel: [ 2825.284018]  [<ffffffffbca7d2d4>] ? __kthread_parkme+0x67/0x67
2017-02-15T06:38:15.236091-04:00 WARNING kernel: [ 2825.284029] ---[ end trace a21c62923cdfe8bf ]---

Luigi, Can we make this warning less noisy or remove it entirely? Currently this is the top warning across all crashes and it might be masking some real bugs underneath.
upload_file_kcrash-4806010a80000000.kcrash
4.3 KB Download

Comment 1 by keta...@chromium.org, Feb 15 2017

Cc: snanda@chromium.org

Comment 2 by snanda@chromium.org, Feb 15 2017

Cc: cernekee@chromium.org
Owner: kirtika@chromium.org

Comment 3 by semenzato@chromium.org, Feb 15 2017

Cc: keta...@chromium.org
It's totally fine with me.  There are several approaches.

1. Fix the problem that causes the warning.
2. Remove the warning.  (Eek.)
3. Blacklist the warning on the warning collector on the clients.  (There is no such mechanism now but it would be easy to add, like 2 hours of work.)
4. Blacklist the warning on the server side.  (No idea how.)
5. Better separation of warnings and actual crashes on the server side.  (No idea how.)
6. Completely remove warning collection.  (Have we used it much yet?  Have we used it *at all*?)

I may have missed a few options.

Comment 4 by kirtika@google.com, Jul 5 2017 

Duplicate of internal bug: https://b.corp.google.com/issues/35587133
Was supposed to be fixed with https://chromium-review.googlesource.com/#/c/442552/ but still exists. I'll follow up there. 


Re #c3:
Reply to Luigi's points, in the same order --
1. Working on it. 
2. Eek. No, we don't want that. 
3. - 
4. - 
5. This already exists, and works pretty well. On crash.corp.google.com, you can 
filter for executable name, and "kernel" and "kernel-warning" are two separate
categories. go/xstability-new also handles this separation well. 
6. Please do not do this. The warning collector is a *super useful* tool (thanks for writing it!) and has pointed out several warnings from Intel wifi.

Comment 5 by matt.c...@intel.corp-partner.google.com, Jul 10 2017 

Hi,

It would be good to verify this issue with the Chrome image that is after 2017-03-04 due to the fix is merged on that date:
https://chromium-review.googlesource.com/c/449034/

Comment 6 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Untriaged)

Comment 7 by zalcorn@chromium.org, Sep 28 

Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.

Comment 8 by weifangsun@chromium.org, Nov 8 

<UI triage> Bug owners, please add the appropriate component to your bug. Thanks!
►

Sign in to add a comment