On Fri, May 5, 2023 at 2:39 PM WANG Xuerui <kernel@xxxxxxxxxx> wrote: > > On 5/6/23 02:00, Alex Deucher wrote: > > On Fri, May 5, 2023 at 1:57 PM WANG Xuerui <kernel@xxxxxxxxxx> wrote: > >> <snip> > >> On a side note, I had to modprobe amdgpu with runpm=0, otherwise my > >> dmesg gets flooded with PSP getting resumed every 8~10 seconds or so. I > >> currently have none of the connectors plugged in. I didn't notice any > >> similar reports on the Internet so I don't know if it's due to platform > >> quirks or not. > > That might just be part of the normal suspend/resume process. If it > > happens at regular intervals, it sounds like something is waking the > > GPU at a regular interval. We should probably remove that message to > > avoid it being too chatty, but you may want to check what is waking it > > so much as doing so sort of negates the value of runtime power > > management. > > Ah. This is extremely helpful as I'm immediately able to confirm it's > node_exporter trying to access the hwmon readings (I have a monitoring > infra for all my devboxes). Every sufficiently spaced read from say > temp1_input wakes up the GPU. Not many people have their boxes working > like this I guess... but at least we could probably reduce the log spam > a bit if it's not feasible to get GPU metrics while avoiding to resume > it? (Currently it's 25 lines per resume, mostly SMU resume logs and ring Well, there are no metrics to pull because the GPU is powered down when in runtime suspend. Alex > info.) > > And of course this is not a big deal, I can always work around it > locally. Thanks for the hint again. > > -- > WANG "xen0n" Xuerui > > Linux/LoongArch mailing list: https://lore.kernel.org/loongarch/ >
