Hello everyone,
i'm running Kubuntu 16.04 as a Virtualbox VM host, and a wireless AP
with an Intel Wireless 7260.
My WLAN connections frequently keep dying, so that i need to disconnect
and reconnect in order to use them again.
My syslog is full of these:
Oct 12 21:48:55 zippy kernel: [3546600.957321] ------------[ cut here
]------------
Oct 12 21:48:55 zippy kernel: [3546600.957352] WARNING: CPU: 2 PID: 1571
at
/build/linux-YyUNAI/linux-4.4.0/drivers/net/wireless/iwlwifi/mvm/utils.c:740
iwl_mvm_disable_txq+0x2a6/0x2c0 [iwlmvm]()
Oct 12 21:48:55 zippy kernel: [3546600.957356] Modules linked in: btrfs
xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c md4
nls_utf8 cifs fscache bnep drbg ansi_cprng ctr ccm pci_stub vboxpci(OE)
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bridge stp llc nf_log_ipv4
nf_log_common xt_LOG xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables arc4
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic
intel_rapl x86_pkg_temp_thermal snd_hda_intel intel_powerclamp coretemp
snd_hda_codec kvm_intel snd_hda_core snd_hwdep input_leds kvm snd_pcm
iwlmvm snd_seq_midi joydev snd_seq_midi_event irqbypass mac80211
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_rawmidi
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper iwlwifi
cryptd snd_seq cfg80211 serio_raw snd_seq_device snd_timer snd mei_me
soundcore mei shpchp hci_uart btbcm btqca btintel intel_lpss_acpi
bluetooth 8250_fintek intel_lpss acpi_als kfifo_buf industrialio
tpm_infineon mac_hid acpi_pad parport_pc ppdev lp parport autofs4
hid_generic usbhid i915_bpo intel_ips i2c_algo_bit drm_kms_helper e1000e
syscopyarea sysfillrect sysimgblt ptp fb_sys_fops psmouse pps_core e100
e1000 ahci drm mii libahci wmi pinctrl_sunrisepoint video i2c_hid
pinctrl_intel hid fjes
Oct 12 21:48:55 zippy kernel: [3546600.957507] CPU: 2 PID: 1571 Comm:
hostapd Tainted: G W OE 4.4.0-93-generic #116-Ubuntu
Oct 12 21:48:55 zippy kernel: [3546600.957511] Hardware name: Gigabyte
Technology Co., Ltd. Z170M-D3H/Z170M-D3H-CF, BIOS F20 11/17/2016
Oct 12 21:48:55 zippy kernel: [3546600.957514] 0000000000000286
f553094adee223e4 ffff880429a2b748 ffffffff813f9f83
Oct 12 21:48:55 zippy kernel: [3546600.957520] 0000000000000000
ffffffffc07335e8 ffff880429a2b780 ffffffff810812f2
Oct 12 21:48:55 zippy kernel: [3546600.957526] ffff88042605d4c8
0000000000000011 ffff88042605d550 0000000000000007
Oct 12 21:48:55 zippy kernel: [3546600.957531] Call Trace:
Oct 12 21:48:55 zippy kernel: [3546600.957541] [<ffffffff813f9f83>]
dump_stack+0x63/0x90
Oct 12 21:48:55 zippy kernel: [3546600.957550] [<ffffffff810812f2>]
warn_slowpath_common+0x82/0xc0
Oct 12 21:48:55 zippy kernel: [3546600.957555] [<ffffffff8108143a>]
warn_slowpath_null+0x1a/0x20
Oct 12 21:48:55 zippy kernel: [3546600.957572] [<ffffffffc070aa46>]
iwl_mvm_disable_txq+0x2a6/0x2c0 [iwlmvm]
Oct 12 21:48:55 zippy kernel: [3546600.957587] [<ffffffffc0709bfd>] ?
iwl_mvm_send_cmd_pdu_status+0x4d/0x70 [iwlmvm]
Oct 12 21:48:55 zippy kernel: [3546600.957604] [<ffffffffc070e588>] ?
iwl_mvm_sta_tx_agg+0xc8/0x150 [iwlmvm]
Oct 12 21:48:55 zippy kernel: [3546600.957621] [<ffffffffc0710853>]
iwl_mvm_sta_tx_agg_flush+0x1b3/0x200 [iwlmvm]
Oct 12 21:48:55 zippy kernel: [3546600.957635] [<ffffffffc0701492>]
iwl_mvm_mac_ampdu_action+0xe2/0x350 [iwlmvm]
Oct 12 21:48:55 zippy kernel: [3546600.957669] [<ffffffffc061db5f>]
drv_ampdu_action+0x6f/0x180 [mac80211]
Oct 12 21:48:55 zippy kernel: [3546600.957702] [<ffffffffc062972d>]
___ieee80211_stop_tx_ba_session+0x13d/0x260 [mac80211]
Oct 12 21:48:55 zippy kernel: [3546600.957734] [<ffffffffc0629e15>]
__ieee80211_stop_tx_ba_session+0x35/0x50 [mac80211]
Oct 12 21:48:55 zippy kernel: [3546600.957763] [<ffffffffc062837f>]
ieee80211_sta_tear_down_BA_sessions+0x3f/0x70 [mac80211]
Oct 12 21:48:55 zippy kernel: [3546600.957790] [<ffffffffc061eab4>]
__sta_info_destroy_part1+0x54/0x470 [mac80211]
Oct 12 21:48:55 zippy kernel: [3546600.957818] [<ffffffffc0621bb6>]
__sta_info_destroy+0x16/0x40 [mac80211]
Oct 12 21:48:55 zippy kernel: [3546600.957826] [<ffffffff81841042>] ?
mutex_lock+0x12/0x30
Oct 12 21:48:55 zippy kernel: [3546600.957852] [<ffffffffc0621c78>]
sta_info_destroy_addr_bss+0x38/0x60 [mac80211]
Oct 12 21:48:55 zippy kernel: [3546600.957888] [<ffffffffc0636dad>]
ieee80211_del_station+0x1d/0x30 [mac80211]
Oct 12 21:48:55 zippy kernel: [3546600.957924] [<ffffffffc04e94d0>]
nl80211_del_station+0xe0/0x1f0 [cfg80211]
Oct 12 21:48:55 zippy kernel: [3546600.957934] [<ffffffff8176c164>]
genl_family_rcv_msg+0x1e4/0x3e0
Oct 12 21:48:55 zippy kernel: [3546600.957941] [<ffffffff81721ab3>] ?
skb_queue_tail+0x43/0x50
Oct 12 21:48:55 zippy kernel: [3546600.957948] [<ffffffff8176c360>] ?
genl_family_rcv_msg+0x3e0/0x3e0
Oct 12 21:48:55 zippy kernel: [3546600.957954] [<ffffffff8176c3d6>]
genl_rcv_msg+0x76/0xb0
Oct 12 21:48:55 zippy kernel: [3546600.957960] [<ffffffff8176b8d4>]
netlink_rcv_skb+0xa4/0xc0
Oct 12 21:48:55 zippy kernel: [3546600.957966] [<ffffffff8176bf68>]
genl_rcv+0x28/0x40
Oct 12 21:48:55 zippy kernel: [3546600.957972] [<ffffffff8176b2aa>]
netlink_unicast+0x18a/0x240
Oct 12 21:48:55 zippy kernel: [3546600.957978] [<ffffffff8176b65b>]
netlink_sendmsg+0x2fb/0x3a0
Oct 12 21:48:55 zippy kernel: [3546600.957986] [<ffffffff813a06f1>] ?
aa_sock_msg_perm+0x61/0x150
Oct 12 21:48:55 zippy kernel: [3546600.957991] [<ffffffff8171aad8>]
sock_sendmsg+0x38/0x50
Oct 12 21:48:55 zippy kernel: [3546600.957996] [<ffffffff8171b581>]
___sys_sendmsg+0x281/0x290
Oct 12 21:48:55 zippy kernel: [3546600.958004] [<ffffffff8122b088>] ?
destroy_inode+0x38/0x60
Oct 12 21:48:55 zippy kernel: [3546600.958010] [<ffffffff8122b1dd>] ?
evict+0x12d/0x190
Oct 12 21:48:55 zippy kernel: [3546600.958016] [<ffffffff8122670e>] ?
dentry_free+0x4e/0x90
Oct 12 21:48:55 zippy kernel: [3546600.958021] [<ffffffff81226d4e>] ?
dput+0x1ee/0x220
Oct 12 21:48:55 zippy kernel: [3546600.958027] [<ffffffff81230614>] ?
mntput+0x24/0x40
Oct 12 21:48:55 zippy kernel: [3546600.958031] [<ffffffff812112f0>] ?
__fput+0x190/0x220
Oct 12 21:48:55 zippy kernel: [3546600.958036] [<ffffffff8171bed1>]
__sys_sendmsg+0x51/0x90
Oct 12 21:48:55 zippy kernel: [3546600.958041] [<ffffffff8171bf22>]
SyS_sendmsg+0x12/0x20
Oct 12 21:48:55 zippy kernel: [3546600.958049] [<ffffffff818431f2>]
entry_SYSCALL_64_fastpath+0x16/0x71
Oct 12 21:48:55 zippy kernel: [3546600.958077] ---[ end trace
d45f6f07a89c801f ]---
Also added to wireless-info.txt for better legibility.
I'm not sure if this is the right forum to post this.
If it isn't, a pointer to the right place would be appreciated.
Please include me in the reply as i'm not on the list.
Let me know, what additional details i need to provide, as i'm
interested in getting this to work.
Thanks.
Regards
Mario
On 16.10.2017 05:37, James Cameron wrote:
> On Sun, Oct 15, 2017 at 06:21:36PM +0200, Mario Theodoridis wrote:
>> Thanks for the pointers, James.
>>
>> On 12.10.2017 23:24, James Cameron wrote:
>>> There's a good chance this problem has been fixed already. You
>>> are using a v4.4 kernel with many patches applied by Ubuntu. Here, we
>>> are more concerned with the latest kernels, and v4.4 is quite old.
>>>
>>> Please test some of the later kernels, see
>>> https://wiki.ubuntu.com/Kernel/MainlineBuilds
>>>
>>> In particular, test v4.13 or v4.14-rc4.
>>
>> I'm having a hard time with that, because the virtualbox-dkms build fails
>> with the 4.13 kernel, and virtualbox unfortunately is essential.
>
> Is virtualbox essential for reproducing the problem, or essential for
> your general use?
It is essential for general use, like Internet connectivity.
> If the former, then that's interesting.
>
> If the latter, then you might instead test the v4.13 or v14-rc4
> kernels for only the problem, and then revert to an older kernel after
> testing.
>
> Either way, to use virtualbox-dkms with a later kernel you may be able
> to upgrade just the virtualbox packages from a later Ubuntu release.
>
> See https://packages.ubuntu.com/virtualbox-dkms and
> https://packages.ubuntu.com/virtualbox for the later versions available.
>
> Purpose of the test can be to help isolate the cause, not only to
> solve your problem.
Thanks for the info.
>
> [...]
> You might also try with later firmware package.
> See https://packages.ubuntu.com/linux-firmware
>
> You might also test with booting installation media in live-mode,
> ignoring the internal disk.
Ok, that was completely off the radar.
I ended up going the other way. I still had a 4.4.0-79-generic kernel
and booted that. It does not have this problem.
After checking out
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial
i tried to find the culprit but was not able to trace the back trace to
a potential null pointer or some such. I got stuck at
iwl_mvm_send_cmd_pdu_status not finding a reference to
iwl_mvm_disable_txq from there.
I did got the following diff though
git diff Ubuntu-4.4.0-79.100 Ubuntu-4.4.0-93.116 --
drivers/net/wireless/iwlwifi/ drivers/net/wireless/mac80211_hwsim.c >
wifi.patch
I don't know whether this came from upstream or was ubuntu sourced.
This fixed the issue for now, but now i'm stuck on that kernel :(
While i'm perfectly comfortable with user land C, i have no kernel
experience (clue stick links definitely welcome).
--
Mit freundlichen Grüßen/Best regards
Mario Theodoridis
On Sun, Oct 15, 2017 at 06:21:36PM +0200, Mario Theodoridis wrote:
> Thanks for the pointers, James.
>
> On 12.10.2017 23:24, James Cameron wrote:
> >There's a good chance this problem has been fixed already. You
> >are using a v4.4 kernel with many patches applied by Ubuntu. Here, we
> >are more concerned with the latest kernels, and v4.4 is quite old.
> >
> >Please test some of the later kernels, see
> >https://wiki.ubuntu.com/Kernel/MainlineBuilds
> >
> >In particular, test v4.13 or v4.14-rc4.
>
> I'm having a hard time with that, because the virtualbox-dkms build fails
> with the 4.13 kernel, and virtualbox unfortunately is essential.
Is virtualbox essential for reproducing the problem, or essential for
your general use?
If the former, then that's interesting.
If the latter, then you might instead test the v4.13 or v14-rc4
kernels for only the problem, and then revert to an older kernel after
testing.
Either way, to use virtualbox-dkms with a later kernel you may be able
to upgrade just the virtualbox packages from a later Ubuntu release.
See https://packages.ubuntu.com/virtualbox-dkms and
https://packages.ubuntu.com/virtualbox for the later versions available.
Purpose of the test can be to help isolate the cause, not only to
solve your problem.
> >If the problem still happens, capture the same information and send it
> >again as a reply.
> >
> >If the problem doesn't happen, then you can either continue to use the
> >new kernel, or find when the problem was fixed; a long but rewarding
> >process.
> >
> >Should the problem have been fixed for v4.10, you might also switch to
> >using the Ubuntu package linux-generic-hwe-16.04.
> >https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack#hwe-16.04
>
> The 4.10 kernel readily produced this one
>
> ------------[ cut here ]------------
> WARNING: CPU: 4 PID: 1617 at /build/linux-hwe-IJy1zi/linux-hwe-4.10.0/drivers/net/wireless/intel/iwlwifi/mvm/tx.c:510
> iwl_mvm_tx_skb_non_sta+0x39a/0x440 [iwlmvm]
> Modules linked in: bnep ccm pci_stub vboxpci(OE) vboxnetadp(OE)
> vboxnetflt(OE) vboxdrv(OE) nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp
> nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter
> ip_tables x_tables snd_hda_codec_hdmi arc4 iwlmvm mac80211
> snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal
> intel_powerclamp iwlwifi coretemp snd_hda_intel snd_hda_codec kvm_intel
> snd_hda_core snd_hwdep kvm input_leds irqbypass crct10dif_pclmul snd_pcm
> bridge crc32_pclmul joydev stp llc ghash_clmulni_intel snd_seq_midi pcbc
> snd_seq_midi_event snd_rawmidi aesni_intel snd_seq aes_x86_64 crypto_simd
> snd_seq_device glue_helper cfg80211 cryptd snd_timer intel_cstate snd
> intel_rapl_perf soundcore shpchp mei_me hci_uart mei btbcm btqca btintel
> bluetooth intel_lpss_acpi
> acpi_als mac_hid intel_lpss kfifo_buf tpm_infineon industrialio acpi_pad
> parport_pc ppdev lp parport autofs4 i915 e1000e i2c_algo_bit drm_kms_helper
> syscopyarea sysfillrect sysimgblt fb_sys_fops e100 hid_generic ptp i2c_hid
> ahci mii drm pps_core pinctrl_sunrisepoint libahci usbhid e1000 hid wmi
> video pinctrl_intel fjes
> CPU: 4 PID: 1617 Comm: hostapd Tainted: G OE 4.10.0-37-generic
> #41~16.04.1-Ubuntu
> Hardware name: Gigabyte Technology Co., Ltd. Z170M-D3H/Z170M-D3H-CF, BIOS
> F20 11/17/2016
> Call Trace:
> dump_stack+0x63/0x90
> __warn+0xcb/0xf0
> warn_slowpath_null+0x1d/0x20
> iwl_mvm_tx_skb_non_sta+0x39a/0x440 [iwlmvm]
> iwl_mvm_mac_tx+0x11e/0x1d0 [iwlmvm]
> ieee80211_tx_frags+0x14b/0x220 [mac80211]
> __ieee80211_tx+0x81/0x180 [mac80211]
> ieee80211_tx+0x10f/0x150 [mac80211]
> ieee80211_xmit+0x9b/0xf0 [mac80211]
> __ieee80211_tx_skb_tid_band+0x5c/0x70 [mac80211]
> ieee80211_mgmt_tx+0x42c/0x4a0 [mac80211]
> cfg80211_mlme_mgmt_tx+0xdc/0x310 [cfg80211]
> nl80211_tx_mgmt+0x212/0x360 [cfg80211]
> genl_family_rcv_msg+0x1db/0x3b0
> ? skb_queue_tail+0x43/0x50
> genl_rcv_msg+0x59/0xa0
> ? genl_notify+0x80/0x80
> netlink_rcv_skb+0xa4/0xc0
> genl_rcv+0x28/0x40
> netlink_unicast+0x18c/0x240
> netlink_sendmsg+0x2fb/0x3a0
> ? aa_sock_msg_perm+0x61/0x150
> sock_sendmsg+0x38/0x50
> ___sys_sendmsg+0x2c2/0x2d0
> ? sock_sendmsg+0x38/0x50
> ? SYSC_sendto+0x101/0x190
> ? __check_object_size+0x108/0x1e3
> ? _copy_to_user+0x55/0x60
> __sys_sendmsg+0x54/0x90
> SyS_sendmsg+0x12/0x20
> entry_SYSCALL_64_fastpath+0x1e/0xad
> RIP: 0033:0x7fcc38cfe450
> RSP: 002b:00007fffdefc9b18 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
> RAX: ffffffffffffffda RBX: 0000563e91285590 RCX: 00007fcc38cfe450
> RDX: 0000000000000000 RSI: 00007fffdefc9ba0 RDI: 0000000000000005
> RBP: 0000000000000000 R08: 0000000000000000 R09: 0000563e91283a70
> R10: 0000000000001000 R11: 0000000000000246 R12: 0000000000000000
> R13: 0000000000000009 R14: 0000000000000000 R15: 0000000000000000
>
> ---[ end trace 4d9a544d3976536e ]---
You might also try with later firmware package.
See https://packages.ubuntu.com/linux-firmware
You might also test with booting installation media in live-mode,
ignoring the internal disk.
--
James Cameron
http://quozl.netrek.org/
On Thu, Oct 12, 2017 at 10:26:33PM +0200, Mario Theodoridis wrote:
> Hello everyone,
>
> i'm running Kubuntu 16.04 as a Virtualbox VM host, and a wireless AP
> with an Intel Wireless 7260.
>
> My WLAN connections frequently keep dying, so that i need to
> disconnect and reconnect in order to use them again.
> My syslog is full of these:
>
> Oct 12 21:48:55 zippy kernel: [3546600.957321] ------------[ cut here
> ]------------
> Oct 12 21:48:55 zippy kernel: [3546600.957352] WARNING: CPU: 2 PID: 1571 at
> /build/linux-YyUNAI/linux-4.4.0/drivers/net/wireless/iwlwifi/mvm/utils.c:740
> iwl_mvm_disable_txq+0x2a6/0x2c0 [iwlmvm]()
> [...]
> I'm not sure if this is the right forum to post this.
> If it isn't, a pointer to the right place would be appreciated.
This is a right place. Another right place is Ubuntu bug reporting.
> Please include me in the reply as i'm not on the list.
> Let me know, what additional details i need to provide, as i'm
> interested in getting this to work.
There's a good chance this problem has been fixed already. You
are using a v4.4 kernel with many patches applied by Ubuntu. Here, we
are more concerned with the latest kernels, and v4.4 is quite old.
Please test some of the later kernels, see
https://wiki.ubuntu.com/Kernel/MainlineBuilds
In particular, test v4.13 or v4.14-rc4.
If the problem still happens, capture the same information and send it
again as a reply.
If the problem doesn't happen, then you can either continue to use the
new kernel, or find when the problem was fixed; a long but rewarding
process.
Should the problem have been fixed for v4.10, you might also switch to
using the Ubuntu package linux-generic-hwe-16.04.
https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack#hwe-16.04
Hope that helps.
> Thanks.
>
> Regards
>
> Mario
[...]
--
James Cameron
http://quozl.netrek.org/
Thanks for the pointers, James.
On 12.10.2017 23:24, James Cameron wrote:
> There's a good chance this problem has been fixed already. You
> are using a v4.4 kernel with many patches applied by Ubuntu. Here, we
> are more concerned with the latest kernels, and v4.4 is quite old.
>
> Please test some of the later kernels, see
> https://wiki.ubuntu.com/Kernel/MainlineBuilds
>
> In particular, test v4.13 or v4.14-rc4.
I'm having a hard time with that, because the virtualbox-dkms build
fails with the 4.13 kernel, and virtualbox unfortunately is essential.
>
> If the problem still happens, capture the same information and send it
> again as a reply.
>
> If the problem doesn't happen, then you can either continue to use the
> new kernel, or find when the problem was fixed; a long but rewarding
> process.
>
> Should the problem have been fixed for v4.10, you might also switch to
> using the Ubuntu package linux-generic-hwe-16.04.
> https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack#hwe-16.04
The 4.10 kernel readily produced this one
------------[ cut here ]------------
WARNING: CPU: 4 PID: 1617 at
/build/linux-hwe-IJy1zi/linux-hwe-4.10.0/drivers/net/wireless/intel/iwlwifi/mvm/tx.c:510
iwl_mvm_tx_skb_non_sta+0x39a/0x440 [iwlmvm]
Modules linked in: bnep ccm pci_stub vboxpci(OE) vboxnetadp(OE)
vboxnetflt(OE) vboxdrv(OE) nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack
iptable_filter ip_tables x_tables snd_hda_codec_hdmi arc4 iwlmvm
mac80211 snd_hda_codec_realtek snd_hda_codec_generic intel_rapl
x86_pkg_temp_thermal intel_powerclamp iwlwifi coretemp snd_hda_intel
snd_hda_codec kvm_intel snd_hda_core snd_hwdep kvm input_leds irqbypass
crct10dif_pclmul snd_pcm bridge crc32_pclmul joydev stp llc
ghash_clmulni_intel snd_seq_midi pcbc snd_seq_midi_event snd_rawmidi
aesni_intel snd_seq aes_x86_64 crypto_simd snd_seq_device glue_helper
cfg80211 cryptd snd_timer intel_cstate snd intel_rapl_perf soundcore
shpchp mei_me hci_uart mei btbcm btqca btintel bluetooth intel_lpss_acpi
acpi_als mac_hid intel_lpss kfifo_buf tpm_infineon industrialio
acpi_pad parport_pc ppdev lp parport autofs4 i915 e1000e i2c_algo_bit
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops e100
hid_generic ptp i2c_hid ahci mii drm pps_core pinctrl_sunrisepoint
libahci usbhid e1000 hid wmi video pinctrl_intel fjes
CPU: 4 PID: 1617 Comm: hostapd Tainted: G OE
4.10.0-37-generic #41~16.04.1-Ubuntu
Hardware name: Gigabyte Technology Co., Ltd. Z170M-D3H/Z170M-D3H-CF,
BIOS F20 11/17/2016
Call Trace:
dump_stack+0x63/0x90
__warn+0xcb/0xf0
warn_slowpath_null+0x1d/0x20
iwl_mvm_tx_skb_non_sta+0x39a/0x440 [iwlmvm]
iwl_mvm_mac_tx+0x11e/0x1d0 [iwlmvm]
ieee80211_tx_frags+0x14b/0x220 [mac80211]
__ieee80211_tx+0x81/0x180 [mac80211]
ieee80211_tx+0x10f/0x150 [mac80211]
ieee80211_xmit+0x9b/0xf0 [mac80211]
__ieee80211_tx_skb_tid_band+0x5c/0x70 [mac80211]
ieee80211_mgmt_tx+0x42c/0x4a0 [mac80211]
cfg80211_mlme_mgmt_tx+0xdc/0x310 [cfg80211]
nl80211_tx_mgmt+0x212/0x360 [cfg80211]
genl_family_rcv_msg+0x1db/0x3b0
? skb_queue_tail+0x43/0x50
genl_rcv_msg+0x59/0xa0
? genl_notify+0x80/0x80
netlink_rcv_skb+0xa4/0xc0
genl_rcv+0x28/0x40
netlink_unicast+0x18c/0x240
netlink_sendmsg+0x2fb/0x3a0
? aa_sock_msg_perm+0x61/0x150
sock_sendmsg+0x38/0x50
___sys_sendmsg+0x2c2/0x2d0
? sock_sendmsg+0x38/0x50
? SYSC_sendto+0x101/0x190
? __check_object_size+0x108/0x1e3
? _copy_to_user+0x55/0x60
__sys_sendmsg+0x54/0x90
SyS_sendmsg+0x12/0x20
entry_SYSCALL_64_fastpath+0x1e/0xad
RIP: 0033:0x7fcc38cfe450
RSP: 002b:00007fffdefc9b18 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000563e91285590 RCX: 00007fcc38cfe450
RDX: 0000000000000000 RSI: 00007fffdefc9ba0 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000563e91283a70
R10: 0000000000001000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000009 R14: 0000000000000000 R15: 0000000000000000
---[ end trace 4d9a544d3976536e ]---
--
Mit freundlichen Grüßen/Best regards
Mario Theodoridis
On Tue, Oct 17, 2017 at 09:35:39PM +0200, Mario Theodoridis wrote:
> On 16.10.2017 05:37, James Cameron wrote:
> >On Sun, Oct 15, 2017 at 06:21:36PM +0200, Mario Theodoridis wrote:
> >>Thanks for the pointers, James.
> >>
> >>On 12.10.2017 23:24, James Cameron wrote:
> >>>There's a good chance this problem has been fixed already. You
> >>>are using a v4.4 kernel with many patches applied by Ubuntu. Here, we
> >>>are more concerned with the latest kernels, and v4.4 is quite old.
> >>>
> >>>Please test some of the later kernels, see
> >>>https://wiki.ubuntu.com/Kernel/MainlineBuilds
> >>>
> >>>In particular, test v4.13 or v4.14-rc4.
> >>
> >>I'm having a hard time with that, because the virtualbox-dkms build fails
> >>with the 4.13 kernel, and virtualbox unfortunately is essential.
> >
> >Is virtualbox essential for reproducing the problem, or essential for
> >your general use?
>
> It is essential for general use, like Internet connectivity.
Okay, good, that means we can ignore virtualbox, and leave that to
you.
Please test v4.13 or v4.14-rc5, ignoring virtualbox for the time being.
> >If the former, then that's interesting.
> >
> >If the latter, then you might instead test the v4.13 or v14-rc4
> >kernels for only the problem, and then revert to an older kernel after
> >testing.
> >
> >Either way, to use virtualbox-dkms with a later kernel you may be able
> >to upgrade just the virtualbox packages from a later Ubuntu release.
> >
> >See https://packages.ubuntu.com/virtualbox-dkms and
> >https://packages.ubuntu.com/virtualbox for the later versions available.
> >
> >Purpose of the test can be to help isolate the cause, not only to
> >solve your problem.
>
> Thanks for the info.
>
> >
> >[...]
> >You might also try with later firmware package.
> >See https://packages.ubuntu.com/linux-firmware
> >
> >You might also test with booting installation media in live-mode,
> >ignoring the internal disk.
>
> Ok, that was completely off the radar.
Updating linux-firmware may run different firmware on the wireless
card, and the change in behaviour may fix the problem. A gamble.
A test with later installation media is useful, because you can verify
problems with different kernels and wireless firmware without change
to configuration. You might try Ubuntu 17.10 Artful ISO.
> I ended up going the other way. I still had a 4.4.0-79-generic kernel and
> booted that. It does not have this problem.
> After checking out
> git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial
> i tried to find the culprit but was not able to trace the back trace to a
> potential null pointer or some such. I got stuck at
> iwl_mvm_send_cmd_pdu_status not finding a reference to iwl_mvm_disable_txq
> from there.
>
> I did got the following diff though
>
> git diff Ubuntu-4.4.0-79.100 Ubuntu-4.4.0-93.116 --
> drivers/net/wireless/iwlwifi/ drivers/net/wireless/mac80211_hwsim.c >
> wifi.patch
>
> I don't know whether this came from upstream or was ubuntu sourced.
Upstream.
You found your problem was introduced in an Ubuntu kernel, in the
update from -79 to -93. This contained Ubuntu backports of two
stable kernel patches, which are also upstream patches;
8fbcfeb8a9cc ("mac80211_hwsim: Replace bogus hrtimer clockid")
from v4.4.69
50ea05efaf3b ("mac80211: pass block ack session timeout to to driver")
from v4.4.77
git log Ubuntu-4.4.0-79.100..Ubuntu-4.4.0-93.116 -- \
drivers/net/wireless/iwlwifi/ drivers/net/wireless/mac80211_hwsim.c
git remote add stable \
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
git fetch stable
git log v4.4.68..v4.4.92 -- \
drivers/net/wireless/iwlwifi/ drivers/net/wireless/mac80211_hwsim.c
> This fixed the issue for now, but now i'm stuck on that kernel :(
Yes.
Here in upstream, we would run the latest kernel v4.13 and work to
fix that. Trouble you had with virtualbox packages would be
eventually solvable, but aren't really a problem with the kernel
itself.
So your next step may be to report an Ubuntu bug, and say that -79
worked fine, and -93 did not.
> While i'm perfectly comfortable with user land C, i have no kernel
> experience (clue stick links definitely welcome).
You might verify the above patches caused the problem by doing a
bisection between -79 and -93.
https://wiki.ubuntu.com/Kernel/KernelBisection
Or by reverting only those patches.
Then report to Ubuntu which patch caused the problem.
> [...]
Hope that helps.
--
James Cameron
http://quozl.netrek.org/