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 Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CBF48C4332F for ; Mon, 21 Nov 2022 16:50:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 6ECE181A58; Mon, 21 Nov 2022 16:50:33 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 6ECE181A58 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=osuosl.org; s=default; t=1669049433; bh=pyW7baHLIg7pn74gOYV07b12dEXpaORqzsD6TR4KK9E=; h=Date:From:To:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Cc:From; b=RzGERh7jhorAqUnoGqz+yaRGKMrUXSnSHjlHVtNtApEb6uMtzvGI24nlhiFDHcx/e xJZQxA3Uk7pLIc6vzprmRte/oMBn1GI0pg9Py3AG/CXUO08L4V2iyvhLnYjAEaIL/g e9gN3L6ks6YDz8a42H0CfxLvFd0IFkpQNopaDk4MWTeO4veLIDSb/353NMM9Kidohb 9UVB37vhnfkHS2iIYhEEyHNgKkY5hMzf+aZ5D64+RAcz4FqnyGjONp/NByx2c560GP piMwIVIFgfjLkTBgbC9JiqrresmCIvmrdBpdo2+zROzdpETlRUtS/LZkLJ4TU76s4F vWPwcfmOzURIA== X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HSTVdFPVxuB7; Mon, 21 Nov 2022 16:50:32 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp1.osuosl.org (Postfix) with ESMTP id 54FD381A92; Mon, 21 Nov 2022 16:50:32 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 54FD381A92 Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by ash.osuosl.org (Postfix) with ESMTP id 500871BF38A for ; Sun, 20 Nov 2022 18:40:30 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 2A4F260BF2 for ; Sun, 20 Nov 2022 18:40:30 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 2A4F260BF2 X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qQI_ngqjP54J for ; Sun, 20 Nov 2022 18:40:29 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org D692160BEF Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by smtp3.osuosl.org (Postfix) with ESMTPS id D692160BEF for ; Sun, 20 Nov 2022 18:40:28 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 92E4C60C7B; Sun, 20 Nov 2022 18:40:27 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 15309C433D6; Sun, 20 Nov 2022 18:40:24 +0000 (UTC) Date: Sun, 20 Nov 2022 18:40:22 +0000 From: Conor Dooley To: Thorsten Leemhuis Message-ID: References: <20221031170535.77be0eb5@kernel.org> <03f7dc73-3e7c-1e6d-275f-85539493cd7f@intel.com> <20221118145443.427ecf10@kernel.org> <8117aac8-947e-49ca-c2b1-ef45c2914975@leemhuis.info> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <8117aac8-947e-49ca-c2b1-ef45c2914975@leemhuis.info> X-Mailman-Approved-At: Mon, 21 Nov 2022 16:50:22 +0000 X-Mailman-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1668969627; bh=IL6rbRNqWxYXvYNDrx+68DN7TWq/FY/OdkWzWHkpV2s=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=J9ME5e+Lds3R1igTMhhQWGqWEHVIxE/Hn6VqHoOz9n06GoleaYryMSD4mkCGiSAJX QeDPdytlp+t5ivYYF+B0C++oOkeSZBCEbuvVF2MK8OSTvdSEaQy/SzjrHkwwpKMPZC H2ywU2bJSDhkdrvQaI5t+JumQFaAmk2uatCIa+rsq+QXkSHQznOGRAqXVS1n6n/Dt1 OjmCHi9Ol+aydv/BBcEwpMpSQ7XU6tLq0QX7AXuducHt6gELqOkImZ4bNpKolqTOTt DGsKJaiZuaqiNz8N4AoI+C/4ll2Y8EPZM/Da+alUd3fyWIzRJ/2YKx4i7pEpL5vtN8 EJnAVKZUYw3CQ== X-Mailman-Original-Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=J9ME5e+L Subject: Re: [Intel-wired-lan] igc kernel module crashes on new hardware (Intel Ethernet I225-V) X-BeenThere: intel-wired-lan@osuosl.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel Wired Ethernet Linux Kernel Driver Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "Fuxbrumer, Devora" , regressions@lists.linux.dev, intel-wired-lan@lists.osuosl.org, Ivan Smirnov , Jakub Kicinski , "Ruinskiy, Dima" , "Avivi, Amir" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: intel-wired-lan-bounces@osuosl.org Sender: "Intel-wired-lan" On Sun, Nov 20, 2022 at 11:32:36AM +0100, Thorsten Leemhuis wrote: > On 19.11.22 00:21, Conor Dooley wrote: > > On Fri, Nov 18, 2022 at 02:54:43PM -0800, Jakub Kicinski wrote: > >> On Fri, 18 Nov 2022 22:43:29 +0000 Conor Dooley wrote: > >>>> Is there any update for the community? More and more folks are asking. We > >>>> are all techies and happy to help debug. > >>> > >>> Vested interest since I am suffering from the same issue (X670E-F > >>> Gaming), but is it okay to add this to regzbot? Not sure whether it > >>> counts as a regression or not since it's new hw with the existing driver, > >>> but this seems to be falling through the cracks without a response for > >>> several weeks. > >> > >> Dunno, Thorsten's will decide. The line has to be drawn somewhere > >> on "vendor doesn't care about Linux support" vs "we broke uAPI". > >> This is the kind of situation I was alluding to in my line of > >> questioning at the maintainer summit: https://lwn.net/Articles/908324/ > > > > Yeah & it is /regression/ tracking which I don't (or rather didn't) > > consider this situation to be. > > Yeah, looks like this is not something that look track-worthy for > regzbot -- at least for now, maybe it one day makes sense to use and > improved regzbot for bug reports as well, but I'd like to focus on > establishing regression tracking properly first, which still requires a > lot of work. > > > I'm generally a little unsure as to when > > I should trigger regzbot in general: > > - immediately when I find something? > > Yes, ideally, as documented here: > https://docs.kernel.org/admin-guide/reporting-regressions.html > > > - only if it goes a while with nothing constructive? > > But that is fine as well. But FWIW, we all don't want bureaucracy. Even > I don't add each and every regression I see to the tracking yet. > > > - is it okay to use it outside of "this used to work and now doesnt"? > > Guess I should clarify that this is unwanted in above doc. Right. I wasn't sure if it was okay to use it for "this never worked" type of issues. Thanks Thorsten! _______________________________________________ Intel-wired-lan mailing list Intel-wired-lan@osuosl.org https://lists.osuosl.org/mailman/listinfo/intel-wired-lan