On Sun, Jun 7, 2015 at 5:53 PM, Emmanuel Grumbach <egrumb...@gmail.com> wrote: > On Sun, Jun 7, 2015 at 3:47 PM, Dominik Brodowski > <li...@dominikbrodowski.net> wrote: >> On Sun, May 31, 2015 at 12:37:19PM +0300, Emmanuel Grumbach wrote: >>> On Sun, May 31, 2015 at 9:52 AM, Dominik Brodowski >>> <li...@dominikbrodowski.net> wrote: >>> > On Sun, May 31, 2015 at 09:29:22AM +0300, Emmanuel Grumbach wrote: >>> >> > >>> >> > No joy. Firmware 25.27.13.0 also is not happy at times: >>> >> >>> >> Are you using 40Mhz or 20Mhz? >>> > >>> > Well, at the moment (and the problem appeared again just minutes ago): >>> > >>> > channel 1 (2412 MHz), width: 40 MHz, center1: 2422 MHz >>> > >>> >>> can you try to move to 20Mhz just to see if you still have the same problem? >>> You can load cfg80211 with cfg80211_disable_40mhz_24ghz set to true if >>> you don't want to play with the settings of your AP. >> >> On 20MHz, I do not see the queue issue, but the "Microcode SW error" >> persists: >> > > Please open a bug on bugzilla.kernel.org with the full dmesg output. > Mention what is the state of cfg80211_disable_40mhz_24ghz and CC > i...@linux.intel.com to the bug. > Please follow the instructions here: > https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging to > collect the fw_dump data. > I attached the firmware with debug enabled to this bug. > Take the time to read the privacy note here: > https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#privacy_aspects > > Thank you.
Let me spare a few more words. You had an initial problem: the queues were stuck. From my experience based on other bug reports, this can be worked around by limiting the bandwidth to 20Mhz on 2.4GHz. There is a known issue in this area. When the queues are stuck, the driver resets the firmware and hence you saw the firmware crash message in dmesg. You reduced the bandwidth to 20Mhz and you stopped seeing the stuck queue message. You have now a different issue: the firmware gets stuck: the watchdog interrupt fires. This is a typical firmware issue which needs to be debugged using firmware debugging tools. Thank you. > >> iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000. >> iwlwifi 0000:02:00.0: CSR values: >> iwlwifi 0000:02:00.0: (2nd byte of CSR_INT_COALESCING is >> CSR_INT_PERIODIC_REG) >> iwlwifi 0000:02:00.0: CSR_HW_IF_CONFIG_REG: 0X40489204 >> iwlwifi 0000:02:00.0: CSR_INT_COALESCING: 0X80000040 >> iwlwifi 0000:02:00.0: CSR_INT: 0X00000000 >> iwlwifi 0000:02:00.0: CSR_INT_MASK: 0X00000000 >> iwlwifi 0000:02:00.0: CSR_FH_INT_STATUS: 0X00000000 >> iwlwifi 0000:02:00.0: CSR_GPIO_IN: 0X00000000 >> iwlwifi 0000:02:00.0: CSR_RESET: 0X00000000 >> iwlwifi 0000:02:00.0: CSR_GP_CNTRL: 0X080403c5 >> iwlwifi 0000:02:00.0: CSR_HW_REV: 0X00000144 >> iwlwifi 0000:02:00.0: CSR_EEPROM_REG: 0X00000000 >> iwlwifi 0000:02:00.0: CSR_EEPROM_GP: 0X80000000 >> iwlwifi 0000:02:00.0: CSR_OTP_GP_REG: 0X803a0000 >> iwlwifi 0000:02:00.0: CSR_GIO_REG: 0X00080040 >> iwlwifi 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000000 >> iwlwifi 0000:02:00.0: CSR_GP_DRIVER_REG: 0X00000000 >> iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP1: 0X00000000 >> iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000 >> iwlwifi 0000:02:00.0: CSR_LED_REG: 0X00000060 >> iwlwifi 0000:02:00.0: CSR_DRAM_INT_TBL_REG: 0X88215528 >> iwlwifi 0000:02:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200 >> iwlwifi 0000:02:00.0: CSR_ANA_PLL_CFG: 0Xd55555d5 >> iwlwifi 0000:02:00.0: CSR_MONITOR_STATUS_REG: 0X3c08019d >> iwlwifi 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a >> iwlwifi 0000:02:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0010 >> iwlwifi 0000:02:00.0: FH register values: >> iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X2140f900 >> iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X02140f80 >> iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_WPTR: 0X00000048 >> iwlwifi 0000:02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00801114 >> iwlwifi 0000:02:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc >> iwlwifi 0000:02:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X02030000 >> iwlwifi 0000:02:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000 >> iwlwifi 0000:02:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001 >> iwlwifi 0000:02:00.0: FH_TSSR_TX_ERROR_REG: 0X00000000 >> iwlwifi 0000:02:00.0: Start IWL Error Log Dump: >> iwlwifi 0000:02:00.0: Status: 0x00000000, count: 6 >> iwlwifi 0000:02:00.0: Loaded firmware version: 25.27.13.0 >> iwlwifi 0000:02:00.0: 0x00000034 | NMI_INTERRUPT_WDG >> iwlwifi 0000:02:00.0: 0x000000E3 | uPc >> iwlwifi 0000:02:00.0: 0x00000000 | branchlink1 >> iwlwifi 0000:02:00.0: 0x00000B2E | branchlink2 >> iwlwifi 0000:02:00.0: 0x00016218 | interruptlink1 >> iwlwifi 0000:02:00.0: 0x000082F2 | interruptlink2 >> iwlwifi 0000:02:00.0: 0x00000000 | data1 >> iwlwifi 0000:02:00.0: 0x00000002 | data2 >> iwlwifi 0000:02:00.0: 0x02039842 | data3 >> iwlwifi 0000:02:00.0: 0xF300076B | beacon time >> iwlwifi 0000:02:00.0: 0x5DEB98B6 | tsf low >> iwlwifi 0000:02:00.0: 0x00000002 | tsf hi >> iwlwifi 0000:02:00.0: 0x00000000 | time gp1 >> iwlwifi 0000:02:00.0: 0x78E966A4 | time gp2 >> iwlwifi 0000:02:00.0: 0x00000000 | time gp3 >> iwlwifi 0000:02:00.0: 0x0004191B | uCode version >> iwlwifi 0000:02:00.0: 0x00000144 | hw version >> iwlwifi 0000:02:00.0: 0x40489204 | board version >> iwlwifi 0000:02:00.0: 0x0000001C | hcmd >> iwlwifi 0000:02:00.0: 0x26F63002 | isr0 >> iwlwifi 0000:02:00.0: 0x11806000 | isr1 >> iwlwifi 0000:02:00.0: 0x0000001A | isr2 >> iwlwifi 0000:02:00.0: 0x40417C82 | isr3 >> iwlwifi 0000:02:00.0: 0x00000000 | isr4 >> iwlwifi 0000:02:00.0: 0x10804112 | isr_pref >> iwlwifi 0000:02:00.0: 0x00000000 | wait_event >> iwlwifi 0000:02:00.0: 0x00004288 | l2p_control >> iwlwifi 0000:02:00.0: 0x00009C22 | l2p_duration >> iwlwifi 0000:02:00.0: 0x000003BF | l2p_mhvalid >> iwlwifi 0000:02:00.0: 0x000000E7 | l2p_addr_match >> iwlwifi 0000:02:00.0: 0x00000017 | lmpm_pmg_sel >> iwlwifi 0000:02:00.0: 0x21051936 | timestamp >> iwlwifi 0000:02:00.0: 0x1F844858 | flow_handler >> ieee80211 phy0: Hardware restart was requested >> >> Best, >> Dominik -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
