Created attachment 285081 [details] sample of the errors Since upgrading kernel to 5.3.0, my journal is *flooded* with errors, but wifi still works. A sample (many more appear, up to several k lines).
*** This bug has been marked as a duplicate of bug 204151 ***
Are you sure this is a duplicate? I did not get any errors in my journal before 5.3 kernel, e.g. with 5.2 series in arch linux.
Yes, we have exactly the same signature: Sep 21 18:42:18 ajax kernel: iwlwifi 0000:04:00.0: 0x00000038 | BAD_COMMAND [...] Sep 21 18:42:18 ajax kernel: iwlwifi 0000:04:00.0: FW error in SYNC CMD GEO_TX_POWER_LIMIT You were probably using something lower than v5.2.9, which is the version that got the buggy patch.
It looks like arch linux had Age Commit message (Expand) Author 3 days 5.3.1.arch1-1 heftig 8 days 5.3.arch1-1 heftig 12 days 5.2.14.arch2-1 heftig 14 days 5.2.14.arch1-1 heftig 2019-09-06 5.2.13.arch1-1 heftig 2019-08-29 5.2.11.arch1-1 heftig 2019-08-25 5.2.10.arch1-1 heftig 2019-08-16 5.2.9.arch1-1 but perhaps you are still right. On 9/24/19, bugzilla-daemon@bugzilla.kernel.org <bugzilla-daemon@bugzilla.kernel.org> wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204943 > > --- Comment #3 from Luca Coelho (luca@coelho.fi) --- > Yes, we have exactly the same signature: > > Sep 21 18:42:18 ajax kernel: iwlwifi 0000:04:00.0: 0x00000038 | BAD_COMMAND > > [...] > Sep 21 18:42:18 ajax kernel: iwlwifi 0000:04:00.0: FW error in SYNC CMD > GEO_TX_POWER_LIMIT > > You were probably using something lower than v5.2.9, which is the version > that > got the buggy patch. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug.
The best way to make sure is probably to take the patch I made and check if it now works for you. ;) https://patchwork.kernel.org/patch/11158395/