From: Jari Ruusu <jariruusu@protonmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Jari Ruusu <jariruusu@users.sourceforge.net>,
Scott Branden <scott.branden@broadcom.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: 5.10 LTS Kernel: 2 or 6 years?
Date: Thu, 18 Feb 2021 17:19:54 +0000 [thread overview]
Message-ID: <dbLhDu5W6LMrWDRrgzNQJGLZPMWGkRtOcxFUbghT-Uuc8zmQObV5KjhYqVBo2U6k7r2rNVtVEaMjev_lyz8eNQGvksSTjVrHd8LaPrO_6Qs=@protonmail.com> (raw)
In-Reply-To: <20210218143341.GB13671@1wt.eu>
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 4096R/8132F189 12D6 4C3A DCDA 0AA4 27BD ACDF F073 3C80 8132 F189
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-18 17:21 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 19:55 5.10 LTS Kernel: 2 or 6 years? Scott Branden
2021-01-26 2:50 ` Adam Borowski
2021-01-26 7:29 ` Greg Kroah-Hartman
2021-01-26 17:35 ` Florian Fainelli
2021-01-26 18:30 ` Scott Branden
2021-01-26 18:51 ` Greg Kroah-Hartman
2021-01-26 20:15 ` Willy Tarreau
2021-01-29 10:00 ` 10 years -- was " Pavel Machek
2021-02-17 9:40 ` Greg Kroah-Hartman
2021-02-17 19:48 ` Scott Branden
2021-02-18 7:43 ` Greg Kroah-Hartman
2021-02-18 11:31 ` Willy Tarreau
2021-02-18 14:15 ` Jari Ruusu
2021-02-18 14:29 ` Greg Kroah-Hartman
2021-02-18 20:55 ` Pavel Machek
2021-02-18 22:43 ` Ondrej Zary
2021-02-19 8:00 ` Pavel Machek
2021-02-19 8:30 ` Greg Kroah-Hartman
2021-02-18 14:33 ` Willy Tarreau
2021-02-18 17:19 ` Jari Ruusu [this message]
2021-02-18 17:22 ` Russell King - ARM Linux admin
2021-02-18 17:44 ` Greg Kroah-Hartman
2021-02-19 7:10 ` Jari Ruusu
2021-02-19 8:22 ` Greg Kroah-Hartman
2021-02-19 10:31 ` Jari Ruusu
2021-02-19 10:37 ` Greg Kroah-Hartman
2021-02-19 10:57 ` Jari Ruusu
2021-02-19 11:16 ` Greg Kroah-Hartman
2021-02-19 15:23 ` Jari Ruusu
2021-02-20 13:29 ` Jari Ruusu
2021-02-20 16:05 ` Greg Kroah-Hartman
2021-02-20 17:06 ` Willy Tarreau
2021-02-21 11:38 ` Jari Ruusu
2021-02-19 16:50 ` Theodore Ts'o
2021-02-18 17:16 ` Florian Fainelli
2021-02-18 12:51 ` Pavel Machek
2021-02-18 16:51 ` Sasha Levin
2021-02-18 17:21 ` Florian Fainelli
2021-02-18 17:53 ` Greg Kroah-Hartman
2021-02-18 17:57 ` Florian Fainelli
2021-02-18 18:20 ` Willy Tarreau
2021-02-18 18:36 ` Greg Kroah-Hartman
2021-02-18 20:16 ` Scott Branden
2021-02-18 21:00 ` Willy Tarreau
2021-02-18 22:38 ` Scott Branden
2021-02-18 21:39 ` Sasha Levin
2021-02-18 22:00 ` Florian Fainelli
2021-02-18 22:26 ` Scott Branden
2021-02-19 8:25 ` Greg Kroah-Hartman
2021-02-19 15:05 ` Florian Fainelli
2021-02-19 15:53 ` Greg Kroah-Hartman
2021-02-19 17:44 ` Florian Fainelli
2021-02-22 14:17 ` Greg Kroah-Hartman
2021-02-18 17:42 ` Florian Fainelli
2021-02-18 18:13 ` Willy Tarreau
2021-02-18 10:04 ` Pavel Machek
2021-01-29 9:49 ` Pavel Machek
2021-02-19 8:54 ` Hanjun Guo
2021-02-19 9:08 ` Greg Kroah-Hartman
2021-02-20 7:02 ` Hanjun Guo
2021-02-20 9:53 ` Greg Kroah-Hartman
2021-02-23 2:14 ` Hanjun Guo
2021-02-19 14:45 ` Nikolai Kondrashov
2021-02-26 8:03 ` Hanjun Guo
2021-02-26 11:21 ` Nikolai Kondrashov
2021-02-22 14:00 ` Nishanth Aravamudan
2021-02-22 14:24 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='dbLhDu5W6LMrWDRrgzNQJGLZPMWGkRtOcxFUbghT-Uuc8zmQObV5KjhYqVBo2U6k7r2rNVtVEaMjev_lyz8eNQGvksSTjVrHd8LaPrO_6Qs=@protonmail.com' \
--to=jariruusu@protonmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=jariruusu@users.sourceforge.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.branden@broadcom.com \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).