On 24/10/17 23:01, James Cameron wrote:
Summary: WARN_ON(iwl_mvm_is_dqa_supported(mvm)) in
iwl_mvm_rx_tx_cmd_single with v4.13, but code is since changed.
On Tue, Oct 24, 2017 at 09:56:31PM +0200, Mario Theodoridis wrote:
Sorry for skipping the list one the last one.
Sorry, that was my fault. It was a private message you replied to.
On 19.10.2017 22:59, James Cameron wrote:
[...]
You didn't say virtualbox was essential for reproducing the problem,
so I'm continuing to exclude it from thought. If it is essential for
reproducing, then you might contact them.
Please do make sure you can exclude virtualbox as a cause.
Let me clarify the virtualbox thing. The machine in question is a VM
host. It hosts several machines, one of which is my mail server, and
another (openbsd) which acts as a gateway to the internet for all machines.
If i run this machine without virtualbox, then my entire network
topology is off-line. While one could argue, that this is bad design,
the alternative would be to use openbsd as a virtual host, but i haven't
seen many tutorials on that. I also would like to run just one machine
24/7 to keep a tap on the electricity consumption.
This machine also bridges several interfaces and acts as a hotspot for
my wlan.
So i don't know whether virtualbox is responsible, but not running
virtualbox is simply not an option.
This one pretty quickly loads my syslog with new error stacks. I
haven't tested actual behavior yet, but the logs don't look so hot.
Do connections frequently keep dying as before?
I ran another wireless-info (attached) and appended some of the
syslog stuff to it.
Thanks, you identified a line of code and cause; a WARN_ON in
iwl_mvm_rx_tx_cmd_single;
case TX_STATUS_FAIL_DEST_PS:
/* In DQA, the FW should have stopped the queue and not
* return this status
*/
WARN_ON(iwl_mvm_is_dqa_supported(mvm));
info->flags |= IEEE80211_TX_STAT_TX_FILTERED;
break;
But it is only a warning. If connections aren't dying, it may not be
important to you.
Please check you are using the most recent linux-firmware?
I'm running
ii linux-firmware 1.169 all
from artful.
No difference to the xenial version.
Several methods, though by far the most common seems to be personal
experience with offsets.
When you don't have that personal experience, the methods are;
1. using GDB against the .o file,
2. using binutils objdump to disassemble .o file or vmlinuz,
3. using GCC to generate assembly listings,
See https://wiki.ubuntu.com/Kernel/KernelDebuggingTricks right down
the end of page for the GDB method.
I have gotten around to that part, yet, as i was busy with the
above, but it seems later versions have issues, too.
However, you're still testing old source code.
Several changes made since are worth testing, please either
cherry-pick the patches or test a 4.14 rc kernel, and without
involving dkms or virtualbox.
Then i'd have to patch those files so they build for 4.14 first.
I've seen patches, but still need to figure out how to get them applied
in the build process.
--
Mit freundlichen Grüßen/Best Regards
Mario Theodoridis
