From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D2DFBC433DB for ; Thu, 18 Feb 2021 17:46:29 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 554D864EAF for ; Thu, 18 Feb 2021 17:46:29 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 554D864EAF Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=oogYLwSOeBaNIV4TgC8bp2kwPbBpegBpA9PPvhTwzME=; b=gORbfBlB+hkSpzsom5RubVpGM xZRwS/TJQLmkDnScfu9ROLO82vi496/Mu7hnkNHEwESUpWCMkJ+2akbFhl+csYi9AYiRpRPIx/BPC eZUmsh6lxq2K6CMZdmKZZZ8EkakpPBMryMY6SRJwP+qWGGZjMsQsA0ud9WgVx9yQqcAs6IuDWHFCr Wm1w+kBWOcdbjZkxAicEK5kIRXF5x/Qw4rmun3YKF83ksuuPL+rVXRq7lJdXKdg3R4/BpJ+1dpqn7 U/FK96Jsn6KH4GgbJZIhMsoBr4pQR/3nJuTNIYEkz2lAtSwGQCsMfd918J8C0t2/Li/c3/yAcGBmZ WNKAEWOyA==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1lCnLX-0001pJ-8z; Thu, 18 Feb 2021 17:44:11 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1lCnLV-0001og-4t for linux-arm-kernel@lists.infradead.org; Thu, 18 Feb 2021 17:44:10 +0000 Received: by mail.kernel.org (Postfix) with ESMTPSA id 23FDE64E3E; Thu, 18 Feb 2021 17:44:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1613670247; bh=dN5Lz8Nkhcc+7OtiNpQTs1HcBWR9lBrcFyuDejV+psY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pfRPveNc8xRM3n0ukIEnd+ripXxdzndk5VzdXkYpOa836nxXkxoxNvuo/dStwBIvO xsBxpmiihK+RdWVilZS3Vn2G1i3j1uNHOMTctUysu01t18gb3cd5lhlCn0BFn9XUq/ cENt4RkhlZV7eJsEwz6bPg7mnPXwGubuzJgH2Xw0= Date: Thu, 18 Feb 2021 18:44:04 +0100 From: Greg Kroah-Hartman To: Jari Ruusu Subject: Re: 5.10 LTS Kernel: 2 or 6 years? Message-ID: References: <8cf503db-ac4c-a546-13c0-aac6da5c073b@broadcom.com> <20210218113107.GA12547@1wt.eu> <602E766F.758C74D8@users.sourceforge.net> <20210218143341.GB13671@1wt.eu> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210218_124409_310321_0B2A3873 X-CRM114-Status: GOOD ( 14.58 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Jari Ruusu , Scott Branden , LKML , BCM Kernel Feedback , Willy Tarreau , Linux ARM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Feb 18, 2021 at 05:19:54PM +0000, Jari Ruusu wrote: > On Thursday, February 18, 2021 4:33 PM, Willy Tarreau 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. It did? Please let us stable maintainers know about, we will always gladly revert problems patches. What commits caused the problem? > 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. So something in the 4.9.y and 4.14.y stable kernels caused a regression, can you please do 'git bisect' to let us know what broke? And if 4.19.0 was always broken, why didn't you report that as well? How about 5.11, have you tried that? If not, please do so and report it to the developers, otherwise how can it ever get fixed? thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel