From: "Theodore Ts'o" <firstname.lastname@example.org> To: Greg Kroah-Hartman <email@example.com> Cc: Jari Ruusu <firstname.lastname@example.org>, Willy Tarreau <email@example.com>, Jari Ruusu <firstname.lastname@example.org>, Scott Branden <email@example.com>, Linux ARM <firstname.lastname@example.org>, LKML <email@example.com>, BCM Kernel Feedback <firstname.lastname@example.org> Subject: Re: 5.10 LTS Kernel: 2 or 6 years? Date: Fri, 19 Feb 2021 11:50:41 -0500 [thread overview] Message-ID: <YC/sYe2vyES0pYQC@mit.edu> (raw) In-Reply-To: <YC+d/NyXDebGSHwN@kroah.com> On Fri, Feb 19, 2021 at 12:16:12PM +0100, Greg Kroah-Hartman wrote: > > Great! Can you run 'git bisect' on the 4.14.y stable tree to find the > offending change? To be fair, especially with WiFi bugs, you may need to run for hours or days before you are absolutely sure that a particular bisection point will result in the the locking/kernel crash bug to manifest itself. Worse, you have to be actively using the Wifi in order to see the problem, and in some cases, it only triggers when you switch between AP's, so you have to be actively using it in the work office, and taking it between conference rooms, only to see your machine crash taking your unsaved work, email drafts, etc. with it. That being said, users should at least report the bug. (That's what I did, when I ran into this a bunch of years ago, with an explanation of "I'm trying to do a bisect, but it may take a few weeks for me to figure out what the !@#!? is going on. In my case, I was trying to use upstream -rcX kernels to dogfood on my work laptop, but the principle is the same.) Ultiumately, I solved the problem, by switching laptops to one that didn't use an NVidia GPU (which sometimes forced me to stay 1-2 upstream versions behind, making life even more difficult when debugging these issues, until the out-of-tree video driver got updated to work with newer upstream), and which also had WiFi hardware which was less subject to these issues. It's unfortunate, but not all hardware is as well supported on Linux. And in my case, because $WORK was using Enterprise WiFi systems with AP's that don't get as much testing by developers, very few other people could repro the bugs. That's life, and sometimes the only solution is to switch hardware. And/or you just use a Chromebook in those sorts of situations, separating your work/enterprise and upstream development hardware, and be done with it. :-) Cheers, - Ted
next prev parent reply other threads:[~2021-02-19 16:52 UTC|newest] Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-25 19:55 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-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 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 [this message] 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-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=YC/sYe2vyES0pYQC@mit.edu \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: 5.10 LTS Kernel: 2 or 6 years?' \ /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
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).