netdev - Re: [RFC PATCH] net: ethtool: do runtime PM outside RTNL

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20231204212849.GA25864@merlins.org>
Date: Mon, 4 Dec 2023 13:28:49 -0800
From: Marc MERLIN <marc@...lins.org>
To: Johannes Berg <johannes@...solutions.net>
Cc: netdev@...r.kernel.org, Jesse Brandeburg <jesse.brandeburg@...el.com>,
	Tony Nguyen <anthony.l.nguyen@...el.com>,
	intel-wired-lan@...ts.osuosl.org,
	Heiner Kallweit <hkallweit1@...il.com>
Subject: Re: [RFC PATCH] net: ethtool: do runtime PM outside RTNL

On Mon, Dec 04, 2023 at 12:54:39PM -0800, Marc MERLIN wrote:
> On Mon, Dec 04, 2023 at 09:40:08PM +0100, Johannes Berg wrote:
> > This one's still the problem, so I guess my 2-line hack didn't do
> > anything.
> 
> sorry, I wasn't clear, this was the last hang before your patch. I
> wanted to make sure it matched your analysis, which it seems to, so
> that's good.  I now understand that the order in printk is not actually
> the order of who is at fault.
> I'm testing your patch now, will let you know ASAP

Well. Good news. So far so good.

sauron:~# ethtool -i enp11s0
driver: igc
version: 6.6.4-amd64-volpre-sysrq-202312
firmware-version: 1073:8754
expansion-rom-version: 
bus-info: 0000:0b:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

sauron:~# iwconfig wlp9s0
wlp9s0    IEEE 802.11  ESSID:"magicnet"  
          Mode:Managed  Frequency:5.2 GHz  Access Point: E0:63:DA:28:03:67   
          Bit Rate=866.7 Mb/s   Tx-Power=22 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=-40 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:992   Missed beacon:0

sauron:~# lspci | grep -i net
09:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a)
0b:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-LM (rev 03)

It's unfortunate that nouveau doesn't seem to support the nvidia chip at all, not even
well enough to turn it off, but thankfully I can do this via
  echo 'auto' > '/sys/bus/pci/devices/0000:01:00.0/power/control'

For power, I was able to get it to idle at 13W with tlp powering down chips to slow
speeds, and the screen fairly dim. It's not great but it's cmoparable to the P73, so
close enough.

The weird PME loops I attached in the last Email would also butn batteries on my P73
without hanging it. Your patch may have fixed that too. If so, thank you
(will report if I see the PME stuff again).

Either way, I'm in much better shape right now on a laptop I was about
to return after having spent 3 days of effort on it, so a heartfelt thank you!

Where do you we go from here? Is the patch obviously good/safe, or do we
need to narrow things down/test some more?

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
 
Home page: http://marc.merlins.org/