Project

General

Profile

Bug #2313

Don't echo warnings about application clocks that are already at max

Added by Erik Lindahl about 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Affected version - extra info:
Affected version:
Difficulty:
simple
Close

Description

On threadripper-gpu02 with a GP100, I get this on stdout for all runs

"Cannot change application clocks for Quadro GP100 to optimal values due to insufficient permissions. Current values are (715,1556), max values are (715,1556).
Use sudo nvidia-smi -acp UNRESTRICTED or contact your admin to change application clocks."

For the case where the clocks are already running at max, I see no reason to echo warnings to stderr and tell users they should do anything.

Associated revisions

Revision 24452f95 (diff)
Added by Erik Lindahl about 2 years ago

Don't warn about NVML clocks that are at max

If the clocks are already maxed out there is no
point in echoing warnings about not being able
to set them.

Fixes #2313.

Change-Id: I77bc7111489166b580c2d7742a7729c003f25e9e

History

#1 Updated by Mark Abraham about 2 years ago

looks like Jiri's bf4589ee427e477b1923b2c691d3dcc211ba2fd2 didn't go far enough

#2 Updated by Gerrit Code Review Bot about 2 years ago

Gerrit received a related patchset '1' for Issue #2313.
Uploader: Erik Lindahl ()
Change-Id: gromacs~release-2018~I77bc7111489166b580c2d7742a7729c003f25e9e
Gerrit URL: https://gerrit.gromacs.org/7319

#3 Updated by Erik Lindahl about 2 years ago

  • Status changed from New to Fix uploaded

#4 Updated by Erik Lindahl about 2 years ago

  • Status changed from Fix uploaded to Resolved

#5 Updated by Erik Lindahl about 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF