Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 18 Feb 2021 17:19:54 +0000
To:     Willy Tarreau <w@1wt.eu>
From:   Jari Ruusu <jariruusu@protonmail.com>
Cc:     Jari Ruusu <jariruusu@users.sourceforge.net>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Scott Branden <scott.branden@broadcom.com>,
        Linux ARM <linux-arm-kernel@lists.infradead.org>,
        LKML <linux-kernel@vger.kernel.org>,
        BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>
Reply-To: Jari Ruusu <jariruusu@protonmail.com>
Subject: Re: 5.10 LTS Kernel: 2 or 6 years?
Message-ID: <dbLhDu5W6LMrWDRrgzNQJGLZPMWGkRtOcxFUbghT-Uuc8zmQObV5KjhYqVBo2U6k7r2rNVtVEaMjev_lyz8eNQGvksSTjVrHd8LaPrO_6Qs=@protonmail.com>
In-Reply-To: <20210218143341.GB13671@1wt.eu>
References: <ef30af4d-2081-305d-cd63-cb74da819a6d@broadcom.com> <YA/E1bHRmZb50MlS@kroah.com> <8cf503db-ac4c-a546-13c0-aac6da5c073b@broadcom.com> <YBBkplRxzzmPYKC+@kroah.com> <YCzknUTDytY8gRA8@kroah.com> <c731b65a-e118-9d37-79d1-d0face334fc4@broadcom.com> <YC4atKmK7ZqlOGER@kroah.com> <20210218113107.GA12547@1wt.eu> <602E766F.758C74D8@users.sourceforge.net> <20210218143341.GB13671@1wt.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Thursday, February 18, 2021 4:33 PM, Willy Tarreau <w@1wt.eu> wrote:
> Usually you pick an LTS kernel for a specific hardware. If it
> works that's great. But you cannot expect hardware to suddenly start to
> work in the middle of a stable kernel. Sometimes it happens (PCI IDs) but
> that's basically all and that's not their purpose.

It was the other way around. Fine working in-tree driver got
broken by backported "fixes". I did mention bit-rot.

In-tree iwlwifi worked half-ok on early 4.9.y stable. If
connection somehow de-autheticated (out of radio range or
whatever) it crashed the kernel spectacularly. Eventually that was
fixed and in-tree iwlwifi worked fine on 4.9.y and 4.14.y stable
kernels. On second half of year 2020 (don't remember exactly when)
iwlwifi started causing erratic behavior when some random process
terminated, as if some exit processing left some resources
un-freed or something weird like that. Upgraded to 4.19.y kernels
in hope to fix the issue. Nope, same problems continued there as
well. Replacing in-tree iwlwifi with out-of-tree upstream Intel
version solved the problem for me.

--
Jari Ruusu=C2=A0 4096R/8132F189 12D6 4C3A DCDA 0AA4 27BD=C2=A0 ACDF F073 3C=
80 8132 F189