From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fout-a1-smtp.messagingengine.com (fout-a1-smtp.messagingengine.com [103.168.172.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 075162E8DFF; Wed, 18 Jun 2025 13:28:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=103.168.172.144 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750253337; cv=none; b=Uwny/7i7zJdGJdSjBleQiChl/vl/f9r6IvKwW6ml8YbI+OAwnQCWXKLTWsaKuIoaRoLYW29PcMKFWS6vBokBPTyVFxBkGuZysA98nLMmhjRD3bbfc2jAYDrZH2tR4HFzZvm/dyW+7UyWVv18TCHXO7K47by008TRlQrW5bXBw6I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750253337; c=relaxed/simple; bh=4pvL2pRMcn6SX0QoJ4lt3Ga1uPDK5VKhU4BGa8uBuGU=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=q+i5mV/7HVXkfxXYpJpudpG72hRI9IVBhP9xXLyykNUd51EXQ+ESJHu7V+DMn7VuCaLlIZbzHLkr4q6oec5sCwtNxVub1P0luciF7CuCULPdppKpzwY2Eb5oA+Nd+QUu1vm7CO4Y4qRznfKE8o6UJ5mpnYMqw+mlJaQab/wtnFs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=invisiblethingslab.com; spf=pass smtp.mailfrom=invisiblethingslab.com; dkim=pass (2048-bit key) header.d=invisiblethingslab.com header.i=@invisiblethingslab.com header.b=WIAuXkm9; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b=Sd9kZIkw; arc=none smtp.client-ip=103.168.172.144 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=invisiblethingslab.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=invisiblethingslab.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=invisiblethingslab.com header.i=@invisiblethingslab.com header.b="WIAuXkm9"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="Sd9kZIkw" Received: from phl-compute-05.internal (phl-compute-05.phl.internal [10.202.2.45]) by mailfout.phl.internal (Postfix) with ESMTP id 3C3EE13803E5; Wed, 18 Jun 2025 09:28:55 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-05.internal (MEProxy); Wed, 18 Jun 2025 09:28:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= invisiblethingslab.com; h=cc:cc:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1750253335; x=1750339735; bh=vz/7ulDQUN+PP0dM9GXUeJUIxa3j77kggycAnGY4Aws=; b= WIAuXkm9l14HnRsq+a1xjXC9OQMw0cStyCOO0VyO1kntZf+QvA1RXHQEE+5D336a +FH+YijbW8zZS4F7C21Au630CUB27tUWo6QmQw3SCr+JZkxqDfYnwUfTNTTjU7q/ xIBAdGnSip0Rk3i45TIkQQHJtcXhpvFC1fUriosNzfqBUCsJSOze5nWFNaaH0bG1 iynaonWX6LxjIw6b7rqiYbop6VSdrXc+8xjE+ihWLE6I1i/4QBP+lOMJ+qhyL3KP N4/jMjnRSkRDk3+Fs0CcW5yfE3tFCsbeVi3/daCSVd3pCiDv1mk4FzHjDhBDnJnw MqFsPf/TGHsKjbzMC/nvRQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1750253335; x=1750339735; bh=vz/7ulDQUN+PP0dM9GXUeJUIxa3j77kggyc AnGY4Aws=; b=Sd9kZIkwjLSpU63LKWOqonj0DhUPRtv3KFnyftCDFFHhMhRnB5C YSpZKF/nvENe/HtM43I9NLi+UBlL8n7vidU1rxwSqyMNFUaqHKGDLlnP2RWxDTFV VXUXxOzsNXTkpzIrniCXy8LIbPGL1LHLoVKwn7dB91bN1dCAac7iiRrEvqemVZdv eREyXRdZS68rstll5G3p037yKeR6UfDVzddhhJnzL1pci2jbO4PcvAHcTE67SPZJ tUORupVgtDItOelNRBA/8QAE/mgrCxjFbQXvVWE7gS5IL3HvgXGDwG2YJIyi4Yj7 j346176r/cBIF7229PSGdtskqQpK7TO7lQQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtddvgddvjeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnh htshculddquddttddmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreertddtjeen ucfhrhhomhepofgrrhgvkhcuofgrrhgtiiihkhhofihskhhiqdfikphrvggtkhhiuceomh grrhhmrghrvghksehinhhvihhsihgslhgvthhhihhnghhslhgrsgdrtghomheqnecuggft rfgrthhtvghrnhepgfduleetfeevhfefheeiteeliefhjefhleduveetteekveettddvge euteefjedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhho mhepmhgrrhhmrghrvghksehinhhvihhsihgslhgvthhhihhnghhslhgrsgdrtghomhdpnh gspghrtghpthhtohepledpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepphhmvghn iigvlhesmhholhhgvghnrdhmphhgrdguvgdprhgtphhtthhopehvihhtrghlhidrlhhifh hshhhithhssehinhhtvghlrdgtohhmpdhrtghpthhtoheprghnthhhohhnhidrlhdrnhhg uhihvghnsehinhhtvghlrdgtohhmpdhrtghpthhtohepphhriigvmhihshhlrgifrdhkih htshiivghlsehinhhtvghlrdgtohhmpdhrtghpthhtohepnhgvthguvghvsehvghgvrhdr khgvrhhnvghlrdhorhhgpdhrtghpthhtohepihhnthgvlhdqfihirhgvugdqlhgrnheslh hishhtshdrohhsuhhoshhlrdhorhhgpdhrtghpthhtoheprhgvghhrvghsshhiohhnshes lhhishhtshdrlhhinhhugidruggvvhdprhgtphhtthhopehsthgrsghlvgesvhhgvghrrd hkvghrnhgvlhdrohhrghdprhgtphhtthhopehsrghshhgrlheskhgvrhhnvghlrdhorhhg X-ME-Proxy: Feedback-ID: i1568416f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 18 Jun 2025 09:28:53 -0400 (EDT) Date: Wed, 18 Jun 2025 15:28:51 +0200 From: Marek =?utf-8?Q?Marczykowski-G=C3=B3recki?= To: Paul Menzel Cc: Vitaly Lifshits , Tony Nguyen , Przemek Kitszel , netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org, regressions@lists.linux.dev, stable@vger.kernel.org, Sasha Levin Subject: Re: [Intel-wired-lan] [REGRESSION] e1000e heavy packet loss on Meteor Lake - 6.14.2 Message-ID: References: Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="iUL4KGRviabJX8Lu" Content-Disposition: inline In-Reply-To: --iUL4KGRviabJX8Lu Content-Type: text/plain; protected-headers=v1; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Date: Wed, 18 Jun 2025 15:28:51 +0200 From: Marek =?utf-8?Q?Marczykowski-G=C3=B3recki?= To: Paul Menzel Cc: Vitaly Lifshits , Tony Nguyen , Przemek Kitszel , netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org, regressions@lists.linux.dev, stable@vger.kernel.org, Sasha Levin Subject: Re: [Intel-wired-lan] [REGRESSION] e1000e heavy packet loss on Meteor Lake - 6.14.2 On Fri, May 09, 2025 at 02:17:32AM +0200, Marek Marczykowski-G=C3=B3recki w= rote: > On Fri, May 09, 2025 at 01:28:36AM +0200, Marek Marczykowski-G=C3=B3recki= wrote: > > On Fri, May 09, 2025 at 01:13:28AM +0200, Paul Menzel wrote: > > > Dear Marek, dear Vitaly, > > >=20 > > >=20 > > > Am 09.05.25 um 00:41 schrieb Marek Marczykowski-G=C3=B3recki: > > > > On Thu, May 08, 2025 at 09:26:18AM +0300, Lifshits, Vitaly > > > > > On 4/21/2025 4:28 PM, Marek Marczykowski-G=C3=B3recki wrote: > > > > > > On Mon, Apr 21, 2025 at 03:19:12PM +0200, Marek Marczykowski-G= =C3=B3recki wrote: > > > > > > > On Mon, Apr 21, 2025 at 03:44:02PM +0300, Lifshits, Vitaly wr= ote: > > > > > > > >=20 > > > > > > > >=20 > > > > > > > > On 4/16/2025 3:43 PM, Marek Marczykowski-G=C3=B3recki wrote: > > > > > > > > > On Wed, Apr 16, 2025 at 03:09:39PM +0300, Lifshits, Vital= y wrote: > > > > > > > > > > Can you please also share the output of ethtool -i? I w= ould like to know the > > > > > > > > > > NVM version that you have on your device. > > > > > > > > >=20 > > > > > > > > > driver: e1000e > > > > > > > > > version: 6.14.1+ > > > > > > > > > firmware-version: 1.1-4 > > > > > > > > > expansion-rom-version: > > > > > > > > > bus-info: 0000:00:1f.6 > > > > > > > > > supports-statistics: yes > > > > > > > > > supports-test: yes > > > > > > > > > supports-eeprom-access: yes > > > > > > > > > supports-register-dump: yes > > > > > > > > > supports-priv-flags: yes > > > > > > > > >=20 > > > > > > > >=20 > > > > > > > > Your firmware version is not the latest, can you check with= the board > > > > > > > > manufacturer if there is a BIOS update to your system? > > > > > > >=20 > > > > > > > I can check, but still, it's a regression in the Linux driver= - old > > > > > > > kernel did work perfectly well on this hw. Maybe new driver t= ries to use > > > > > > > some feature that is missing (or broken) in the old firmware? > > > > > >=20 > > > > > > A little bit of context: I'm maintaining the kernel package for= a Qubes > > > > > > OS distribution. While I can try to update firmware on my test = system, I > > > > > > have no influence on what hardware users will use this kernel, = and > > > > > > which firmware version they will use (and whether all the vendo= rs > > > > > > provide newer firmware at all). I cannot ship a kernel that is = known > > > > > > to break network on some devices. > > > > > >=20 > > > > > > > > Also, you mentioned that on another system this issue doesn= 't reproduce, do > > > > > > > > they have the same firmware version? > > > > > > >=20 > > > > > > > The other one has also 1.1-4 firmware. And I re-checked, e100= 0e from > > > > > > > 6.14.2 works fine there. > > >=20 > > > > > Thank you for your detailed feedback and for providing the reques= ted > > > > > information. > > > > >=20 > > > > > We have conducted extensive testing of this patch across multiple= systems > > > > > and have not observed any packet loss issues. Upon comparing the = mentioned > > > > > setups, we noted that while the LAN controller is similar, the CP= U differs. > > > > > We believe that the issue may be related to transitions in the CP= U's low > > > > > power states. > > > > >=20 > > > > > Consequently, we kindly request that you disable the CPU low powe= r state > > > > > transitions in the S0 system state and verify if the issue persis= ts. You can > > > > > disable this in the kernel parameters on the command line with id= le=3Dpoll. > > > > > Please note that this command is intended for debugging purposes = only, as it > > > > > may result in higher power consumption. > > > >=20 > > > > I tried with idle=3Dpoll, and it didn't help, I still see a lot of = packet > > > > losses. But I can also confirm that idle=3Dpoll makes the system use > > > > significantly more power (previously at 25-30W, with this option st= ays > > > > at about 42W). > > > >=20 > > > > Is there any other info I can provide, enable some debug features or > > > > something? > > > >=20 > > > > I see the problem is with receiving packets - in my simple ping tes= t, > > > > the ping target sees all the echo requests (and respond to them), b= ut > > > > the responses aren't reaching ping back (and are not visible on tcp= dump > > > > on the problematic system either). > > >=20 > > > As the cause is still unclear, can the commit please be reverted in t= he > > > master branch due adhere to Linux=E2=80=99 no-regression policy, so t= hat it can be > > > reverted from the stable series? > > >=20 > > > Marek, did you also test 6.15 release candidates? > >=20 > > The last test I did was on 6.15-rc3. I can re-test on -rc5. >=20 > Same with 6.15-rc5. And the same issue still applies to 6.16-rc2. FWIW Qubes OS kernel has this buggy patch revered and nobody complained (contrary to the version with the patch included). Should I submit the revert patch? --=20 Best Regards, Marek Marczykowski-G=C3=B3recki Invisible Things Lab --iUL4KGRviabJX8Lu Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmhSvxMACgkQ24/THMrX 1yyXAQf+K53U8Y6jWL6iyqumhg77CPbzn0qaQrxtA2sKrbY+GBzdBG3ptbzs1bY0 T5YlBl9fiGCHMqAO1H/BgQnbHY7oRk2jMgR10m52fMWE0pnsHPcHxVi2ChLvrpfx UdYSbRHZpEDwVZNfQkAI0ppKGF/It+BtIjD9xWeLqOiezEr6GmT2Z1uvBywbwq4m AbK3ZFzvSHIEUyVQZMXopcGwsAzJWL19/zPJOLLXDIMhUy9mKvpNR7/MjivwuuT4 Y0oy6tAuqGLJv3m0oIIByL7lAc/2oq0TizFTqOGnvGMJYALdXiA2QpKNZSc2MT8t NUXAGDW3WOntp2X+TvgJW4+pfqn8Rw== =MhTN -----END PGP SIGNATURE----- --iUL4KGRviabJX8Lu--