From nobody Mon Sep 23 12:42:47 2024 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XC2hf08X7z52DhR for ; Mon, 23 Sep 2024 12:42:58 +0000 (UTC) (envelope-from mail@eseipi.net) Received: from out-170.mta1.migadu.com (out-170.mta1.migadu.com [95.215.58.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XC2hc5y47z4vd0 for ; Mon, 23 Sep 2024 12:42:56 +0000 (UTC) (envelope-from mail@eseipi.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=eseipi.net header.s=key1 header.b=AqKW3LNO; dmarc=pass (policy=quarantine) header.from=eseipi.net; spf=pass (mx1.freebsd.org: domain of mail@eseipi.net designates 95.215.58.170 as permitted sender) smtp.mailfrom=mail@eseipi.net Date: Mon, 23 Sep 2024 12:42:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eseipi.net; s=key1; t=1727095374; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Pi3i2660lCIWf3gsWSrhQJnvf21jlC5kzf0ohoXeICg=; b=AqKW3LNOru+sVMeOs1DDbKHr61R6hmsXQwfD/7weF6i5k+pnjy1zTG+l215Lw461hVHmDh ps9Gw3ZFGQZ9uPXEZBFIg/qtJOkykO8mYX9PrhpC1/zr8Frq/v4dZajsjCwlbpgfOPqwhl BXwGnkQaAvBXSKdUBk5J51TaYJ5ozVFPjgMGglxVb0NfHEtmu+3BgfT++FC5RDgVZ2oCCm aOiAjcUiWDblxwN9q3xq8Lo1aM8K2JGB6QxJAkhJrKCgey5ZKf7Xdmwv+RcnKJFMLCxslH 7SFx3Oud6AinICWmBy//1zsjVvlsA8Cm8N1voBxULq7g6DdwEcaGnqe48BoasA== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Alexey Sukhoguzov To: freebsd-hackers@freebsd.org Subject: Re: nvme(4): some non-operational power states are broken Message-ID: References: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT X-Spamd-Result: default: False [-4.10 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[eseipi.net,quarantine]; R_DKIM_ALLOW(-0.20)[eseipi.net:s=key1]; R_SPF_ALLOW(-0.20)[+ip4:95.215.58.0/24]; RCVD_IN_DNSWL_LOW(-0.10)[95.215.58.170:from]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:202172, ipnet:95.215.58.0/24, country:CH]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[eseipi.net:+] X-Rspamd-Queue-Id: 4XC2hc5y47z4vd0 X-Spamd-Bar: ---- On Mon, Sep 23, 2024 at 11:10:15AM +0100, Warner Losh wrote: > Does Linux have active power state management? I didn't know there was such a thing, thanks! I tried to boot with 'pcie_aspm=off' kernel parameter and dmesg said that ASPM was disabled, but I didn't see any difference in terms of temperature or /sys/class/power_supply/BAT0/power_now value, they all are within normal boundaries. > And what's the workload? This machine is my workstation, so I would say there is almost no workload in terms of IO. > What performance are you seeing? I have no other issues with the device, except for power consumption in states 4 and 5. After enabling APST (I patched the kernel for this) and limiting idle transitions to state 3 this problem was mostly resolved as well, but I think it would still be worth finding out what is actually going on. > And what's the reported model number? What form factor? Model number is KXG5AZNV256G, form factor is M.2 2280. If necessary, I can send Identify command output. > We used these at work years ago, but in only one hw spin. For production machines idle power consumption may not be relevant at all, but for a laptop it's a huge difference. And that's a good news if it's just my faulty device and no one else is having the same problem. No additional work is needed then, which is always great :)