Created attachment 279057 [details] dmesg log for Ubuntu 18.04 /4.18 Configuration: HW: NUC7i5DNH: with Wireless-AC 8265 SW tested (driver crash appears on all the tested versions below, logs attached): Ubuntu Server 16.04 LTS, kernel 4.14.13 Ubuntu 17 Kernel 4.14.35 FW 34.0.1 Ubuntu 18 Kernel 4.18, fw 36 AC 8265 is set to AP mode, external USB dongle – wifi access STA Sometimes iwlwifi driver generates an OOPS. A device reboot is needed to recover. Sometimes iwlwifi driver just crashes and restarts itself, creating ~2 second delay in all communications. Customer doesn't have a reliable way to reproduce either case. IPv6 has been disabled, as it is though to reduce problem frequency. Tested: Kernel 4.18 After installing this kernel , fw 36 did load by itself. This configuration crashed frequently, due to reasons beyond WiFi. Apparently this kernel is not intended to work well with Ubuntu 16.04 Upgrading to 18.04 /4.18 The errors seems to occur with this kernel as well. Attached a dmesg log (2018-10-12-Ubuntu18.04-Kernel-4.18.13-iwlwifi.txt) Various WiFi STA variations Customer attempted several WiFi module replacements for the STA connection to the dental office. i.e. the Intel module remains the local AP network. Customer reported that it does makes a difference . Crash frequency is dependent on the module. The one they had initially used seems to fair well relatively. Intel module as STA, external AP dongle Customer had switched the use of the Intel module to STA, and used an AP capable USB dongle as AP. The external AP worked fine, but the crash frequency of the iwlwifi went up.
We will look into it.
Created attachment 279071 [details] -36 firmware with debug enabled. There are two logs attached. * ASSERT 1007 which we will not handled since it has been happened with an old firmware (34.0.1). * TFD queue hang with the latest firmware. For the TFD queue hang, we need the customer to collect debug data with the firmware attached. Please see the instructions here: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#firmware_debugging We also need to record tracing as explained here: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#tracing The best would be to have the tracing and the firmware dump of the same run. Please note that we don't provide business level support, but rather community support which is a different engagement and commitment.
I forget to say that you should pay attention to the privacy note here: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#privacy_aspects before sending private data to us. Thank you.
Created attachment 279459 [details] fix
This bug is being handled over emails.