Launchpad has imported 27 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=204151.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2019-07-12T21:36:20+00:00 sharvil.nanavati wrote: Created attachment 283657 Relevant dmesg output Running Ubuntu 18.04 LTS with stock kernel (4.15.0-54-generic). Firmware failure with stock firmware from linux-firmware package (version 29.1044073957.0) and firmware supplied by Emmanuel (29.4009927039.0). Takes about 1 day of uptime for the first firmware crash. After that, firmware restarts are fairly common (2-3 per day). Throughput drops by 3-4x after first firmware restart and never recovers. No specific repro steps; simply remain connected to a 5GHz WPA2 Personal network with occasional network activity. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/0 ------------------------------------------------------------------------ On 2019-07-22T06:05:23+00:00 jethro.rose wrote: I have also been seeing this sort of behaviour since about April/May with Fedora 30 and various kernel versions. Seems to be load-dependent - it will be fine for a while but do anything "strenous" network wise (like, say download distribution updates) and it seems more likely to happen. Sometimes after less than an hour. ifconfig down/up gets the network back. I thought it was kernel related but as far as i can determine it is wireless firmware related, as rolling back to a previous fedora package (that was dated prior to May 14th on the fedora side) seems to revert the issue. But my testing has been limited as every time i update the box it seems to break again. If anyone has some suggestions for diagnostics I'm willing to assist. similar systemd journal output from my box also attached. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/1 ------------------------------------------------------------------------ On 2019-07-22T06:06:21+00:00 jethro.rose wrote: Created attachment 283893 systemd journal output, same issue, fedora 30 on asrock taichi x470 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/2 ------------------------------------------------------------------------ On 2019-07-23T02:21:28+00:00 jethro.rose wrote: To confirm, this started happening for me in May, with kernel version 5.0.17 (as far as i can determine) onwards. So it isn't just with kernel 4.x, and as above i do not believe it to be kernel specific, rather wireless firmware specific due to firmware rollback resolving the issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/3 ------------------------------------------------------------------------ On 2019-08-20T11:42:14+00:00 luca wrote: There seems to be an issue with the new FW where it doesn't flag support for the new command version, but uses it anyway. The crash is caused by the driver sending a command in the wrong (i.e. old) format. I'll fix this and send a patch/new FW version in a bit. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/4 ------------------------------------------------------------------------ On 2019-08-20T12:17:24+00:00 luca wrote: *** Bug 204213 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/5 ------------------------------------------------------------------------ On 2019-08-22T05:35:42+00:00 luca wrote: *** Bug 204153 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/6 ------------------------------------------------------------------------ On 2019-08-30T19:42:41+00:00 noonetinone wrote: Created attachment 284709 dmesg output from iwlwifi 3168 I'm getting strange kernel output with Intel(R) Dual Band Wireless AC 3168, REV=0x220. It amounts to just garbage backtrace. For me, it only happens with the 5.3 release candidates. Everything is good with linux stable tree. I've updated the firmware but no dice. Am I missing a kernel config option? A bios setting perhaps? I've got a Asrock x370 taichi mother board. Attached is some output from dmesg and lspci. The first 10 lines were pruned. Around line 180 is the output from lspci. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/7 ------------------------------------------------------------------------ On 2019-09-07T07:43:17+00:00 chris2553 wrote: Created attachment 284873 FW crash messages extracted from kernel log. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/8 ------------------------------------------------------------------------ On 2019-09-07T07:44:12+00:00 chris2553 wrote: Is the patch/new FW mentioned in comment 4 above available yet, please? I'm still seeing this FW crash in 5.3.0-rc7+. I'm using the latest firmware in the linux-firmware git tree (iwlwifi 0000:02:00.0: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm) in the hiope that this is the FW referred to in the comment. Relevant messages from kernel log is attached. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/9 ------------------------------------------------------------------------ On 2019-09-07T18:17:43+00:00 bugzilla wrote: I'm still seeing it every boot and wake from suspend with 5.3.0-rc7 as well, on an 8260 controller. [ 9.866194] flap.local kernel: iwlwifi 0000:6c:00.0: Microcode SW error detected. Restarting 0x2000000. [ 9.866330] flap.local kernel: iwlwifi 0000:6c:00.0: Start IWL Error Log Dump: [ 9.866331] flap.local kernel: iwlwifi 0000:6c:00.0: Status: 0x00000080, count: 6 [ 9.866332] flap.local kernel: iwlwifi 0000:6c:00.0: Loaded firmware version: 36.77d01142.0 [ 9.866334] flap.local kernel: iwlwifi 0000:6c:00.0: 0x00000038 | BAD_COMMAND ... [ 9.867069] flap.local kernel: iwlwifi 0000:6c:00.0: FW error in SYNC CMD GEO_TX_POWER_LIMIT ... [ 9.867192] flap.local kernel: WARNING: CPU: 2 PID: 685 at drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1874 iwl_mvm_rx_umac_scan_complete_notif.cold+0xc> [ 9.867237] flap.local kernel: CPU: 2 PID: 685 Comm: kworker/2:5 Not tainted 5.3.0-0.rc7.git0.1.fc31.x86_64 #1 And kernel is then tainted 512. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/10 ------------------------------------------------------------------------ On 2019-09-20T04:32:14+00:00 ilya.lipnitskiy wrote: Still happens on 5.3.0 on an 8260 controller, any updates? kernel: iwlwifi 0000:02:00.0: loaded firmware version 36.77d01142.0 op_mode iwlmvm kernel: iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 kernel: iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x82000000. kernel: iwlwifi 0000:02:00.0: Loaded firmware version: 36.77d01142.0 kernel: iwlwifi 0000:02:00.0: FW error in SYNC CMD GEO_TX_POWER_LIMIT kernel: CPU: 2 PID: 71 Comm: kworker/2:1 Tainted: P OE 5.3.0-arch1-1-ARCH #1 kernel: Hardware name: HP HP ZBook 15 G3/80D5, BIOS N81 Ver. 01.41 07/16/2019 kernel: Workqueue: events iwl_mvm_async_handlers_wk [iwlmvm] kernel: Call Trace: kernel: dump_stack+0x5c/0x80 kernel: iwl_trans_pcie_send_hcmd+0x547/0x560 [iwlwifi] kernel: ? wait_woken+0x70/0x70 kernel: iwl_trans_send_cmd+0x59/0xb0 [iwlwifi] kernel: iwl_mvm_send_cmd+0x2e/0x80 [iwlmvm] kernel: iwl_mvm_get_sar_geo_profile+0x102/0x180 [iwlmvm] kernel: iwl_mvm_rx_chub_update_mcc+0x10b/0x1a0 [iwlmvm] kernel: iwl_mvm_async_handlers_wk+0xaa/0x140 [iwlmvm] kernel: process_one_work+0x1d1/0x3a0 kernel: worker_thread+0x4a/0x3d0 kernel: kthread+0xfb/0x130 kernel: ? process_one_work+0x3a0/0x3a0 kernel: ? kthread_park+0x80/0x80 kernel: ret_from_fork+0x35/0x40 kernel: iwlwifi 0000:02:00.0: Failed to get geographic profile info -5 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/11 ------------------------------------------------------------------------ On 2019-09-20T04:46:31+00:00 ilya.lipnitskiy wrote: Created attachment 285073 Crash on 5.3.0 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/12 ------------------------------------------------------------------------ On 2019-09-23T12:34:16+00:00 luca wrote: *** Bug 204917 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/13 ------------------------------------------------------------------------ On 2019-09-24T09:44:03+00:00 luca wrote: *** Bug 204943 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/14 ------------------------------------------------------------------------ On 2019-09-24T10:34:29+00:00 luca wrote: I have just sent a fix for this upstream: https://patchwork.kernel.org/patch/11158395/ It will hopefully be taken to v5.4 soon and from there to stable v5.3, v5.2 and v4.19. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/15 ------------------------------------------------------------------------ On 2019-09-24T17:03:24+00:00 sharvil.nanavati wrote: Looking at the original log I attached to this bug report, I see that the uCode major version for my device is 0x1D (29): [79300.452830] iwlwifi 0000:05:00.0: 0x0000001D | uCode version major The patch enables GEO_TX_POWER_LIMIT for uCode major version 36 which wouldn't affect my device. Maybe I misunderstood something about the nature of the issue / patch, but it seems that the original bug report I reported is different than what is being fixed here. If so, should I file another bug or should we reopen this bug? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/16 ------------------------------------------------------------------------ On 2019-09-24T17:29:35+00:00 bugzilla wrote: Awesome, thanks Luca! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/17 ------------------------------------------------------------------------ On 2019-09-24T17:30:54+00:00 chris2553 wrote: On 24/09/2019 18:03, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204151 > > --- Comment #16 from sharvil.nanav...@gmail.com --- > Looking at the original log I attached to this bug report, I see that the > uCode > major version for my device is 0x1D (29): > > [79300.452830] iwlwifi 0000:05:00.0: 0x0000001D | uCode version major > > The patch enables GEO_TX_POWER_LIMIT for uCode major version 36 which > wouldn't > affect my device. > Even with that patch applied, I'm still getting the crash too. Hardware and uCode version are shown in: [ 3.447509] iwlwifi 0000:02:00.0: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm [ 3.493018] iwlwifi 0000:02:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 > Maybe I misunderstood something about the nature of the issue / patch, but it > seems that the original bug report I reported is different than what is being > fixed here. If so, should I file another bug or should we reopen this bug? > Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/18 ------------------------------------------------------------------------ On 2019-09-24T17:52:50+00:00 luca wrote: (In reply to sharvil.nanavati from comment #16) > Looking at the original log I attached to this bug report, I see that the > uCode major version for my device is 0x1D (29): > > [79300.452830] iwlwifi 0000:05:00.0: 0x0000001D | uCode version major > > The patch enables GEO_TX_POWER_LIMIT for uCode major version 36 which > wouldn't affect my device. > > Maybe I misunderstood something about the nature of the issue / patch, but > it seems that the original bug report I reported is different than what is > being fixed here. If so, should I file another bug or should we reopen this > bug? The original bug you reported, the one that has this line in the logs: [79300.452799] iwlwifi 0000:05:00.0: 0x00000034 | NMI_INTERRUPT_WDG ...has been fix with commit 0c3d7282233c ("iwlwifi: Add support for SAR South Korea limitation") upstream (it's in v5.3). This back has also been backported to v5.2.10+. The new patch I posted here today is not relevant for the "NMI_INTERRUPT_WDG" case. Please make sure you are using v5.2.10 or above. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/19 ------------------------------------------------------------------------ On 2019-09-24T17:55:25+00:00 luca wrote: (In reply to Chris Clayton from comment #18) > Even with that patch applied, I'm still getting the crash too. Hardware and > uCode version are shown in: > > [ 3.447509] iwlwifi 0000:02:00.0: loaded firmware version 46.6bf1df06.0 > op_mode iwlmvm > [ 3.493018] iwlwifi 0000:02:00.0: Detected Intel(R) Wireless-AC 9260 > 160MHz, REV=0x324 With this device you are probably getting the NMI_INTERRUPT_WDG case. I can't see the kernel version you are using, but it probably doesn't have the fix. Can you please check and report? For the record, this is the patch upstream for the NMI_INTERRUPT_WDG case: https://patchwork.kernel.org/patch/11021735/ Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/20 ------------------------------------------------------------------------ On 2019-09-24T18:04:27+00:00 sharvil.nanavati wrote: Thanks for closing the loop on this, Luca. Much appreciated. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/21 ------------------------------------------------------------------------ On 2019-09-25T06:34:54+00:00 chris2553 wrote: (In reply to Luca Coelho from comment #20) > (In reply to Chris Clayton from comment #18) > > Even with that patch applied, I'm still getting the crash too. Hardware and > > uCode version are shown in: > > > > [ 3.447509] iwlwifi 0000:02:00.0: loaded firmware version 46.6bf1df06.0 > > op_mode iwlmvm > > [ 3.493018] iwlwifi 0000:02:00.0: Detected Intel(R) Wireless-AC 9260 > > 160MHz, REV=0x324 > > With this device you are probably getting the NMI_INTERRUPT_WDG case. I > can't see the kernel version you are using, but it probably doesn't have the > fix. Can you please check and report? > > For the record, this is the patch upstream for the NMI_INTERRUPT_WDG case: > > https://patchwork.kernel.org/patch/11021735/ I'm running 5.3.1 which already includes the patch you've pointed to. I can generate the Microcode SW error more or less at will by downloading a large file (e.g. the Fedora 30 .iso). I've just done that and I'll attach the output from dmesg in a moment. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/22 ------------------------------------------------------------------------ On 2019-09-25T06:35:58+00:00 chris2553 wrote: Created attachment 285165 dmesg showing Microcode SW error Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/23 ------------------------------------------------------------------------ On 2019-09-25T06:48:55+00:00 luca wrote: *** Bug 204983 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/24 ------------------------------------------------------------------------ On 2019-09-25T06:53:31+00:00 luca wrote: (In reply to Chris Clayton from comment #22) > I'm running 5.3.1 which already includes the patch you've pointed to. > > I can generate the Microcode SW error more or less at will by downloading a > large file (e.g. the Fedora 30 .iso). I've just done that and I'll attach > the output from dmesg in a moment. The error you are getting is a different one: [ 554.990533] iwlwifi 0000:02:00.0: 0x000022CE | ADVANCED_SYSASSERT In this case, the signature is SYSASSERT and 0x000022CE. Can you please file a separate report for it? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/25 ------------------------------------------------------------------------ On 2019-09-30T12:14:40+00:00 mcroce wrote: *** Bug 205035 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016/comments/26 ** Changed in: linux Status: Unknown => Fix Released ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846016 Title: iwlwifi regular scan timed out error sending statistics_cmd queue 0 is inactive To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
