Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #81264 > unrolled thread

Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected Diederik de Haas <didi.debian@cknow.org> - 2023-12-19 23:20 +0100
    Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected Thorsten Glaser <tg@mirbsd.de> - 2023-12-20 14:10 +0100
      Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected Diederik de Haas <didi.debian@cknow.org> - 2023-12-20 19:10 +0100
        Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected Thorsten Glaser <tg@mirbsd.de> - 2023-12-20 22:30 +0100
          Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected Diederik de Haas <didi.debian@cknow.org> - 2023-12-21 00:20 +0100

#81264 — Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo

On Sat, 21 Nov 2020 11:32:08 +0100 Thorsten Glaser <tg@mirbsd.de> wrote:
> Package: firmware-iwlwifi
> Version: 20200918-1
> Followup-For: Bug #934781
> X-Debbugs-Cc: tg@mirbsd.de
> 
> It still happens.
> 
> [583944.226966] iwl4965 0000:03:00.0: Microcode SW error detected.  Restarting 0x2000000.
> [583944.226974] iwl4965 0000:03:00.0: Loaded firmware version: 228.61.2.24
> [583944.226991] iwl4965 0000:03:00.0: Start IWL Error Log Dump:
> [583944.226996] iwl4965 0000:03:00.0: Status: 0x000213E4, count: 5
> [583944.227139] iwl4965 0000:03:00.0: Desc                                  Time       data1      data2      line
> [583944.227146] iwl4965 0000:03:00.0: NMI_INTERRUPT_WDG            (0x0004) 2382371429 0x00000002 0x02630000 208
> [583944.227150] iwl4965 0000:03:00.0: pc      blink1  blink2  ilink1  ilink2  hcmd
> [583944.227155] iwl4965 0000:03:00.0: 0x0046C 0x02156 0x004C2 0x006DA 0x005F2 0x41E0048
> [583944.227160] iwl4965 0000:03:00.0: FH register values:
> [583944.227176] iwl4965 0000:03:00.0:       FH49_RSCSR_CHNL0_STTS_WPTR_REG: 0X22aec200
> [583944.227192] iwl4965 0000:03:00.0:      FH49_RSCSR_CHNL0_RBDCB_BASE_REG: 0X022ae4d0
> [583944.227208] iwl4965 0000:03:00.0:                FH49_RSCSR_CHNL0_WPTR: 0X00000080
> [583944.227224] iwl4965 0000:03:00.0:       FH49_MEM_RCSR_CHNL0_CONFIG_REG: 0X80809000
> [583944.227239] iwl4965 0000:03:00.0:        FH49_MEM_RSSR_SHARED_CTRL_REG: 0X0000003c
> [583944.227255] iwl4965 0000:03:00.0:          FH49_MEM_RSSR_RX_STATUS_REG: 0X02630000
> [583944.227271] iwl4965 0000:03:00.0:   FH49_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
> [583944.227286] iwl4965 0000:03:00.0:              FH49_TSSR_TX_STATUS_REG: 0X07ff0002
> [583944.227302] iwl4965 0000:03:00.0:               FH49_TSSR_TX_ERROR_REG: 0X00000000
> [583944.228668] iwl4965 0000:03:00.0: Can't stop Rx DMA.
> [583944.228708] ieee80211 phy0: Hardware restart was requested
> 
> Kernel: Linux 5.9.0-2-amd64 (SMP w/2 CPU threads)

Is this issue still happening?
The firmware file iwlwifi-4965-2.ucode hasn't been updated since 2009-07-09,
but maybe/hopefully the kernel deals better with it now?

[toc] | [next] | [standalone]

#81280

Diederik de Haas dixit:

>Is this issue still happening?

Good question. The system currently suffers from fan error and
I don’t have the tuits to repair it, so I switched to a different
X61 Thinkpad, for now.

>The firmware file iwlwifi-4965-2.ucode hasn't been updated since 2009-07-09,
>but maybe/hopefully the kernel deals better with it now?

Perhaps. On this different Thinkpad, I’m running bullseye and
don’t get the messages. iwl-related dmesg entries:

[   39.470604] iwl4965: Intel(R) Wireless WiFi 4965 driver for Linux, in-tree:
[   39.484180] iwl4965: Copyright(c) 2003-2011 Intel Corporation
[   39.511132] iwl4965 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[   39.536450] iwl4965 0000:03:00.0: Detected Intel(R) Wireless WiFi Link 4965AGN, REV=0x4
[   39.606629] iwl4965 0000:03:00.0: device EEPROM VER=0x36, CALIB=0x5
[   39.620005] iwl4965 0000:03:00.0: Tunable channels: 13 802.11bg, 19 802.11a channels
[   39.701630] iwl4965 0000:03:00.0: firmware: direct-loading firmware iwlwifi-4965-2.ucode
[   39.715098] iwl4965 0000:03:00.0: loaded firmware version 228.61.2.24
[   39.729426] ieee80211 phy0: Selected rate control algorithm 'iwl-4965-rs'

bye,
//mirabilos
-- 
15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)

[toc] | [prev] | [next] | [standalone]

#81297

[Multipart message — attachments visible in raw view] — view raw

On Wednesday, 20 December 2023 14:02:57 CET Thorsten Glaser wrote:
> >The firmware file iwlwifi-4965-2.ucode hasn't been updated since
> >2009-07-09, but maybe/hopefully the kernel deals better with it now?
> 
> Perhaps. On this different Thinkpad, I’m running bullseye and
> don’t get the messages. iwl-related dmesg entries:

So it was present on 5.9.0-2 (5.9.6-1), but no longer on 5.10.X?

Do you want to keep the bug open for your other/original system?

[toc] | [prev] | [next] | [standalone]

#81301

Diederik de Haas dixit:

>So it was present on 5.9.0-2 (5.9.6-1), but no longer on 5.10.X?

Yes to the former, unsure to the latter.

>Do you want to keep the bug open for your other/original system?

If you’d rather not, I can keep a note on my TODO for when the
other system is back up, then reproduce and either unarchive or
let it rest, as I don’t have a timeframe for that.

bye,
//mirabilos
-- 
[16:04:33] bkix: "veni vidi violini"
[16:04:45] bkix: "ich kam, sah und vergeigte"...

[toc] | [prev] | [next] | [standalone]

#81302

[Multipart message — attachments visible in raw view] — view raw

On Wednesday, 20 December 2023 22:08:27 CET Thorsten Glaser wrote:
> >So it was present on 5.9.0-2 (5.9.6-1), but no longer on 5.10.X?
> 
> Yes to the former, unsure to the latter.
> 
> >Do you want to keep the bug open for your other/original system?

The latter question was based on it on the assumption that it was fixed on 
5.10.x, but as you're unsure, let's keep it open.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web