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
| ||
|
Message-ID: <79d4bf3e-fdc7-4273-aa1e-9b5e8194696b@intel.com> Date: Mon, 25 Dec 2023 10:03:23 +0200 From: Sasha Neftin <sasha.neftin@...el.com> To: Heiner Kallweit <hkallweit1@...il.com>, Marc MERLIN <marc@...lins.org> CC: Jakub Kicinski <kuba@...nel.org>, Johannes Berg <johannes@...solutions.net>, <netdev@...r.kernel.org>, "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>, Przemek Kitszel <przemyslaw.kitszel@...el.com> Subject: Re: [Intel-wired-lan] [PATCH net v3] net: ethtool: do runtime PM outside RTNL On 25/12/2023 1:12, Heiner Kallweit wrote: > On 24.12.2023 17:30, Marc MERLIN wrote: >> On Fri, Dec 15, 2023 at 09:46:34AM -0800, Marc MERLIN wrote: >>> On Fri, Dec 15, 2023 at 02:42:01PM +0100, Heiner Kallweit wrote: >>>> Why don't you simply disable runtime pm for the affected device as a >>>> workaround? This can be done via sysfs. >>> >>> 1) because I didn't know what the exact bug was and how to work around it :) >> >> Mmmh, so I need to test an ubuntu kernel (6.5.0-14) because of sound >> issues in mainline TOT, and I can't boot the kernel to completion >> without hititng this hang bug. I'm not exactly sure which part of the >> boot triggers it. >> >> I can't patch that kernel easily. How exactly do I disable runtime PM >> from the kernel command line for "that device" which I'm not even sure > > Change <device>/power/control from "auto" to "on". Need to figure out your controller location in a file system via lspci/lspci -t and then change to "on" For example: echo on > /sys/devices/pci0000\:00/0000\:00\:1c.0/0000\:ae\:00.0/power/control We are starting to look at this problem, but I can't reproduce the problem on my machines yet. > >> which one it is. If it's the eth device, I already removed the igc >> module to prevent it from loading, and I also removed the ethtool >> binary, but I'm still getting the hang. >> >> On the plus side, with 6.6.8 and the old patch which I understand is not >> the ideal solution, I can confirm that I've been running problem free >> until now, so thanks again for that interim patch. >> >> Thanks, >> Marc > > _______________________________________________ > Intel-wired-lan mailing list > Intel-wired-lan@...osl.org > https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
Powered by blists - more mailing lists