On 24/09/2019 18:03, <email address hidden> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=204151
>
> --- Comment #16 from <email address hidden> ---
> 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:
> 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?
>
On 24/09/2019 18:03, <email address hidden> wrote: /bugzilla. kernel. org/show_ bug.cgi? id=204151
> https:/
>
> --- Comment #16 from <email address hidden> ---
> 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?
>