Comment 10 for bug 1270808

Revision history for this message
Li The G No Lie (helpunclejackoff) wrote :

Hi,

Thanks for the patch @sforshee! My WLAN experience has improved quite a bit. I now believe my router also has problems, but that's another issue for my ISP.

I only have this error in /var/log/syslog to report:

Nov 1 08:59:14 loneliverse kernel: [ 2225.990764] ------------[ cut here ]------------
Nov 1 08:59:14 loneliverse kernel: [ 2225.990773] WARNING: CPU: 7 PID: 222 at /tmp/kernel-sforshee-IXMwpI4I/build/fs/proc/generic.c:522 remove_proc_entry+0x19f/0x1b0()
Nov 1 08:59:14 loneliverse kernel: [ 2225.990775] remove_proc_entry: removing non-empty directory 'fs/nfsfs', leaking at least 'volumes'
Nov 1 08:59:14 loneliverse kernel: [ 2225.990776] Modules linked in: ctr ccm cuse bnep rfcomm bluetooth nfsd binfmt_misc auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_realtek snd_hda_codec_hdmi arc4 iwldvm snd_hda_intel mac80211 snd_hda_codec x86_pkg_temp_thermal intel_powerclamp snd_hwdep snd_pcm coretemp snd_page_alloc snd_seq_midi snd_seq_midi_event radeon snd_rawmidi kvm_intel snd_seq uvcvideo kvm videobuf2_vmalloc videobuf2_memops videobuf2_core iwlwifi snd_seq_device videodev ttm snd_timer cfg80211 shpchp snd mei_me joydev rtsx_pci_ms soundcore mei serio_raw memstick lpc_ich mac_hid parport_pc ppdev lp parport dm_crypt ses enclosure usb_storage hid_generic usbhid hid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper i915 cryptd firewire_ohci ahci psmouse firewire_core r8169 libahci rtsx_pci crc_itu_t mii i2c_algo_bit drm_kms_helper video wmi drm
Nov 1 08:59:14 loneliverse kernel: [ 2225.990822] CPU: 7 PID: 222 Comm: kworker/u16:4 Tainted: G I 3.13.0-38-generic #65+iwlwifi201410162240
Nov 1 08:59:14 loneliverse kernel: [ 2225.990823] Hardware name: Notebook P15SM /P15SM , BIOS 4.6.5 08/06/2013
Nov 1 08:59:14 loneliverse kernel: [ 2225.990827] Workqueue: netns cleanup_net
Nov 1 08:59:14 loneliverse kernel: [ 2225.990828] 0000000000000009 ffff88021e8c3c80 ffffffff8171ece7 ffff88021e8c3cc8
Nov 1 08:59:14 loneliverse kernel: [ 2225.990831] ffff88021e8c3cb8 ffffffff8106773d ffff880035e06f80 0000000000000005
Nov 1 08:59:14 loneliverse kernel: [ 2225.990833] ffffffffa087b948 ffff88021eabcab0 ffff880035e06ff5 ffff88021e8c3d18
Nov 1 08:59:14 loneliverse kernel: [ 2225.990835] Call Trace:
Nov 1 08:59:14 loneliverse kernel: [ 2225.990839] [<ffffffff8171ece7>] dump_stack+0x45/0x56
Nov 1 08:59:14 loneliverse kernel: [ 2225.990842] [<ffffffff8106773d>] warn_slowpath_common+0x7d/0xa0
Nov 1 08:59:14 loneliverse kernel: [ 2225.990855] [<ffffffff810677ac>] warn_slowpath_fmt+0x4c/0x50
Nov 1 08:59:14 loneliverse kernel: [ 2225.990857] [<ffffffff812298ef>] remove_proc_entry+0x19f/0x1b0
Nov 1 08:59:14 loneliverse kernel: [ 2225.990863] [<ffffffffa085b4e2>] nfs_fs_proc_net_exit+0x62/0x70 [nfs]
Nov 1 08:59:14 loneliverse kernel: [ 2225.990868] [<ffffffffa08615b2>] nfs_net_exit+0x12/0x20 [nfs]
Nov 1 08:59:14 loneliverse kernel: [ 2225.990870] [<ffffffff8161b3a9>] ops_exit_list.isra.1+0x39/0x60
Nov 1 08:59:14 loneliverse kernel: [ 2225.990871] [<ffffffff8161bc30>] cleanup_net+0x110/0x250
Nov 1 08:59:14 loneliverse kernel: [ 2225.990874] [<ffffffff810839c2>] process_one_work+0x182/0x450
Nov 1 08:59:14 loneliverse kernel: [ 2225.990876] [<ffffffff810847b1>] worker_thread+0x121/0x410
Nov 1 08:59:14 loneliverse kernel: [ 2225.990878] [<ffffffff81084690>] ? rescuer_thread+0x430/0x430
Nov 1 08:59:14 loneliverse kernel: [ 2225.990880] [<ffffffff8108b492>] kthread+0xd2/0xf0
Nov 1 08:59:14 loneliverse kernel: [ 2225.990881] [<ffffffff8108b3c0>] ? kthread_create_on_node+0x1c0/0x1c0
Nov 1 08:59:14 loneliverse kernel: [ 2225.990884] [<ffffffff8172f73c>] ret_from_fork+0x7c/0xb0
Nov 1 08:59:14 loneliverse kernel: [ 2225.990885] [<ffffffff8108b3c0>] ? kthread_create_on_node+0x1c0/0x1c0
Nov 1 08:59:14 loneliverse kernel: [ 2225.990886] ---[ end trace d5d7145b575ceae1 ]---

It doesn't happen often, but when it does it seems like all wifi communication goes still.
I'm also seeing this in the logs, but I don't know if it's related to the patch:

Nov 1 13:30:14 loneliverse wpa_supplicant[1803]: wlan0: CTRL-EVENT-SCAN-STARTED
Nov 1 13:30:33 loneliverse wpa_supplicant[1803]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Nov 1 13:32:14 loneliverse wpa_supplicant[1803]: wlan0: CTRL-EVENT-SCAN-STARTED
Nov 1 14:32:14 loneliverse wpa_supplicant[1803]: message repeated 30 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]
Nov 1 14:32:29 loneliverse wpa_supplicant[1803]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Nov 1 14:34:14 loneliverse wpa_supplicant[1803]: wlan0: CTRL-EVENT-SCAN-STARTED
Nov 1 14:34:42 loneliverse wpa_supplicant[1803]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Nov 1 14:36:14 loneliverse wpa_supplicant[1803]: wlan0: CTRL-EVENT-SCAN-STARTED
Nov 1 15:48:14 loneliverse wpa_supplicant[1803]: message repeated 36 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]

Cheers!