Re: [PATCH] iwlwifi: Don't IWL_WARN on FW reconfiguration

2020-07-13 Thread Johannes Hirte
On 2020 Jul 13, Chris Down wrote: > Just to check in again since this is still happening: is this expected? > > I expect that if this is IWL_WARN, it should indicate some unexpected or > non-ideal state, but the card seems to operate just fine afterwards. I'm confused too, cause I'm seeing this

Re: [PATCH] iwlwifi: Don't IWL_WARN on FW reconfiguration

2020-07-13 Thread Chris Down
Just to check in again since this is still happening: is this expected? I expect that if this is IWL_WARN, it should indicate some unexpected or non-ideal state, but the card seems to operate just fine afterwards.

Re: [PATCH] iwlwifi: Don't IWL_WARN on FW reconfiguration

2019-10-17 Thread Chris Down
To be more clear in case this actually is representative of a real problem (although I doubt it since this seems present on every device like this I encountered), it's always FW_DBG_START_FROM_ALIVE: % sudo journalctl _TRANSPORT=kernel -o cat | grep 'FW already configured' | sort | uniq -c

[PATCH] iwlwifi: Don't IWL_WARN on FW reconfiguration

2019-10-17 Thread Chris Down
IWL_WARN seems excessive here since this can happen during normal operation. Every time I connect to a new network with 8086:24fd I get this as KERN_WARNING on the console, which mildly distracts from other more pressing messages. For example: % sudo journalctl _TRANSPORT=kernel | grep -c 'FW