Comments (94)
KeithMyers
commented on August 28, 2024
Seems reasonable.
I think you cover Intel igpus also, correct? What about the upcoming discrete Intel Xe gpus. Tackle that whenever they arrive and you have actual real hardware out in the field to experiment with?
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
The project reads basic PCIe information for all installed GPUs. For Intel details, I will need to work with a user similar to what we did for NV. It may take a while to find a volunteer.
from gpu-utils.
KeithMyers
commented on August 28, 2024
Yes, I wonder if this new discrete Xe gpu is going to become lustable. Or ho-hum. Can't depend on the rumors or leaked benchmarks until the real gpu is in the hands of real testers.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
@csecht
Any concerns with the direction? Could require significant updates to the UsersGuide.
from gpu-utils.
csecht
commented on August 28, 2024
Sorry, I haven’t checked e-mail for a few days. I need to catch up on the developments. (Been trying to learn bash scripting; working on automated editing of app_config.xml to change gpu_usage in response to VRAM%.)
… On Jun 24, 2020, at 6:52 PM, Rick ***@***.***> wrote:
@csecht <https://github.com/csecht>
Any concerns with the direction? Could require significant updates to the UsersGuide.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALMVCQXQQKFYN63JM3AKKVTRYKGVXANCNFSM4OGEFXNA>.
from gpu-utils.
csecht
commented on August 28, 2024
A name change is needed no doubt. The new names are descriptive. Could shorter commands be used, like, gpu-ls, gpu-mon, etc.?
… On Jun 23, 2020, at 6:33 PM, Rick ***@***.***> wrote:
The latest development work on the utilities has been to add Nvidia read capabilities. Also, the utilities now leverage generic PCIe sensor reading to detect all GPUs in a system. As a result, it may be appropriate to change the name of the project for the next major release. I was considering a name that would be consistent with what could be used for the package on Debian and a package released on PyPI. I was considering a project name of rickslab-gpu-utils and executables with names like rlgpu-ls, rlgpu-mon, rlgpu-pac, and rlgpu-plot.
Let me know your thoughts or any other recomendations.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#88>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALMVCQQMKR7GBX7VQCSEBODRYE3TNANCNFSM4OGEFXNA>.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I was originally thinking avoiding a potential conflict with some other gpu utilities, but having the -xxx should avoid that. I will start development on a new branch named integration.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I have pushed the new integration branch. Still lots of work to do.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Sorry, I haven’t checked e-mail for a few days. I need to catch up on the developments. (Been trying to learn bash scripting; working on automated editing of app_config.xml to change gpu_usage in response to VRAM%.)
Sounds like a cool project! You should post a repository. Also, maybe consider Python. It is such a great language. I have been so motivated to get back into coding due to how great Python is. Lots of good tutorials on YouTube.
from gpu-utils.
csecht
commented on August 28, 2024
Thanks, good thought. Haha, I just ordered a book on Bash scripting; need to get one for Python now! (Any recommendations?)
I did a fair amount of perl scripting at work, back in the day, but my aging brain makes it all slow going these days.
I will start on updating the User Guide based on what is in readme.md.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I originally thought I needed to get a book to get started, as I did with PERL and C a long time ago, so I bought one and never used it. There is so much info out there you can just google anything. I started with some simple videos from TheNewBoston, Sentdex, CoreySchafer, and Socratica. Once you get a good start, then you can google about any question you have, but most answers come from stackoverflow. I suggest starting with a good IDE. I like PyCharm.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
@csecht
Not sure if you started UserGuide updates. If so, please request a pull when you are finished for the day. I have some time available to work on it later my day.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I made progress on the User Guide today and pushed my latest.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
@KeithMyers
Is there a man page for nvidia-smi? Should be able to detect with command:
man nvidia-smi
from gpu-utils.
KeithMyers
commented on August 28, 2024
Yes, there is.
nvidia-smi(1) NVIDIA nvidia-smi(1)
NAME
nvidia-smi - NVIDIA System Management Interface program
SYNOPSIS
nvidia-smi [OPTION1 [ARG1]] [OPTION2 [ARG2]] ...
DESCRIPTION
nvidia-smi (also NVSMI) provides monitoring and management capabilities
for each of NVIDIA's Tesla, Quadro, GRID and GeForce devices from Fermi
and higher architecture families. GeForce Titan series devices are sup‐
ported for most functions with very limited information provided for
the remainder of the Geforce brand. NVSMI is a cross platform tool
that supports all standard NVIDIA driver-supported Linux distros, as
well as 64bit versions of Windows starting with Windows Server 2008 R2.
Metrics can be consumed directly by users via stdout, or provided by
file via CSV and XML formats for scripting purposes.
Note that much of the functionality of NVSMI is provided by the under‐
lying NVML C-based library. See the NVIDIA developer website link be‐
low for more information about NVML. NVML-based python bindings are
also available.
The output of NVSMI is not guaranteed to be backwards compatible. How‐
ever, both NVML and the Python bindings are backwards compatible, and
should be the first choice when writing any tools that must be main‐
tained across NVIDIA driver releases.
NVML SDK: http://developer.nvidia.com/nvidia-management-library-nvml/
Python bindings: http://pypi.python.org/pypi/nvidia-ml-py/
OPTIONS
GENERAL OPTIONS
-h, --help
Print usage information and exit.
SUMMARY OPTIONS
-L, --list-gpus
List each of the NVIDIA GPUs in the system, along with their UUIDs.
-B, --list-blacklist-gpus
List each of the blacklisted NVIDIA GPUs in the system, along with
their UUIDs.
QUERY OPTIONS
-q, --query
Display GPU or Unit info. Displayed info includes all data listed in
the (GPU ATTRIBUTES) or (UNIT ATTRIBUTES) sections of this document.
Some devices and/or environments don't support all possible informa‐
tion. Any unsupported data is indicated by a "N/A" in the output. By
default information for all available GPUs or Units is displayed. Use
the -i option to restrict the output to a single GPU or Unit.
[plus optional]
-u, --unit
Display Unit data instead of GPU data. Unit data is only available for
NVIDIA S-class Tesla enclosures.
-i, --id=ID
Display data for a single specified GPU or Unit. The specified id may
be the GPU/Unit's 0-based index in the natural enumeration returned by
the driver, the GPU's board serial number, the GPU's UUID, or the GPU's
PCI bus ID (as domain:bus:device.function in hex). It is recommended
that users desiring consistency use either UUID or PCI bus ID, since
device enumeration ordering is not guaranteed to be consistent between
reboots and board serial number might be shared between multiple GPUs
on the same board.
-f FILE, --filename=FILE
Redirect query output to the specified file in place of the default
stdout. The specified file will be overwritten.
-x, --xml-format
Produce XML output in place of the default human-readable format. Both
GPU and Unit query outputs conform to corresponding DTDs. These are
available via the --dtd flag.
--dtd
Use with -x. Embed the DTD in the XML output.
--debug=FILE
Produces an encrypted debug log for use in submission of bugs back to
NVIDIA.
-d TYPE, --display=TYPE
Display only selected information: MEMORY, UTILIZATION, ECC, TEMPERA‐
TURE, POWER, CLOCK, COMPUTE, PIDS, PERFORMANCE, SUPPORTED_CLOCKS,
PAGE_RETIREMENT, ACCOUNTING, ENCODER_STATS. Flags can be combined with
comma e.g. "MEMORY,ECC". Sampling data with max, min and avg is also
returned for POWER, UTILIZATION and CLOCK display types. Doesn't work
with -u/--unit or -x/--xml-format flags.
-l SEC, --loop=SEC
Continuously report query data at the specified interval, rather than
the default of just once. The application will sleep in-between
queries. Note that on Linux ECC error or XID error events will print
out during the sleep period if the -x flag was not specified. Pressing
Ctrl+C at any time will abort the loop, which will otherwise run indef‐
initely. If no argument is specified for the -l form a default inter‐
val of 5 seconds is used.
SELECTIVE QUERY OPTIONS
Allows the caller to pass an explicit list of properties to query.
[one of]
--query-gpu=
Information about GPU. Pass comma separated list of properties you
want to query. e.g. --query-gpu=pci.bus_id,persistence_mode. Call
--help-query-gpu for more info.
--query-supported-clocks=
List of supported clocks. Call --help-query-supported-clocks for more
info.
--query-compute-apps=
List of currently active compute processes. Call --help-query-com‐
pute-apps for more info.
--query-accounted-apps=
List of accounted compute processes. Call --help-query-accounted-apps
for more info. This query is not supported on vGPU host.
--query-retired-pages=
List of GPU device memory pages that have been retired. Call
--help-query-retired-pages for more info.
[mandatory]
--format=
Comma separated list of format options:
• csv - comma separated values (MANDATORY)
• noheader - skip first line with column headers
• nounits - don't print units for numerical values
[plus any of]
-i, --id=ID
Display data for a single specified GPU. The specified id may be the
GPU's 0-based index in the natural enumeration returned by the driver,
the GPU's board serial number, the GPU's UUID, or the GPU's PCI bus ID
(as domain:bus:device.function in hex). It is recommended that users
desiring consistency use either UUID or PCI bus ID, since device enu‐
meration ordering is not guaranteed to be consistent between reboots
and board serial number might be shared between multiple GPUs on the
same board.
-f FILE, --filename=FILE
Redirect query output to the specified file in place of the default
stdout. The specified file will be overwritten.
-l SEC, --loop=SEC
Continuously report query data at the specified interval, rather than
the default of just once. The application will sleep in-between
queries. Note that on Linux ECC error or XID error events will print
out during the sleep period if the -x flag was not specified. Pressing
Ctrl+C at any time will abort the loop, which will otherwise run indef‐
initely. If no argument is specified for the -l form a default inter‐
val of 5 seconds is used.
-lms ms, --loop-ms=ms
Same as -l,--loop but in milliseconds.
DEVICE MODIFICATION OPTIONS
[any one of]
-pm, --persistence-mode=MODE
Set the persistence mode for the target GPUs. See the (GPU ATTRIBUTES)
section for a description of persistence mode. Requires root. Will
impact all GPUs unless a single GPU is specified using the -i argument.
The effect of this operation is immediate. However, it does not per‐
sist across reboots. After each reboot persistence mode will default
to "Disabled". Available on Linux only.
-e, --ecc-config=CONFIG
Set the ECC mode for the target GPUs. See the (GPU ATTRIBUTES) section
for a description of ECC mode. Requires root. Will impact all GPUs
unless a single GPU is specified using the -i argument. This setting
takes effect after the next reboot and is persistent.
-p, --reset-ecc-errors=TYPE
Reset the ECC error counters for the target GPUs. See the (GPU AT‐
TRIBUTES) section for a description of ECC error counter types. Avail‐
able arguments are 0|VOLATILE or 1|AGGREGATE. Requires root. Will im‐
pact all GPUs unless a single GPU is specified using the -i argument.
The effect of this operation is immediate.
-c, --compute-mode=MODE
Set the compute mode for the target GPUs. See the (GPU ATTRIBUTES)
section for a description of compute mode. Requires root. Will impact
all GPUs unless a single GPU is specified using the -i argument. The
effect of this operation is immediate. However, it does not persist
across reboots. After each reboot compute mode will reset to "DE‐
FAULT".
-dm TYPE, --driver-model=TYPE
-fdm TYPE, --force-driver-model=TYPE
Enable or disable TCC driver model. For Windows only. Requires admin‐
istrator privileges. -dm will fail if a display is attached, but -fdm
will force the driver model to change. Will impact all GPUs unless a
single GPU is specified using the -i argument. A reboot is required
for the change to take place. See Driver Model for more information on
Windows driver models.
--gom=MODE
Set GPU Operation Mode: 0/ALL_ON, 1/COMPUTE, 2/LOW_DP Supported on
GK110 M-class and X-class Tesla products from the Kepler family. Not
supported on Quadro and Tesla C-class products. LOW_DP and ALL_ON are
the only modes supported on GeForce Titan devices. Requires adminis‐
trator privileges. See GPU Operation Mode for more information about
GOM. GOM changes take effect after reboot. The reboot requirement
might be removed in the future. Compute only GOMs don't support WDDM
(Windows Display Driver Model)
-r, --gpu-reset
Trigger a reset of one or more GPUs. Can be used to clear GPU HW and
SW state in situations that would otherwise require a machine reboot.
Typically useful if a double bit ECC error has occurred. Optional -i
switch can be used to target one or more specific devices. Without
this option, all GPUs are reset. Requires root. There can't be any
applications using these devices (e.g. CUDA application, graphics ap‐
plication like X server, monitoring application like other instance of
nvidia-smi). There also can't be any compute applications running on
any other GPU in the system.
Any GPUs with NVLink connections to a GPU being reset must also be re‐
set in the same command. This can be done either by omitting the -i
switch, or using the -i switch to specify the GPUs to be reset. If the
-i option does not specify a complete set of NVLink GPUs to reset, this
command will issue an error identifying the additional GPUs that must
be included in the reset command.
GPU reset is not guaranteed to work in all cases. It is not recommended
for production environments at this time. In some situations there may
be HW components on the board that fail to revert back to an initial
state following the reset request. This is more likely to be seen on
Fermi-generation products vs. Kepler, and more likely to be seen if the
reset is being performed on a hung GPU.
Following a reset, it is recommended that the health of each reset GPU
be verified before further use. The nvidia-healthmon tool is a good
choice for this test. If any GPU is not healthy a complete reset
should be instigated by power cycling the node.
Visit http://developer.nvidia.com/gpu-deployment-kit to download the
GDK and nvidia-healthmon.
-lgc, --lock-gpu-clocks=MIN_GPU_CLOCK,MAX_GPU_CLOCK
Specifies <minGpuClock,maxGpuClock> clocks as a pair (e.g. 1500,1500)
that defines closest desired locked GPU clock speed in MHz. Input can
also use be a singular desired clock value (e.g. <GpuClockValue>).
Supported on Volta+. Requires root
-rgc, --reset-gpu-clocks
Resets the GPU clocks to the default value. Supported on Volta+. Re‐
quires root.
-ac, --applications-clocks=MEM_CLOCK,GRAPHICS_CLOCK
Specifies maximum <memory,graphics> clocks as a pair (e.g. 2000,800)
that defines GPU's speed while running applications on a GPU. Sup‐
ported on Maxwell-based GeForce and from the Kepler+ family in
Tesla/Quadro/Titan devices. Requires root unless restrictions are re‐
laxed with the -acp command..
-rac, --reset-applications-clocks
Resets the applications clocks to the default value. Supported on Max‐
well-based GeForce and from the Kepler+ family in Tesla/Quadro/Titan
devices. Requires root unless restrictions are relaxed with the -acp
command.
-acp, --applications-clocks-permission=MODE
Toggle whether applications clocks can be changed by all users or only
by root. Available arguments are 0|UNRESTRICTED, 1|RESTRICTED. Sup‐
ported on Maxwell-based GeForce and from the Kepler+ family in
Tesla/Quadro/Titan devices. Requires root.
-pl, --power-limit=POWER_LIMIT
Specifies maximum power limit in watts. Accepts integer and floating
point numbers. Only on supported devices from Kepler family. Requires
administrator privileges. Value needs to be between Min and Max Power
Limit as reported by nvidia-smi.
-cc, --cuda-clocks=MODE
Overrides or restores default CUDA clocks Available arguments are 0|RE‐
STORE_DEFAULT or 1|OVERRIDE.
-am, --accounting-mode=MODE
Enables or disables GPU Accounting. With GPU Accounting one can keep
track of usage of resources throughout lifespan of a single process.
Only on supported devices from Kepler family. Requires administrator
privileges. Available arguments are 0|DISABLED or 1|ENABLED.
-caa, --clear-accounted-apps
Clears all processes accounted so far. Only on supported devices from
Kepler family. Requires administrator privileges.
--auto-boost-default=MODE
Set the default auto boost policy to 0/DISABLED or 1/ENABLED, enforcing
the change only after the last boost client has exited. Only on cer‐
tain Tesla devices from the Kepler+ family and Maxwell-based GeForce
devices. Requires root.
--auto-boost-default-force=MODE
Set the default auto boost policy to 0/DISABLED or 1/ENABLED, enforcing
the change immediately. Only on certain Tesla devices from the Kepler+
family and Maxwell-based GeForce devices. Requires root.
--auto-boost-permission=MODE
Allow non-admin/root control over auto boost mode. Available arguments
are 0|UNRESTRICTED, 1|RESTRICTED. Only on certain Tesla devices from
the Kepler+ family and Maxwell-based GeForce devices. Requires root.
[plus optional]
-i, --id=ID
Modify a single specified GPU. The specified id may be the GPU/Unit's
0-based index in the natural enumeration returned by the driver, the
GPU's board serial number, the GPU's UUID, or the GPU's PCI bus ID (as
domain:bus:device.function in hex). It is recommended that users de‐
siring consistency use either UUID or PCI bus ID, since device enumera‐
tion ordering is not guaranteed to be consistent between reboots and
board serial number might be shared between multiple GPUs on the same
board.
UNIT MODIFICATION OPTIONS
-t, --toggle-led=STATE
Set the LED indicator state on the front and back of the unit to the
specified color. See the (UNIT ATTRIBUTES) section for a description
of the LED states. Allowed colors are 0|GREEN and 1|AMBER. Requires
root.
[plus optional]
-i, --id=ID
Modify a single specified Unit. The specified id is the Unit's 0-based
index in the natural enumeration returned by the driver.
SHOW DTD OPTIONS
--dtd
Display Device or Unit DTD.
[plus optional]
-f FILE, --filename=FILE
Redirect query output to the specified file in place of the default
stdout. The specified file will be overwritten.
-u, --unit
Display Unit DTD instead of device DTD.
stats
Display statistics information about the GPU. Use "nvidia-smi stats
-h" for more information. Linux only.
topo
Display topology information about the system. Use "nvidia-smi topo
-h" for more information. Linux only. Shows all GPUs NVML is able to
detect but CPU affinity information will only be shown for GPUs with
Kepler or newer architectures. Note: GPU enumeration is the same as
NVML.
drain
Display and modify the GPU drain states. Use "nvidia-smi drain -h" for
more information. Linux only.
nvlink
Display nvlink information. Use "nvidia-smi nvlink -h" for more infor‐
mation.
clocks
Query and control clocking behavior. Currently, this only pertains to
synchronized boost. Use "nvidia-smi clocks --help" for more informa‐
tion.
vgpu
Display information on GRID virtual GPUs. Use "nvidia-smi vgpu -h" for
more information.
RETURN VALUE
Return code reflects whether the operation succeeded or failed and what
was the reason of failure.
• Return code 0 - Success
• Return code 2 - A supplied argument or flag is invalid
• Return code 3 - The requested operation is not available on tar‐
get device
• Return code 4 - The current user does not have permission to ac‐
cess this device or perform this operation
• Return code 6 - A query to find an object was unsuccessful
• Return code 8 - A device's external power cables are not prop‐
erly attached
• Return code 9 - NVIDIA driver is not loaded
• Return code 10 - NVIDIA Kernel detected an interrupt issue with
a GPU
• Return code 12 - NVML Shared Library couldn't be found or loaded
• Return code 13 - Local version of NVML doesn't implement this
function
• Return code 14 - infoROM is corrupted
• Return code 15 - The GPU has fallen off the bus or has otherwise
become inaccessible
• Return code 255 - Other error or internal driver error occurred
GPU ATTRIBUTES
The following list describes all possible data returned by the -q de‐
vice query option. Unless otherwise noted all numerical results are
base 10 and unitless.
Timestamp
The current system timestamp at the time nvidia-smi was invoked. For‐
mat is "Day-of-week Month Day HH:MM:SS Year".
Driver Version
The version of the installed NVIDIA display driver. This is an al‐
phanumeric string.
Attached GPUs
The number of NVIDIA GPUs in the system.
Product Name
The official product name of the GPU. This is an alphanumeric string.
For all products.
Display Mode
A flag that indicates whether a physical display (e.g. monitor) is cur‐
rently connected to any of the GPU's connectors. "Enabled" indicates
an attached display. "Disabled" indicates otherwise.
Display Active
A flag that indicates whether a display is initialized on the GPU's
(e.g. memory is allocated on the device for display). Display can be
active even when no monitor is physically attached. "Enabled" indi‐
cates an active display. "Disabled" indicates otherwise.
Persistence Mode
A flag that indicates whether persistence mode is enabled for the GPU.
Value is either "Enabled" or "Disabled". When persistence mode is en‐
abled the NVIDIA driver remains loaded even when no active clients,
such as X11 or nvidia-smi, exist. This minimizes the driver load la‐
tency associated with running dependent apps, such as CUDA programs.
For all CUDA-capable products. Linux only.
Accounting Mode
A flag that indicates whether accounting mode is enabled for the GPU
Value is either When accounting is enabled statistics are calculated
for each compute process running on the GPU. Statistics can be queried
during the lifetime or after termination of the process. The execution
time of process is reported as 0 while the process is in running state
and updated to actual execution time after the process has terminated.
See --help-query-accounted-apps for more info.
Accounting Mode Buffer Size
Returns the size of the circular buffer that holds list of processes
that can be queried for accounting stats. This is the maximum number
of processes that accounting information will be stored for before in‐
formation about oldest processes will get overwritten by information
about new processes.
Driver Model
On Windows, the TCC and WDDM driver models are supported. The driver
model can be changed with the (-dm) or (-fdm) flags. The TCC driver
model is optimized for compute applications. I.E. kernel launch times
will be quicker with TCC. The WDDM driver model is designed for graph‐
ics applications and is not recommended for compute applications.
Linux does not support multiple driver models, and will always have the
value of "N/A".
Current The driver model currently in use. Always "N/A" on
Linux.
Pending The driver model that will be used on the next reboot.
Always "N/A" on Linux.
Serial Number
This number matches the serial number physically printed on each board.
It is a globally unique immutable alphanumeric value.
GPU UUID
This value is the globally unique immutable alphanumeric identifier of
the GPU. It does not correspond to any physical label on the board.
Minor Number
The minor number for the device is such that the Nvidia device node
file for each GPU will have the form /dev/nvidia[minor number]. Avail‐
able only on Linux platform.
VBIOS Version
The BIOS of the GPU board.
MultiGPU Board
Whether or not this GPU is part of a multiGPU board.
Board ID
The unique board ID assigned by the driver. If two or more GPUs have
the same board ID and the above "MultiGPU" field is true then the GPUs
are on the same board.
Inforom Version
Version numbers for each object in the GPU board's inforom storage.
The inforom is a small, persistent store of configuration and state
data for the GPU. All inforom version fields are numerical. It can be
useful to know these version numbers because some GPU features are only
available with inforoms of a certain version or higher.
If any of the fields below return Unknown Error additional Inforom ver‐
ification check is performed and appropriate warning message is dis‐
played.
Image Version Global version of the infoROM image. Image version just
like VBIOS version uniquely describes the exact version
of the infoROM flashed on the board in contrast to in‐
foROM object version which is only an indicator of sup‐
ported features.
OEM Object Version for the OEM configuration data.
ECC Object Version for the ECC recording data.
Power Object Version for the power management data.
GPU Operation Mode
GOM allows to reduce power usage and optimize GPU throughput by dis‐
abling GPU features.
Each GOM is designed to meet specific user needs.
In "All On" mode everything is enabled and running at full speed.
The "Compute" mode is designed for running only compute tasks. Graphics
operations are not allowed.
The "Low Double Precision" mode is designed for running graphics appli‐
cations that don't require high bandwidth double precision.
GOM can be changed with the (--gom) flag.
Supported on GK110 M-class and X-class Tesla products from the Kepler
family. Not supported on Quadro and Tesla C-class products. Low Dou‐
ble Precision and All On modes are the only modes available for sup‐
ported GeForce Titan products.
Current The GOM currently in use.
Pending The GOM that will be used on the next reboot.
PCI
Basic PCI info for the device. Some of this information may change
whenever cards are added/removed/moved in a system. For all products.
Bus PCI bus number, in hex
Device PCI device number, in hex
Domain PCI domain number, in hex
Device Id PCI vendor device id, in hex
Sub System Id PCI Sub System id, in hex
Bus Id PCI bus id as "domain:bus:device.function", in hex
GPU Link information
The PCIe link generation and bus width
Current The current link generation and width. These may be re‐
duced when the GPU is not in use.
Maximum The maximum link generation and width possible with this
GPU and system configuration. For example, if the GPU
supports a higher PCIe generation than the system sup‐
ports then this reports the system PCIe generation.
Bridge Chip
Information related to Bridge Chip on the device. The bridge chip
firmware is only present on certain boards and may display "N/A" for
some newer multiGPUs boards.
Type The type of bridge chip. Reported as N/A if doesn't ex‐
ist.
Firmware Version
The firmware version of the bridge chip. Reported as N/A
if doesn't exist.
Replays Since Reset
The number of PCIe replays since reset.
Replay Number Rollovers
The number of PCIe replay number rollovers since reset. A replay number
rollover occurs after 4 consecutive replays and results in retraining
the link.
Tx Throughput
The GPU-centric transmission throughput across the PCIe bus in MB/s
over the past 20ms. Only supported on Maxwell architectures and newer.
Rx Throughput
The GPU-centric receive throughput across the PCIe bus in MB/s over the
past 20ms. Only supported on Maxwell architectures and newer.
Fan Speed
The fan speed value is the percent of maximum speed that the device's
fan is currently intended to run at. It ranges from 0 to 100%. Note:
The reported speed is the intended fan speed. If the fan is physically
blocked and unable to spin, this output will not match the actual fan
speed. Many parts do not report fan speeds because they rely on cool‐
ing via fans in the surrounding enclosure. For all discrete products
with dedicated fans.
Performance State
The current performance state for the GPU. States range from P0 (maxi‐
mum performance) to P12 (minimum performance).
Clocks Throttle Reasons
Retrieves information about factors that are reducing the frequency of
clocks.
If all throttle reasons are returned as "Not Active" it means that
clocks are running as high as possible.
Idle Nothing is running on the GPU and the clocks are drop‐
ping to Idle state. This limiter may be removed in a
later release.
Application Clocks Setting
GPU clocks are limited by applications clocks setting.
E.g. can be changed using nvidia-smi --applica‐
tions-clocks=
SW Power Cap SW Power Scaling algorithm is reducing the clocks below
requested clocks because the GPU is consuming too much
power. E.g. SW power cap limit can be changed with
nvidia-smi --power-limit=
HW Slowdown HW Slowdown (reducing the core clocks by a factor of 2
or more) is engaged. HW Thermal Slowdown and HW Power
Brake will be displayed on Pascal+.
This is an indicator of:
* Temperature being too high (HW Thermal Slowdown)
* External Power Brake Assertion is triggered (e.g. by
the system power supply) (HW Power Brake Slowdown)
* Power draw is too high and Fast Trigger protection is
reducing the clocks
SW Thermal Slowdown
SW Thermal capping algorithm is reducing clocks below
requested clocks because GPU temperature is higher than
Max Operating Temp
FB Memory Usage
On-board frame buffer memory information. Reported total memory is af‐
fected by ECC state. If ECC is enabled the total available memory is
decreased by several percent, due to the requisite parity bits. The
driver may also reserve a small amount of memory for internal use, even
without active work on the GPU. For all products.
Total Total size of FB memory.
Used Used size of FB memory.
Free Available size of FB memory.
BAR1 Memory Usage
BAR1 is used to map the FB (device memory) so that it can be directly
accessed by the CPU or by 3rd party devices (peer-to-peer on the PCIe
bus).
Total Total size of BAR1 memory.
Used Used size of BAR1 memory.
Free Available size of BAR1 memory.
Compute Mode
The compute mode flag indicates whether individual or multiple compute
applications may run on the GPU.
"Default" means multiple contexts are allowed per device.
"Exclusive Process" means only one context is allowed per device, us‐
able from multiple threads at a time.
"Prohibited" means no contexts are allowed per device (no compute
apps).
"EXCLUSIVE_PROCESS" was added in CUDA 4.0. Prior CUDA releases sup‐
ported only one exclusive mode, which is equivalent to "EXCLU‐
SIVE_THREAD" in CUDA 4.0 and beyond.
For all CUDA-capable products.
Utilization
Utilization rates report how busy each GPU is over time, and can be
used to determine how much an application is using the GPUs in the sys‐
tem.
Note: During driver initialization when ECC is enabled one can see high
GPU and Memory Utilization readings. This is caused by ECC Memory
Scrubbing mechanism that is performed during driver initialization.
GPU Percent of time over the past sample period during which
one or more kernels was executing on the GPU. The sam‐
ple period may be between 1 second and 1/6 second de‐
pending on the product.
Memory Percent of time over the past sample period during which
global (device) memory was being read or written. The
sample period may be between 1 second and 1/6 second de‐
pending on the product.
Encoder Percent of time over the past sample period during which
the GPU's video encoder was being used. The sampling
rate is variable and can be obtained directly via the
nvmlDeviceGetEncoderUtilization() API
Decoder Percent of time over the past sample period during which
the GPU's video decoder was being used. The sampling
rate is variable and can be obtained directly via the
nvmlDeviceGetDecoderUtilization() API
Ecc Mode
A flag that indicates whether ECC support is enabled. May be either
"Enabled" or "Disabled". Changes to ECC mode require a reboot. Re‐
quires Inforom ECC object version 1.0 or higher.
Current The ECC mode that the GPU is currently operating under.
Pending The ECC mode that the GPU will operate under after the
next reboot.
ECC Errors
NVIDIA GPUs can provide error counts for various types of ECC errors.
Some ECC errors are either single or double bit, where single bit er‐
rors are corrected and double bit errors are uncorrectable. Texture
memory errors may be correctable via resend or uncorrectable if the re‐
send fails. These errors are available across two timescales (volatile
and aggregate). Single bit ECC errors are automatically corrected by
the HW and do not result in data corruption. Double bit errors are de‐
tected but not corrected. Please see the ECC documents on the web for
information on compute application behavior when double bit errors oc‐
cur. Volatile error counters track the number of errors detected since
the last driver load. Aggregate error counts persist indefinitely and
thus act as a lifetime counter.
A note about volatile counts: On Windows this is once per boot. On
Linux this can be more frequent. On Linux the driver unloads when no
active clients exist. Hence, if persistence mode is enabled or there
is always a driver client active (e.g. X11), then Linux also sees per-
boot behavior. If not, volatile counts are reset each time a compute
app is run.
Tesla and Quadro products from the Fermi and Kepler family can display
total ECC error counts, as well as a breakdown of errors based on loca‐
tion on the chip. The locations are described below. Location-based
data for aggregate error counts requires Inforom ECC object version
2.0. All other ECC counts require ECC object version 1.0.
Device Memory Errors detected in global device memory.
Register File Errors detected in register file memory.
L1 Cache Errors detected in the L1 cache.
L2 Cache Errors detected in the L2 cache.
Texture Memory Parity errors detected in texture memory.
Total Total errors detected across entire chip. Sum of Device
Memory, Register File, L1 Cache, L2 Cache and Texture
Memory.
Page Retirement
NVIDIA GPUs can retire pages of GPU device memory when they become un‐
reliable. This can happen when multiple single bit ECC errors occur
for the same page, or on a double bit ECC error. When a page is re‐
tired, the NVIDIA driver will hide it such that no driver, or applica‐
tion memory allocations can access it.
Double Bit ECC The number of GPU device memory pages that have been re‐
tired due to a double bit ECC error.
Single Bit ECC The number of GPU device memory pages that have been re‐
tired due to multiple single bit ECC errors.
Pending Checks if any GPU device memory pages are pending blacklist on
the next reboot. Pages that are retired but not yet blacklisted can
still be allocated, and may cause further reliability issues.
Temperature
Readings from temperature sensors on the board. All readings are in
degrees C. Not all products support all reading types. In particular,
products in module form factors that rely on case fans or passive cool‐
ing do not usually provide temperature readings. See below for re‐
strictions.
GPU Core GPU temperature. For all discrete and S-class
products.
Shutdown Temp The temperature at which a GPU will shutdown.
Slowdown Temp The temperature at which a GPU will begin slowing itself
down through HW, in order to cool.
Max Operating Temp
The temperature at which a GPU will begin slowing itself
down through SW, in order to cool.
Power Readings
Power readings help to shed light on the current power usage of the
GPU, and the factors that affect that usage. When power management is
enabled the GPU limits power draw under load to fit within a predefined
power envelope by manipulating the current performance state. See be‐
low for limits of availability. Please note that power readings are
not applicable for Pascal and higher GPUs with BA sensor boards.
Power State Power State is deprecated and has been renamed to Per‐
formance State in 2.285. To maintain XML compatibility,
in XML format Performance State is listed in both
places.
Power Management
A flag that indicates whether power management is en‐
abled. Either "Supported" or "N/A". Requires Inforom
PWR object version 3.0 or higher or Kepler device.
Power Draw The last measured power draw for the entire board, in
watts. Only available if power management is supported.
Please note that for boards without INA sensors, this
refers to the power draw for the GPU and not for the en‐
tire board.
Power Limit The software power limit, in watts. Set by software
such as nvidia-smi. Only available if power management
is supported. Requires Inforom PWR object version 3.0
or higher or Kepler device. On Kepler devices Power
Limit can be adjusted using -pl,--power-limit= switches.
Enforced Power Limit
The power management algorithm's power ceiling, in
watts. Total board power draw is manipulated by the
power management algorithm such that it stays under this
value. This limit is the minimum of various limits such
as the software limit listed above. Only available if
power management is supported. Requires a Kepler de‐
vice. Please note that for boards without INA sensors,
it is the GPU power draw that is being manipulated.
Default Power Limit
The default power management algorithm's power ceiling,
in watts. Power Limit will be set back to Default Power
Limit after driver unload. Only on supported devices
from Kepler family.
Min Power Limit
The minimum value in watts that power limit can be set
to. Only on supported devices from Kepler family.
Max Power Limit
The maximum value in watts that power limit can be set
to. Only on supported devices from Kepler family.
Clocks
Current frequency at which parts of the GPU are running. All readings
are in MHz.
Graphics Current frequency of graphics (shader) clock.
SM Current frequency of SM (Streaming Multiprocessor)
clock.
Memory Current frequency of memory clock.
Video Current frequency of video (encoder + decoder) clocks.
Applications Clocks
User specified frequency at which applications will be running at. Can
be changed with [-ac | --applications-clocks] switches.
Graphics User specified frequency of graphics (shader) clock.
Memory User specified frequency of memory clock.
Default Applications Clocks
Default frequency at which applications will be running at. Applica‐
tion clocks can be changed with [-ac | --applications-clocks] switches.
Application clocks can be set to default using [-rac | --reset-applica‐
tions-clocks] switches.
Graphics Default frequency of applications graphics (shader)
clock.
Memory Default frequency of applications memory clock.
Max Clocks
Maximum frequency at which parts of the GPU are design to run. All
readings are in MHz.
On GPUs from Fermi family current P0 clocks (reported in Clocks sec‐
tion) can differ from max clocks by few MHz.
Graphics Maximum frequency of graphics (shader) clock.
SM Maximum frequency of SM (Streaming Multiprocessor)
clock.
Memory Maximum frequency of memory clock.
Video Maximum frequency of video (encoder + decoder) clock.
Clock Policy
User-specified settings for automated clocking changes such as auto
boost.
Auto Boost Indicates whether auto boost mode is currently enabled
for this GPU (On) or disabled for this GPU (Off). Shows
(N/A) if boost is not supported. Auto boost allows dy‐
namic GPU clocking based on power, thermal and utiliza‐
tion. When auto boost is disabled the GPU will attempt
to maintain clocks at precisely the Current Application
Clocks settings (whenever a CUDA context is active).
With auto boost enabled the GPU will still attempt to
maintain this floor, but will opportunistically boost to
higher clocks when power, thermal and utilization head‐
room allow. This setting persists for the life of the
CUDA context for which it was requested. Apps can re‐
quest a particular mode either via an NVML call (see
NVML SDK) or by setting the CUDA environment variable
CUDA_AUTO_BOOST.
Auto Boost Default
Indicates the default setting for auto boost mode, ei‐
ther enabled (On) or disabled (Off). Shows (N/A) if
boost is not supported. Apps will run in the default
mode if they have not explicitly requested a particular
mode. Note: Auto Boost settings can only be modified if
"Persistence Mode" is enabled, which is NOT by default.
Supported clocks
List of possible memory and graphics clocks combinations that the GPU
can operate on (not taking into account HW brake reduced clocks).
These are the only clock combinations that can be passed to --applica‐
tions-clocks flag. Supported Clocks are listed only when -q -d SUP‐
PORTED_CLOCKS switches are provided or in XML format.
Processes
List of processes having Compute or Graphics Context on the device.
Compute processes are reported on all the fully supported products. Re‐
porting for Graphics processes is limited to the supported products
starting with Kepler architecture.
Each Entry is of format "<GPU Index> <PID> <Type> <Process Name> <GPU
Memory Usage>"
GPU Index Represents NVML Index of the device.
PID Represents Process ID corresponding to the active Com‐
pute or Graphics context.
Type Displayed as "C" for Compute Process, "G" for Graphics
Process, and "C+G" for the process having both Compute
and Graphics contexts.
Process Name Represents process name for the Compute or Graphics
process.
GPU Memory Usage
Amount of memory used on the device by the context. Not
available on Windows when running in WDDM mode because
Windows KMD manages all the memory not NVIDIA driver.
Stats (EXPERIMENTAL)
List GPU statistics such as power samples, utilization samples, xid
events, clock change events and violation counters.
Supported on Tesla, GRID and Quadro based products under Linux.
Limited to Kepler or newer GPUs.
Displays statistics in CSV format as follows:
<GPU device index>, <metric name>, <CPU Timestamp in us>, <value for
metric>
The metrics to display with their units are as follows:
Power samples in Watts.
GPU Temperature samples in degrees Celsius.
GPU, Memory, Encoder and Decoder utilization samples in Percentage.
Xid error events reported with Xid error code. The error code is 999
for unknown xid error.
Processor and Memory clock changes in MHz.
Violation due to Power capping with violation time in ns. (Tesla Only)
Violation due to Thermal capping with violation boolean flag (1/0).
(Tesla Only)
Notes:
Any statistic preceded by "#" is a comment.
Non supported device is displayed as "#<device Index>, Device not sup‐
ported".
Non supported metric is displayed as "<device index>, <metric name>,
N/A, N/A".
Violation due to Thermal/Power supported only for Tesla based products.
Thermal Violations are limited to Tesla K20 and higher.
Device Monitoring
The "nvidia-smi dmon" command-line is used to monitor one or more GPUs
(up to 4 devices) plugged into the system. This tool allows the user to
see one line of monitoring data per monitoring cycle. The output is in
concise format and easy to interpret in interactive mode. The output
data per line is limited by the terminal size. It is supported on
Tesla, GRID, Quadro and limited GeForce products for Kepler or newer
GPUs under bare metal 64 bits Linux. By default, the monitoring data
includes Power Usage, Temperature, SM clocks, Memory clocks and Uti‐
lization values for SM, Memory, Encoder and Decoder. It can also be
configured to report other metrics such as frame buffer memory usage,
bar1 memory usage, power/thermal violations and aggregate single/double
bit ecc errors. If any of the metric is not supported on the device or
any other error in fetching the metric is reported as "-" in the output
data. The user can also configure monitoring frequency and the number
of monitoring iterations for each run. There is also an option to in‐
clude date and time at each line. All the supported options are exclu‐
sive and can be used together in any order.
Usage:
1) Default with no arguments
nvidia-smi dmon
Monitors default metrics for up to 4 supported devices under natural
enumeration (starting with GPU index 0) at a frequency of 1 sec. Runs
until terminated with ^C.
2) Select one or more devices
nvidia-smi dmon -i <device1,device2, .. , deviceN>
Reports default metrics for the devices selected by comma separated de‐
vice list. The tool picks up to 4 supported devices from the list under
natural enumeration (starting with GPU index 0).
3) Select metrics to be displayed
nvidia-smi dmon -s <metric_group>
<metric_group> can be one or more from the following:
p - Power Usage (in Watts) and Gpu/Memory Temperature (in C) if
supported
u - Utilization (SM, Memory, Encoder and Decoder Utilization in %)
c - Proc and Mem Clocks (in MHz)
v - Power Violations (in %) and Thermal Violations (as a boolean
flag)
m - Frame Buffer and Bar1 memory usage (in MB)
e - ECC (Number of aggregated single bit, double bit ecc errors)
and PCIe Replay errors
t - PCIe Rx and Tx Throughput in MB/s (Maxwell and above)
4) Configure monitoring iterations
nvidia-smi dmon -c <number of samples>
Displays data for specified number of samples and exit.
5) Configure monitoring frequency
nvidia-smi dmon -d <time in secs>
Collects and displays data at every specified monitoring interval until
terminated with ^C.
6) Display date
nvidia-smi dmon -o D
Prepends monitoring data with date in YYYYMMDD format.
7) Display time
nvidia-smi dmon -o T
Prepends monitoring data with time in HH:MM:SS format.
8) Help Information
nvidia-smi dmon -h
Displays help information for using the command line.
Daemon (EXPERIMENTAL)
The "nvidia-smi daemon" starts a background process to monitor one or
more GPUs plugged in to the system. It monitors the requested GPUs ev‐
ery monitoring cycle and logs the file in compressed format at the user
provided path or the default location at /var/log/nvstats/. The log
file is created with system's date appended to it and of the format
nvstats-YYYYMMDD. The flush operation to the log file is done every al‐
ternate monitoring cycle. Daemon also logs it's own PID at
/var/run/nvsmi.pid. By default, the monitoring data to persist includes
Power Usage, Temperature, SM clocks, Memory clocks and Utilization val‐
ues for SM, Memory, Encoder and Decoder. The daemon tools can also be
configured to record other metrics such as frame buffer memory usage,
bar1 memory usage, power/thermal violations and aggregate single/double
bit ecc errors.The default monitoring cycle is set to 10 secs and can
be configured via command-line. It is supported on Tesla, GRID, Quadro
and GeForce products for Kepler or newer GPUs under bare metal 64 bits
Linux. The daemon requires root privileges to run, and only supports
running a single instance on the system. All of the supported options
are exclusive and can be used together in any order.
Usage:
1) Default with no arguments
nvidia-smi daemon
Runs in the background to monitor default metrics for up to 4 supported
devices under natural enumeration (starting with GPU index 0) at a fre‐
quency of 10 sec. The date stamped log file is created at /var/log/nvs‐
tats/.
2) Select one or more devices
nvidia-smi daemon -i <device1,device2, .. , deviceN>
Runs in the background to monitor default metrics for the devices se‐
lected by comma separated device list. The tool picks up to 4 supported
devices from the list under natural enumeration (starting with GPU in‐
dex 0).
3) Select metrics to be monitored
nvidia-smi daemon -s <metric_group>
<metric_group> can be one or more from the following:
p - Power Usage (in Watts) and Gpu/Memory Temperature (in C) if
supported
u - Utilization (SM, Memory, Encoder and Decoder Utilization in %)
c - Proc and Mem Clocks (in MHz)
v - Power Violations (in %) and Thermal Violations (as a boolean
flag)
m - Frame Buffer and Bar1 memory usage (in MB)
e - ECC (Number of aggregated single bit, double bit ecc errors)
and PCIe Replay errors
t - PCIe Rx and Tx Throughput in MB/s (Maxwell and above)
4) Configure monitoring frequency
nvidia-smi daemon -d <time in secs>
Collects data at every specified monitoring interval until terminated.
5) Configure log directory
nvidia-smi daemon -p <path of directory>
The log files are created at the specified directory.
6) Configure log file name
nvidia-smi daemon -j <string to append log file name>
The command-line is used to append the log file name with the user pro‐
vided string.
7) Terminate the daemon
nvidia-smi daemon -t
This command-line uses the stored PID (at /var/run/nvsmi.pid) to termi‐
nate the daemon. It makes the best effort to stop the daemon and offers
no guarantees for it's termination. In case the daemon is not termi‐
nated, then the user can manually terminate by sending kill signal to
the daemon. Performing a GPU reset operation (via nvidia-smi) requires
all GPU processes to be exited, including the daemon. Users who have
the daemon open will see an error to the effect that the GPU is busy.
8) Help Information
nvidia-smi daemon -h
Displays help information for using the command line.
Replay Mode (EXPERIMENTAL)
The "nvidia-smi replay" command-line is used to extract/replay all or
parts of log file generated by the daemon. By default, the tool tries
to pull the metrics such as Power Usage, Temperature, SM clocks, Memory
clocks and Utilization values for SM, Memory, Encoder and Decoder. The
replay tool can also fetch other metrics such as frame buffer memory
usage, bar1 memory usage, power/thermal violations and aggregate sin‐
gle/double bit ecc errors. There is an option to select a set of met‐
rics to replay, If any of the requested metric is not maintained or
logged as not-supported then it's shown as "-" in the output. The for‐
mat of data produced by this mode is such that the user is running the
device monitoring utility interactively. The command line requires
mandatory option "-f" to specify complete path of the log filename, all
the other supported options are exclusive and can be used together in
any order.
Usage:
1) Specify log file to be replayed
nvidia-smi replay -f <log file name>
Fetches monitoring data from the compressed log file and allows the
user to see one line of monitoring data (default metrics with time-
stamp) for each monitoring iteration stored in the log file. A new line
of monitoring data is replayed every other second irrespective of the
actual monitoring frequency maintained at the time of collection. It is
displayed till the end of file or until terminated by ^C.
2) Filter metrics to be replayed
nvidia-smi replay -f <path to log file> -s <metric_group>
<metric_group> can be one or more from the following:
p - Power Usage (in Watts) and Gpu/Memory Temperature (in C) if
supported
u - Utilization (SM, Memory, Encoder and Decoder Utilization in %)
c - Proc and Mem Clocks (in MHz)
v - Power Violations (in %) and Thermal Violations (as a boolean
flag)
m - Frame Buffer and Bar1 memory usage (in MB)
e - ECC (Number of aggregated single bit, double bit ecc errors)
and PCIe Replay errors
t - PCIe Rx and Tx Throughput in MB/s (Maxwell and above)
3) Limit replay to one or more devices
nvidia-smi replay -f <log file> -i <device1,device2, .. , deviceN>
Limits reporting of the metrics to the set of devices selected by comma
separated device list. The tool skips any of the devices not maintained
in the log file.
4) Restrict the time frame between which data is reported
nvidia-smi replay -f <log file> -b <start time in HH:MM:SS format> -e
<end time in HH:MM:SS format>
This option allows the data to be limited between the specified time
range. Specifying time as 0 with -b or -e option implies start or end
file respectively.
5) Redirect replay information to a log file
nvidia-smi replay -f <log file> -r <output file name>
This option takes log file as an input and extracts the information re‐
lated to default metrics in the specified output file.
6) Help Information
nvidia-smi replay -h
Displays help information for using the command line.
Process Monitoring
The "nvidia-smi pmon" command-line is used to monitor compute and
graphics processes running on one or more GPUs (up to 4 devices)
plugged into the system. This tool allows the user to see the statis‐
tics for all the running processes on each device at every monitoring
cycle. The output is in concise format and easy to interpret in inter‐
active mode. The output data per line is limited by the terminal size.
It is supported on Tesla, GRID, Quadro and limited GeForce products for
Kepler or newer GPUs under bare metal 64 bits Linux. By default, the
monitoring data for each process includes the pid, command name and av‐
erage utilization values for SM, Memory, Encoder and Decoder since the
last monitoring cycle. It can also be configured to report frame buffer
memory usage for each process. If there is no process running for the
device, then all the metrics are reported as "-" for the device. If any
of the metric is not supported on the device or any other error in
fetching the metric is also reported as "-" in the output data. The
user can also configure monitoring frequency and the number of monitor‐
ing iterations for each run. There is also an option to include date
and time at each line. All the supported options are exclusive and can
be used together in any order.
Usage:
1) Default with no arguments
nvidia-smi pmon
Monitors all the processes running on each device for up to 4 supported
devices under natural enumeration (starting with GPU index 0) at a fre‐
quency of 1 sec. Runs until terminated with ^C.
2) Select one or more devices
nvidia-smi pmon -i <device1,device2, .. , deviceN>
Reports statistics for all the processes running on the devices se‐
lected by comma separated device list. The tool picks up to 4 supported
devices from the list under natural enumeration (starting with GPU in‐
dex 0).
3) Select metrics to be displayed
nvidia-smi pmon -s <metric_group>
<metric_group> can be one or more from the following:
u - Utilization (SM, Memory, Encoder and Decoder Utilization for
the process in %). Reports average utilization since last monitoring
cycle.
m - Frame Buffer usage (in MB). Reports instantaneous value for
memory usage.
4) Configure monitoring iterations
nvidia-smi pmon -c <number of samples>
Displays data for specified number of samples and exit.
5) Configure monitoring frequency
nvidia-smi pmon -d <time in secs>
Collects and displays data at every specified monitoring interval until
terminated with ^C. The monitoring frequency must be between 1 to 10
secs.
6) Display date
nvidia-smi pmon -o D
Prepends monitoring data with date in YYYYMMDD format.
7) Display time
nvidia-smi pmon -o T
Prepends monitoring data with time in HH:MM:SS format.
8) Help Information
nvidia-smi pmon -h
Displays help information for using the command line.
Topology (EXPERIMENTAL)
List topology information about the system's GPUs, how they connect to
each other as well as qualified NICs capable of RDMA
Displays a matrix of available GPUs with the following legend:
Legend:
X = Self
SYS = Connection traversing PCIe as well as the SMP
interconnect between NUMA nodes (e.g., QPI/UPI)
NODE = Connection traversing PCIe as well as the in‐
terconnect between PCIe Host Bridges within a NUMA node
PHB = Connection traversing PCIe as well as a PCIe
Host Bridge (typically the CPU)
PXB = Connection traversing multiple PCIe switches
(without traversing the PCIe Host Bridge)
PIX = Connection traversing a single PCIe switch
NV# = Connection traversing a bonded set of # NVLinks
vGPU Management
The "nvidia-smi vgpu" command reports on GRID vGPUs executing on sup‐
ported GPUs and hypervisors (refer to driver release notes for sup‐
ported platforms). Summary reporting provides basic information about
vGPUs currently executing on the system. Additional options provide de‐
tailed reporting of vGPU properties, per-vGPU reporting of SM, Memory,
Encoder, and Decoder utilization, and per-GPU reporting of supported
and creatable vGPUs. Periodic reports can be automatically generated by
specifying a configurable loop frequency to any command.
Usage:
1) Help Information
nvidia-smi vgpu -h
Displays help information for using the command line.
2) Default with no arguments
nvidia-smi vgpu
Reports summary of all the vGPUs currently active on each device.
3) Display detailed info on currently active vGPUs
nvidia-smi vgpu -q
Collects and displays information on currently active vGPUs on each de‐
vice, including driver version, utilization, and other information.
4) Select one or more devices
nvidia-smi vgpu -i <device1,device2, .. , deviceN>
Reports summary for all the vGPUs currently active on the devices se‐
lected by comma-separated device list.
5) Display supported vGPUs
nvidia-smi vgpu -s
Displays vGPU types supported on each device. Use the -v / --verbose
option to show detailed info on each vGPU type.
6) Display creatable vGPUs
nvidia-smi vgpu -c
Displays vGPU types creatable on each device. This varies dynamically,
depending on the vGPUs already active on the device. Use the -v /
--verbose option to show detailed info on each vGPU type.
7) Report utilization for currently active vGPUs.
nvidia-smi vgpu -u
Reports average utilization (SM, Memory, Encoder and Decoder) for each
active vGPU since last monitoring cycle. The default cycle time is 1
second, and the command runs until terminated with ^C. If a device has
no active vGPUs, its metrics are reported as "-".
8) Configure loop frequency
nvidia-smi vgpu [-s -c -q -u] -l <time in secs>
Collects and displays data at a specified loop interval until termi‐
nated with ^C. The loop frequency must be between 1 and 10 secs. When
no time is specified, the loop frequency defaults to 5 secs.
9) Display GPU engine usage
nvidia-smi vgpu -p
Display GPU engine usage of currently active processes running in the
vGPU VMs.
10) Display migration capabitlities.
nvidia-smi vgpu -m
Display pGPU's migration/suspend/resume capability.
11) Display Nvidia Encoder session info.
nvidia-smi vgpu -es
Display the information about encoder sessions for currently running
vGPUs.
12) Display accounting statistics.
nvidia-smi vgpu --query-accounted-apps=[input parameters]
Display accounting stats for compute/graphics processes.
To find list of properties which can be queried, run - 'nvidia-smi
--help-query-accounted-apps'.
13) Display Nvidia Frame Buffer Capture session info.
nvidia-smi vgpu -fs
Display the information about FBC sessions for currently running vGPUs.
Note : Horizontal resolution, vertical resolution, average FPS and av‐
erage latency data for a FBC session may be zero if there are no new
frames captured since the session started.
UNIT ATTRIBUTES
The following list describes all possible data returned by the -q -u
unit query option. Unless otherwise noted all numerical results are
base 10 and unitless.
Timestamp
The current system timestamp at the time nvidia-smi was invoked. For‐
mat is "Day-of-week Month Day HH:MM:SS Year".
Driver Version
The version of the installed NVIDIA display driver. Format is "Ma‐
jor-Number.Minor-Number".
HIC Info
Information about any Host Interface Cards (HIC) that are installed in
the system.
Firmware Version
The version of the firmware running on the HIC.
Attached Units
The number of attached Units in the system.
Product Name
The official product name of the unit. This is an alphanumeric value.
For all S-class products.
Product Id
The product identifier for the unit. This is an alphanumeric value of
the form "part1-part2-part3". For all S-class products.
Product Serial
The immutable globally unique identifier for the unit. This is an al‐
phanumeric value. For all S-class products.
Firmware Version
The version of the firmware running on the unit. Format is "Major-Num‐
ber.Minor-Number". For all S-class products.
LED State
The LED indicator is used to flag systems with potential problems. An
LED color of AMBER indicates an issue. For all S-class products.
Color The color of the LED indicator. Either "GREEN" or "AM‐
BER".
Cause The reason for the current LED color. The cause may be
listed as any combination of "Unknown", "Set to AMBER by
host system", "Thermal sensor failure", "Fan failure"
and "Temperature exceeds critical limit".
Temperature
Temperature readings for important components of the Unit. All read‐
ings are in degrees C. Not all readings may be available. For all S-
class products.
Intake Air temperature at the unit intake.
Exhaust Air temperature at the unit exhaust point.
Board Air temperature across the unit board.
PSU
Readings for the unit power supply. For all S-class products.
State Operating state of the PSU. The power supply state can
be any of the following: "Normal", "Abnormal", "High
voltage", "Fan failure", "Heatsink temperature", "Cur‐
rent limit", "Voltage below UV alarm threshold",
"Low-voltage", "I2C remote off command", "MOD_DISABLE
input" or "Short pin transition".
Voltage PSU voltage setting, in volts.
Current PSU current draw, in amps.
Fan Info
Fan readings for the unit. A reading is provided for each fan, of
which there can be many. For all S-class products.
State The state of the fan, either "NORMAL" or "FAILED".
Speed For a healthy fan, the fan's speed in RPM.
Attached GPUs
A list of PCI bus ids that correspond to each of the GPUs attached to
the unit. The bus ids have the form "domain:bus:device.function", in
hex. For all S-class products.
NOTES
On Linux, NVIDIA device files may be modified by nvidia-smi if run as
root. Please see the relevant section of the driver README file.
The -a and -g arguments are now deprecated in favor of -q and -i, re‐
spectively. However, the old arguments still work for this release.
EXAMPLES
nvidia-smi -q
Query attributes for all GPUs once, and display in plain text to std‐
out.
nvidia-smi --format=csv,noheader --query-gpu=uuid,persistence_mode
Query UUID and persistence mode of all GPUs in the system.
nvidia-smi -q -d ECC,POWER -i 0 -l 10 -f out.log
Query ECC errors and power consumption for GPU 0 at a frequency of 10
seconds, indefinitely, and record to the file out.log.
"nvidia-smi -c 1 -i
GPU-b2f5f1b745e3d23d-65a3a26d-097db358-7303e0b6-149642ff3d219f8587cde3a8"
Set the compute mode to "PROHIBITED" for GPU with UUID
"GPU-b2f5f1b745e3d23d-65a3a26d-097db358-7303e0b6-149642ff3d219f8587cde3a8".
nvidia-smi -q -u -x --dtd
Query attributes for all Units once, and display in XML format with em‐
bedded DTD to stdout.
nvidia-smi --dtd -u -f nvsmi_unit.dtd
Write the Unit DTD to nvsmi_unit.dtd.
nvidia-smi -q -d SUPPORTED_CLOCKS
Display supported clocks of all GPUs.
nvidia-smi -i 0 --applications-clocks 2500,745
Set applications clocks to 2500 MHz memory, and 745 MHz graphics.
CHANGE LOG
=== Known Issues ===
* On Linux GPU Reset can't be triggered when there is pending GOM
change.
* On Linux GPU Reset may not successfully change pending ECC mode. A
full reboot may be required to enable the mode change.
* On Linux platforms that configure NVIDIA GPUs as NUMA nodes, en‐
abling persistence mode or resetting GPUs may print "Warning: persis‐
tence mode is disabled on device" if nvidia-persistenced is not run‐
ning, or if nvidia-persistenced cannot access files in the NVIDIA
driver's procfs directory for the device (/proc/driver/nvidia/gpus/<PCI
Config Address>/). During GPU reset and driver reload, this directory
will be deleted and recreated, and outstanding references to the
deleted directory, such as mounts or shells, can prevent processes from
accessing files in the new directory.
* === Changes between nvidia-smi v361 Update and v418 ===
* Support for Volta and Turing architectures, bug fixes, performance
improvements, and new features
* === Changes between nvidia-smi v352 Update and v361 ===
* Added nvlink support to expose the publicly available NVLINK NVML
APIs
* Added clocks sub-command with synchronized boost support
* Updated nvidia-smi stats to report GPU temperature metric
* Updated nvidia-smi dmon to support PCIe throughput
* Updated nvidia-smi daemon/replay to support PCIe throughput
* Updated nvidia-smi dmon, daemon and replay to support PCIe Replay
Errors
* Added GPU part numbers in nvidia-smi -q
* Removed support for exclusive thread compute mode
* Added Video (encoder/decode) clocks to the Clocks and Max Clocks
display of nvidia-smi -q
* Added memory temperature output to nvidia-smi dmon
* Added --lock-gpu-clock and --reset-gpu-clock command to lock to
closest min/max GPU clock provided and reset clock
* Added --cuda-clocks to override or restore default CUDA clocks
=== Changes between nvidia-smi v346 Update and v352 ===
* Added topo support to display affinities per GPU
* Added topo support to display neighboring GPUs for a given level
* Added topo support to show pathway between two given GPUs
* Added "nvidia-smi pmon" command-line for process monitoring in
scrolling format
* Added "--debug" option to produce an encrypted debug log for use in
submission of bugs back to NVIDIA
* Fixed reporting of Used/Free memory under Windows WDDM mode
* The accounting stats is updated to include both running and termi‐
nated processes. The execution time of running process is reported as 0
and updated to actual value when the process is terminated.
=== Changes between nvidia-smi v340 Update and v346 ===
* Added reporting of PCIe replay counters
* Added support for reporting Graphics processes via nvidia-smi
* Added reporting of PCIe utilization
* Added dmon command-line for device monitoring in scrolling format
* Added daemon command-line to run in background and monitor devices
as a daemon process. Generates dated log files at /var/log/nvstats/
* Added replay command-line to replay/extract the stat files gener‐
ated by the daemon tool
=== Changes between nvidia-smi v331 Update and v340 ===
* Added reporting of temperature threshold information.
* Added reporting of brand information (e.g. Tesla, Quadro, etc.)
* Added support for K40d and K80.
* Added reporting of max, min and avg for samples (power, utiliza‐
tion, clock changes). Example commandline: nvidia-smi -q -d power,uti‐
lization, clock
* Added nvidia-smi stats interface to collect statistics such as
power, utilization, clock changes, xid events and perf capping counters
with a notion of time attached to each sample. Example commandline:
nvidia-smi stats
* Added support for collectively reporting metrics on more than one
GPU. Used with comma separated with "-i" option. Example: nvidia-smi -i
0,1,2
* Added support for displaying the GPU encoder and decoder utiliza‐
tions
* Added nvidia-smi topo interface to display the GPUDirect communica‐
tion matrix (EXPERIMENTAL)
* Added support for displayed the GPU board ID and whether or not it
is a multiGPU board
* Removed user-defined throttle reason from XML output
=== Changes between nvidia-smi v5.319 Update and v331 ===
* Added reporting of minor number.
* Added reporting BAR1 memory size.
* Added reporting of bridge chip firmware.
=== Changes between nvidia-smi v4.319 Production and v4.319 Update
===
* Added new --applications-clocks-permission switch to change permis‐
sion requirements for setting and resetting applications clocks.
=== Changes between nvidia-smi v4.304 and v4.319 Production ===
* Added reporting of Display Active state and updated documentation
to clarify how it differs from Display Mode and Display Active state
* For consistency on multi-GPU boards nvidia-smi -L always displays
UUID instead of serial number
* Added machine readable selective reporting. See SELECTIVE QUERY OP‐
TIONS section of nvidia-smi -h
* Added queries for page retirement information. See --help-query-
retired-pages and -d PAGE_RETIREMENT
* Renamed Clock Throttle Reason User Defined Clocks to Applications
Clocks Setting
* On error, return codes have distinct non zero values for each error
class. See RETURN VALUE section
* nvidia-smi -i can now query information from healthy GPU when there
is a problem with other GPU in the system
* All messages that point to a problem with a GPU print pci bus id of
a GPU at fault
* New flag --loop-ms for querying information at higher rates than
once a second (can have negative impact on system performance)
* Added queries for accounting procsses. See --help-query-accounted-
apps and -d ACCOUNTING
* Added the enforced power limit to the query output
=== Changes between nvidia-smi v4.304 RC and v4.304 Production ===
* Added reporting of GPU Operation Mode (GOM)
* Added new --gom switch to set GPU Operation Mode
=== Changes between nvidia-smi v3.295 and v4.304 RC ===
* Reformatted non-verbose output due to user feedback. Removed pend‐
ing information from table.
* Print out helpful message if initialization fails due to kernel
module not receiving interrupts
* Better error handling when NVML shared library is not present in
the system
* Added new --applications-clocks switch
* Added new filter to --display switch. Run with -d SUPPORTED_CLOCKS
to list possible clocks on a GPU
* When reporting free memory, calculate it from the rounded total and
used memory so that values add up
* Added reporting of power management limit constraints and default
limit
* Added new --power-limit switch
* Added reporting of texture memory ECC errors
* Added reporting of Clock Throttle Reasons
=== Changes between nvidia-smi v2.285 and v3.295 ===
* Clearer error reporting for running commands (like changing compute
mode)
* When running commands on multiple GPUs at once N/A errors are
treated as warnings.
* nvidia-smi -i now also supports UUID
* UUID format changed to match UUID standard and will report a dif‐
ferent value.
=== Changes between nvidia-smi v2.0 and v2.285 ===
* Report VBIOS version.
* Added -d/--display flag to filter parts of data
* Added reporting of PCI Sub System ID
* Updated docs to indicate we support M2075 and C2075
* Report HIC HWBC firmware version with -u switch
* Report max(P0) clocks next to current clocks
* Added --dtd flag to print the device or unit DTD
* Added message when NVIDIA driver is not running
* Added reporting of PCIe link generation (max and current), and link
width (max and current).
* Getting pending driver model works on non-admin
* Added support for running nvidia-smi on Windows Guest accounts
* Running nvidia-smi without -q command will output non verbose ver‐
sion of -q instead of help
* Fixed parsing of -l/--loop= argument (default value, 0, to big
value)
* Changed format of pciBusId (to XXXX:XX:XX.X - this change was visi‐
ble in 280)
* Parsing of busId for -i command is less restrictive. You can pass
0:2:0.0 or 0000:02:00 and other variations
* Changed versioning scheme to also include "driver version"
* XML format always conforms to DTD, even when error conditions occur
* Added support for single and double bit ECC events and XID errors
(enabled by default with -l flag disabled for -x flag)
* Added device reset -r --gpu-reset flags
* Added listing of compute running processes
* Renamed power state to performance state. Deprecated support exists
in XML output only.
* Updated DTD version number to 2.0 to match the updated XML output
SEE ALSO
On Linux, the driver README is installed as
/usr/share/doc/NVIDIA_GLX-1.0/README.txt
AUTHOR
NVIDIA Corporation
COPYRIGHT
Copyright 2011-2020 NVIDIA Corporation.
nvidia-smi 440.100 2020/5/29 nvidia-smi(1)
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Thanks! I have added a reference to it in project man pages.
from gpu-utils.
csecht
commented on August 28, 2024
I was behind the curve on updating the User Guide for the new release, sorry. The updates you made are very good - better than what I would have done for sure.
I see a few places that could use minor edits, but nothing relating to the new release. I’ll set up a pull request.
… On Jun 27, 2020, at 6:44 AM, Rick ***@***.***> wrote:
I made progress on the User Guide today and pushed my latest.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALMVCQT7TC5YEFAIYNTBXRTRYXLRRANCNFSM4OGEFXNA>.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
@csecht
It would be great if you updated the images also. I have made significant changes in the gui since you last updated them. On my systems, I am currently not running any GPU projects, so the plots are boring...
Also, I have changed the repository name, so it would be good to clone/fork again to get the new name. Maybe fork is automatically updated...
from gpu-utils.
csecht
commented on August 28, 2024
I’ll work on new images. I tried to fork the renamed repository into a new repository with the name on my account, but haven’t figured out how to do that from the web site. Any attempt to fork your base gpu-utils repository into my new one goes instead to my original amdgpu-utils. Once I get that sorted, I’ll update the images.
… On Jun 28, 2020, at 7:32 PM, Rick ***@***.***> wrote:
@csecht <https://github.com/csecht>
It would be great if you updated the images also. I have made significant changes in the gui since you last updated them. On my systems, I am currently not running any GPU projects, so the plots are boring...
Also, I have changed the repository name, so it would be good to clone/fork again to get the new name. Maybe fork is automatically updated...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALMVCQU43H5XB4J35OT5E5DRY7OJ3ANCNFSM4OGEFXNA>.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Do you know anyone who has both NV and AMD GPUs in a system? It would be cool to get an image of that for the plot example. Seems like Tbar on SETI has a NV/AMD setup, but did not respond to PM. Maybe not the best place to post since the project is in hibernation...
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I’ll work on new images. I tried to fork the renamed repository into a new repository with the name on my account, but haven’t figured out how to do that from the web site. Any attempt to fork your base gpu-utils repository into my new one goes instead to my original amdgpu-utils. Once I get that sorted, I’ll update the images.
By default, the old references will still work, but it is a good idea to update to the new ones. Perhaps deleting your fork and re-forking will work.
from gpu-utils.
KeithMyers
commented on August 28, 2024
Do you know anyone who has both NV and AMD GPUs in a system? It would be cool to get an image of that for the plot example. Seems like Tbar on SETI has a NV/AMD setup, but did not respond to PM. Maybe not the best place to post since the project is in hibernation...
TBar has been ignoring all PM's to him on all the project team forums since the end of Seti. I have sent numerous posts and got nada back from him.
Tom M. might be the other person who could put both AMD and Nvidia into the same host. Seems he is always experimenting with maximizing RAC on his mining rigs.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Tom M. responded, but currently has no systems running in this configuration.
from gpu-utils.
KeithMyers
commented on August 28, 2024
Too bad you didn't catch him a month earlier. I know for a fact he was running both AMD and Nvidia in the same host for a while.
from gpu-utils.
csecht
commented on August 28, 2024
I have a GTX 750 that I could bring out of retirement, if it would be suitable. Would that be supported? Would it work with nvidia-smi? Are there nvidia CUDA drivers that I would need to install on my Linux system, Ubuntu 18.04.4?
If it's suitable, then I could set it up in my RX 5600XT host for a "photo op".
from gpu-utils.
csecht
commented on August 28, 2024
By default, the old references will still work, but it is a good idea to update to the new ones. Perhaps deleting your fork and re-forking will work.
Yes, that worked to set up my new repo, thanks.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I have a GTX 750 that I could bring out of retirement, if it would be suitable. Would that be supported? Would it work with nvidia-smi? Are there nvidia CUDA drivers that I would need to install on my Linux system, Ubuntu 18.04.4?
If it's suitable, then I could set it up in my RX 5600XT host for a "photo op".
I have no experience with NV cards. Perhaps @KeithMyers can comment.
from gpu-utils.
KeithMyers
commented on August 28, 2024
Just install the Nvidia drivers from the distro repository. Already comes with the CUDA library. Nvidia-smi is part of the driver package. You will also get installed the Nvidia X Server Settings application in your Apps.
You would just need to install the card. Boot the system and do a sudo apt update >> sudo apt upgrade and you will pull in the latest Nvidia drivers which is 440.100 version on Ubuntu 18.04.4.
If you haven't already installed the clinfo utility, do that also. Sudo apt install clinfo. Then once you've rebooted after the sudo apt update and the nvidia drivers are put into the kernel, run clinfo from the Terminal and look at the output. You should see the 440.100 drivers listed along with GTX 750 card as well as your AMD cards and you should see the OpenCL libraries listed also.
from gpu-utils.
csecht
commented on August 28, 2024
Thanks. Will start on this tomorrow.
… On Jun 29, 2020, at 8:06 PM, KeithMyers ***@***.***> wrote:
Just install the Nvidia drivers from the distro repository. Already comes with the CUDA library. Nvidia-smi is part of the driver package. You will also get installed the Nvidia X Server Settings application in your Apps.
You would just need to install the card. Boot the system and do a sudo apt update >> sudo apt upgrade and you will pull in the latest Nvidia drivers which is 440.100 version on Ubuntu 18.04.4.
If you haven't already installed the clinfo utility, do that also. Sudo apt install clinfo. Then once you've rebooted after the sudo apt update and the nvidia drivers are put into the kernel, run clinfo from the Terminal and look at the output. You should see the 440.100 drivers listed along with GTX 750 card as well as your AMD cards and you should see the OpenCL libraries listed also.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALMVCQXFCGGAM2EMOYQDU3LRZE275ANCNFSM4OGEFXNA>.
from gpu-utils.
csecht
commented on August 28, 2024
I got the GTX 750 installed alongside the RX 5600xt, but can't get it crunching; the reason is that the the NVIDIA card (and all earlier AMD generations) use OpenCL 1.2, while the Navi card uses OpenCL 2.0 and the system cannot "drive" both. ..at least that I know how.
gpu-ls works fine.
gpu-mon shows information for both cards, but the model name for the GTX 750 does not show up, even though it does with gpu-ls :
Decoded Device ID: GM107 [GeForce GTX 750]
Do you want a terminal output graphic like this (card1 model name edited in)?
┌─────────────┬────────────────┬────────────────┐
│Card # │card1 │card2 │
├─────────────┼────────────────┼────────────────┤
│Model │GeForce GTX 750 │Radeon RX 5600 X│
│GPU Load % │0 │90 │
│Mem Load % │0 │71 │
│VRAM Usage % │None │53.353 │
│GTT Usage % │None │0.444 │
│Power (W) │0.97 │90.0 │
│Power Cap (W)│38.50 │160.0 │
│Energy (kWh) │0.0 │0.023 │
│T (C) │34.0 │55.0 │
│VddGFX (mV) │0 │937 │
│Fan Spd (%) │40.0 │25 │
│Sclk (MHz) │135 │1780 │
│Sclk Pstate │8 │2 │
│Mclk (MHz) │405 │875 │
│Mclk Pstate │8 │3 │
│Perf Mode │[Not Supported] │5-COMPUTE │
└─────────────┴────────────────┴────────────────┘
gpu-ls --table, however, has a glitch
$ ./gpu-ls --table
OS command [nvidia-smi] executable found: [/usr/bin/nvidia-smi]
Detected GPUs: INTEL: 1, NVIDIA: 1, AMD: 1
AMD: amdgpu version: 20.10-1048554
AMD: Wattman features enabled: 0xfffd7fff
3 total GPUs, 1 rw, 1 r-only, 0 w-only
Status of Readable GPUs:
┌─────────────┬────────────────┬────────────────┐
│Card # │card1 │card2 │
├─────────────┼────────────────┼────────────────┤
│Model │ │Radeon RX 5600 X│
│GPU Load % │None │0 │
│Mem Load % │None │0 │
│VRAM Usage % │None │0.271 │
│GTT Usage % │None │0.218 │
│Power (W) │None │7.0 │
│Power Cap (W)│None │160.0 │
│Energy (kWh) │0.0 │0.0 │
│T (C) Traceback (most recent call last):
File "./gpu-ls", line 150, in <module>
main()
File "./gpu-ls", line 143, in main
com_gpu_list.print_table(title='Status of Readable GPUs:')
File "/home/craig/amdgpu-utils-master/GPUmodules/GPUmodule.py", line 2106, in print_table
data_value_raw = gpu.get_params_value(table_item)
File "/home/craig/amdgpu-utils-master/GPUmodules/GPUmodule.py", line 631, in get_params_value
if 'edge' in self.prm['temperatures'].keys():
AttributeError: 'NoneType' object has no attribute 'keys'
gpu-plot shows both cards, but only the AMD is active. Do you want something like this .png for the Guide (below, at bottom)? Again, no name for the nvidia card1. The boinc-client is not giving gamma-ray pulsar work to the nvidia card even though everything seems to be in order. This from the boinc-client event log after startup:
Wed 01 Jul 2020 02:04:58 PM CDT | | CUDA: NVIDIA GPU 0: GeForce GTX 750 (driver version 390.13, CUDA version 9.1, compute capability 5.0, 981MB, 920MB available, 1111 GFLOPS peak)
Wed 01 Jul 2020 02:04:58 PM CDT | | OpenCL: NVIDIA GPU 0: GeForce GTX 750 (driver version 390.138, device version OpenCL 1.2 CUDA, 981MB, 920MB available, 1111 GFLOPS peak)
Wed 01 Jul 2020 02:04:58 PM CDT | | OpenCL: AMD/ATI GPU 0: AMD Radeon RX 5600 XT (driver version 3075.10 (PAL,LC), device version OpenCL 2.0 AMD-APP (3075.10), 6128MB, 6128MB available, 4101 GFLOPS peak)
Ah, I just noticed that it only has 920MB available. Strange, because I started E@H with with this GTX card crunching gamma-ray tasks, but now it won't. Maybe I'm remembering wrong.
Where to from here?
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Thanks for checking this out. I would like to resolve all of the issues while you have the system setup. I will let you know when I post code updates that need verification.
from gpu-utils.
csecht
commented on August 28, 2024
Okay, no problem. The NVIDIA card is now crunching! I was just impatient earlier; didn't give boinc-client time to do its thing.
Here is a plot with the two active cards. Is this what you had in mind for the Guide?
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I just pushed a fix for the AttributeError when running gpu-ls --table.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I just pushed a change to fix the selection of the shortest NV card name.
from gpu-utils.
csecht
commented on August 28, 2024
Got it. *gpu-ls --table works now:
$ ./gpu-ls --table
OS command [nvidia-smi] executable found: [/usr/bin/nvidia-smi]
Detected GPUs: INTEL: 1, NVIDIA: 1, AMD: 1
AMD: amdgpu version: 20.10-1048554
AMD: Wattman features enabled: 0xfffd7fff
3 total GPUs, 1 rw, 1 r-only, 0 w-only
Status of Readable GPUs:
┌─────────────┬────────────────┬────────────────┐
│Card # │card1 │card2 │
├─────────────┼────────────────┼────────────────┤
│Model │ │Radeon RX 5600 X│
│GPU Load % │None │95 │
│Mem Load % │None │52 │
│VRAM Usage % │None │11.969 │
│GTT Usage % │None │0.432 │
│Power (W) │None │98.0 │
│Power Cap (W)│None │160.0 │
│Energy (kWh) │0.0 │0.0 │
│T (C) │None │62.0 │
│VddGFX (mV) │0 │931 │
│Fan Spd (%) │None │36 │
│Sclk (MHz) │None │1780 │
│Sclk Pstate │ │2 │
│Mclk (MHz) │None │875 │
│Mclk Pstate │ │3 │
│Perf Mode │ │5-COMPUTE │
└─────────────┴────────────────┴────────────────┘
The short name doesn't show up anywhere though.
from gpu-utils.
csecht
commented on August 28, 2024
Here is the debug file from gpu-ls --table
debug_gpu-utils_20200701-191032.log
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Just pushed another fix for Model name.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
From the log file, it seems like to call to read all sensors is failing:
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query None error: [Command '['/usr/bin/nvidia-smi', '-i', '01:00.0', '--query-gpu=power.limit,power.min_limit,power.max_limit,memory.total,vbios_version,driver_version,compute_mode,name,serial,index,gpu_uuid,power.draw,temperature.gpu,temperature.memory,clocks.gr,clocks.sm,clocks.mem,clocks.video,clocks.max.gr,clocks.max.sm,clocks.max.mem,utilization.gpu,utilization.memory,memory.used,fan.speed,gom.current,pcie.link.width.current,pcie.link.gen.current,pstate', '--format=csv,noheader,nounits']' returned non-zero exit status 2.]
Can you isolate which item has an issue for your card? Maybe if you run the above command on the command line it will indicate which parameter failed. I guess it is possible that older generation cards support less parameters for reading.
from gpu-utils.
csecht
commented on August 28, 2024
I'll give it a shot.
Probably this:
/usr/bin/nvidia-smi -i 01:00.0 --query-gpu=temperature.memory --format=csv
Field "temperature.memory" is not a valid field to query.
serial and gom.current are [Not Supported]
All the rest worked.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I'll give it a shot.
Probably this:
/usr/bin/nvidia-smi -i 01:00.0 --query-gpu=temperature.memory --format=csv
Field "temperature.memory" is not a valid field to query.serial and gom.current are [Not Supported]
All the rest worked.
I am implementing a validate version of read all sensors that will read one at a time and add failing parameters to a sensor disable list, just like is done for AMD.
Can you check if the model name issue is solved? gpu-plot should work now. The outstanding issue should not impact plot or mon.
from gpu-utils.
csecht
commented on August 28, 2024
Name is showing up now, but is truncated. The "official" name is too long, but that's a pciid issue, not gpu-utils.
from gpu-utils.
csecht
commented on August 28, 2024
The complete name shows in gpu-plot
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Looks good!
It will take a day for me to complete the changes to fix the issue with gpu-ls
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I pushed a version that reads NV sensors individually and adds problematic sensors to a disable list for the first time the All set of sensors is read. Please help to verify gpu-ls.
from gpu-utils.
csecht
commented on August 28, 2024
There's a bug:
~/Desktop/gpu-utils-master$ ./gpu-ls
OS command [nvidia-smi] executable found: [/usr/bin/nvidia-smi]
Traceback (most recent call last):
File "./gpu-ls", line 150, in <module>
main()
File "./gpu-ls", line 98, in main
gpu_list.set_gpu_list(clinfo_flag=True)
File "/home/craig/gpu-utils-master/GPUmodules/GPUmodule.py", line 1849, in set_gpu_list
self[gpu_uuid].read_gpu_sensor_set_nv()
File "/home/craig/gpu-utils-master/GPUmodules/GPUmodule.py", line 1304, in read_gpu_sensor_set_nv
if re.fullmatch(PATTERNS['IS_FLOAT'], results[sn_k]):
File "/usr/lib/python3.6/re.py", line 177, in fullmatch
return _compile(pattern, flags).fullmatch(string)
TypeError: expected string or bytes-like object
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Thanks. This may take a few rounds to get it robust. I have just pushed an update. Let me know if it resolves the issue.
from gpu-utils.
KeithMyers
commented on August 28, 2024
Is it just because Craig and I have different libraries loaded that I haven't found any bugs in the apps yet?
Or is it because his GTX750 is a Maxwell family gpu while all mine are Turing and two generations newer?
Is the app failing on looking for sensors that were not implemented on the earlier generations?
I have run through all the parameter options on gpu-ls and nothing has been tripped up yet.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
The original code was based on the functionality of your GPUs. The older GPU used by Craig appears to respond to a subset of the query items valid for your cards. I’m trying to implement a generic approach to deal with this by first reading all items individually, and building a disabled sensor list to ignore in future reads that use a single call with only valid sensors. It also appears that the older card returns invalid results for some queries.
Have you verified that the latest on master works with your system? It would be good to know that the new strategy still works on your cards.
from gpu-utils.
KeithMyers
commented on August 28, 2024
Well, I just uninstalled and reinstalled and got the same version level.
Successfully installed rickslab-gpu-utils-3.4.11
Is that your latest?
All the apps run correctly without errors on my cards.
from gpu-utils.
csecht
commented on August 28, 2024
A different problem now:
~/Desktop/gpu-utils-master$ ./gpu-ls
OS command [nvidia-smi] executable found: [/usr/bin/nvidia-smi]
Traceback (most recent call last):
File "./gpu-ls", line 150, in <module>
main()
File "./gpu-ls", line 98, in main
gpu_list.set_gpu_list(clinfo_flag=True)
File "/home/craig/gpu-utils-master/GPUmodules/GPUmodule.py", line 1849, in set_gpu_list
self[gpu_uuid].read_gpu_sensor_set_nv()
File "/home/craig/gpu-utils-master/GPUmodules/GPUmodule.py", line 1281, in read_gpu_sensor_set_nv
if results['[power.min.limit'] and re.fullmatch(PATTERNS['IS_FLOAT'], results['power.min_limit']):
KeyError: '[power.min.limit'
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Well, I just uninstalled and reinstalled and got the same version level.
Successfully installed rickslab-gpu-utils-3.4.11
Is that your latest?
All the apps run correctly without errors on my cards.
You need to download from GitHub in order to test the code I am working on. I won’t package it until it is verified.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
@csecht
Your latest results looks like nvidia-smi isn't accessible. But before you fix that can you run again with the latest? I won't to make sure it is robust enough to deal with all items not being read.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
@csecht
Your latest results looks like nvidia-smi isn't accessible. But before you fix that can you run again with the latest? I won't to make sure it is robust enough to deal with all items not being read.
Never mind... I read your post to quickly. Actually said it was found. I fixed a typo that should fix the error.
from gpu-utils.
csecht
commented on August 28, 2024
The typo edit didn't fix it:
./gpu-ls
OS command [nvidia-smi] executable found: [/usr/bin/nvidia-smi]
Traceback (most recent call last):
File "./gpu-ls", line 150, in <module>
main()
File "./gpu-ls", line 98, in main
gpu_list.set_gpu_list(clinfo_flag=True)
File "/home/craig/gpu-utils-master/GPUmodules/GPUmodule.py", line 1849, in set_gpu_list
self[gpu_uuid].read_gpu_sensor_set_nv()
File "/home/craig/gpu-utils-master/GPUmodules/GPUmodule.py", line 1281, in read_gpu_sensor_set_nv
if results['power.min.limit'] and re.fullmatch(PATTERNS['IS_FLOAT'], results['power.min_limit']):
KeyError: 'power.min.limit'
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Sorry, just pushed another version. Now it is fixed.
from gpu-utils.
csecht
commented on August 28, 2024
Not fixed yet...
~/Desktop/gpu-utils-master$ ./gpu-ls
OS command [nvidia-smi] executable found: [/usr/bin/nvidia-smi]
Traceback (most recent call last):
File "./gpu-ls", line 150, in <module>
main()
File "./gpu-ls", line 98, in main
gpu_list.set_gpu_list(clinfo_flag=True)
File "/home/craig/gpu-utils-master/GPUmodules/GPUmodule.py", line 1850, in set_gpu_list
self[gpu_uuid].read_gpu_sensor_set_nv()
File "/home/craig/gpu-utils-master/GPUmodules/GPUmodule.py", line 1304, in read_gpu_sensor_set_nv
if results[sn_k] and re.fullmatch(PATTERNS['IS_FLOAT']):
TypeError: fullmatch() missing 1 required positional argument: 'string'
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Surprised the IDE didn't catch that one. I have pushed a fix.
from gpu-utils.
csecht
commented on August 28, 2024
It's hanging on an bad nvidia-smi call
:~/Desktop/gpu-utils-master$ ./gpu-ls
OS command [nvidia-smi] executable found: [/usr/bin/nvidia-smi]
Detected GPUs: INTEL: 1, NVIDIA: 1, AMD: 1
AMD: amdgpu version: 20.10-1048554
AMD: Wattman features enabled: 0xfffd7fff
Traceback (most recent call last):
File "./gpu-ls", line 150, in <module>
main()
File "./gpu-ls", line 121, in main
gpu_list.read_gpu_sensor_set(data_type=Gpu.GpuItem.SensorSet.All)
File "/home/craig/gpu-utils-master/GPUmodules/GPUmodule.py", line 2093, in read_gpu_sensor_set
gpu.read_gpu_sensor_set(data_type)
File "/home/craig/gpu-utils-master/GPUmodules/GPUmodule.py", line 1234, in read_gpu_sensor_set
return self.read_gpu_sensor_set_nv(data_type)
File "/home/craig/gpu-utils-master/GPUmodules/GPUmodule.py", line 1304, in read_gpu_sensor_set_nv
if results[sn_k] and re.fullmatch(PATTERNS['IS_FLOAT'], results[sn_k]):
KeyError: 'temperature.memory'
When run from nvidia-smi:
:~$ /usr/bin/nvidia-smi -i 01:00.0 --query-gpu=temperature.memory --format=csv
Field "temperature.memory" is not a valid field to query.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I have pushed an update. Can you also post a debug log for the next one?
from gpu-utils.
csecht
commented on August 28, 2024
It worked! (U still want the debug? lol)
~/Desktop/gpu-utils-master$ ./gpu-ls --debug
Ubuntu: Validated
OS command [nvidia-smi] executable found: [/usr/bin/nvidia-smi]
Detected GPUs: INTEL: 1, NVIDIA: 1, AMD: 1
AMD: amdgpu version: 20.10-1048554
AMD: Wattman features enabled: 0xfffd7fff
3 total GPUs, 1 rw, 1 r-only, 0 w-only
Card Number: 0
Vendor: INTEL
Readable: False
Writable: False
Compute: False
Device ID: {'device': '0x3e91', 'subsystem_device': '0x8694', 'subsystem_vendor': '0x1043', 'vendor': '0x8086'}
Decoded Device ID: 8th Gen Core Processor Gaussian Mixture Model
Card Model: Intel Corporation 8th Gen Core Processor Gaussian Mixture Model
PCIe ID: 00:02.0
Driver: i915
GPU Type: Unsupported
HWmon: None
Card Path: /sys/class/drm/card0/device
System Card Path: /sys/devices/pci0000:00/0000:00:02.0
Card Number: 1
Vendor: NVIDIA
Readable: True
Writable: False
Compute: True
GPU UID: GPU-fcbaadc4-4040-c2e5-d5b6-52d1547bcc64
GPU S/N: [Not Supported]
Device ID: {'device': '0x1381', 'subsystem_device': '0x1073', 'subsystem_vendor': '0x10de', 'vendor': '0x10de'}
Decoded Device ID: GM107 [GeForce GTX 750]
Card Model: GeForce GTX 750
Display Card Model: GeForce GTX 750
Card Index: 0
PCIe ID: 01:00.0
Link Speed: GEN3
Link Width: 8
##################################################
Driver: 390.138
vBIOS Version: 82.07.32.00.32
Compute Platform: OpenCL 1.2 CUDA
Compute Mode: Default
GPU Type: Supported
HWmon: None
Card Path: /sys/class/drm/card1/device
System Card Path: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0
##################################################
Current Power (W): 1.360
Power Cap (W): 38.50
Power Cap Range (W): [30.0, 38.5]
Fan Target Speed (rpm): None
Current Fan PWM (%): 40.000
##################################################
Current GPU Loading (%): 0
Current Memory Loading (%): 0
Current VRAM Usage (%): 20.387
Current VRAM Used (GB): 0.195
Total VRAM (GB): 0.958
Current Temps (C): {'temperature.gpu': 29.0}
Current Clk Frequencies (MHz): {'clocks.gr': 1019.0, 'clocks.mem': 2505.0, 'clocks.sm': 1019.0, 'clocks.video': 917.0}
Maximum Clk Frequencies (MHz): {'clocks.max.gr': 1293.0, 'clocks.max.mem': 2505.0, 'clocks.max.sm': 1293.0}
Current SCLK P-State: [0, '']
Power Profile Mode: [Not Supported]
Card Number: 2
Vendor: AMD
Readable: True
Writable: True
Compute: False
GPU UID: None
Device ID: {'device': '0x731f', 'subsystem_device': '0xe411', 'subsystem_vendor': '0x1da2', 'vendor': '0x1002'}
Decoded Device ID: Radeon RX 5600 XT
Card Model: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev ca)
Display Card Model: Radeon RX 5600 XT
PCIe ID: 04:00.0
Link Speed: 16 GT/s
Link Width: 16
##################################################
Driver: amdgpu
vBIOS Version: 113-5E4111U-X4G
Compute Platform: None
GPU Type: CurvePts
HWmon: /sys/class/drm/card2/device/hwmon/hwmon3
Card Path: /sys/class/drm/card2/device
System Card Path: /sys/devices/pci0000:00/0000:00:01.1/0000:02:00.0/0000:03:00.0/0000:04:00.0
##################################################
Current Power (W): 7.000
Power Cap (W): 160.000
Power Cap Range (W): [0, 192]
Fan Enable: 0
Fan PWM Mode: [2, 'Dynamic']
Fan Target Speed (rpm): 0
Current Fan Speed (rpm): 0
Current Fan PWM (%): 0
Fan Speed Range (rpm): [0, 3200]
Fan PWM Range (%): [0, 100]
##################################################
Current GPU Loading (%): 0
Current Memory Loading (%): 0
Current GTT Memory Usage (%): 0.218
Current GTT Memory Used (GB): 0.013
Total GTT Memory (GB): 5.984
Current VRAM Usage (%): 0.271
Current VRAM Used (GB): 0.016
Total VRAM (GB): 5.984
Current Temps (C): {'edge': 35.0, 'junction': 35.0, 'mem': 38.0}
Critical Temps (C): {'edge': 118.0, 'junction': 99.0, 'mem': 99.0}
Current Voltages (V): {'vddgfx': 775}
Current Clk Frequencies (MHz): {'mclk': 100.0, 'sclk': 1780.0}
Current SCLK P-State: [2, '1780Mhz']
SCLK Range: ['800Mhz', '1820Mhz']
Current MCLK P-State: [0, '100Mhz']
MCLK Range: ['625Mhz', '930Mhz']
Power Profile Mode: 5-COMPUTE
Power DPM Force Performance Level: manual
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Cool! I found what I think is a redundant read and have removed it. Can you try it again?
from gpu-utils.
csecht
commented on August 28, 2024
Here's the --table:
OS command [nvidia-smi] executable found: [/usr/bin/nvidia-smi]
Detected GPUs: INTEL: 1, NVIDIA: 1, AMD: 1
AMD: amdgpu version: 20.10-1048554
AMD: Wattman features enabled: 0xfffd7fff
3 total GPUs, 1 rw, 1 r-only, 0 w-only
Status of Readable GPUs:
┌─────────────┬────────────────┬────────────────┐
│Card # │card1 │card2 │
├─────────────┼────────────────┼────────────────┤
│Model │GeForce GTX 750 │Radeon RX 5600 X│
│GPU Load % │100 │99 │
│Mem Load % │36 │75 │
│VRAM Usage % │89.501 │11.969 │
│GTT Usage % │None │0.432 │
│Power (W) │14.72 │114.0 │
│Power Cap (W)│38.50 │160.0 │
│Energy (kWh) │0.0 │0.0 │
│T (C) │39.0 │53.0 │
│VddGFX (mV) │0 │931 │
│Fan Spd (%) │40.0 │34 │
│Sclk (MHz) │1163 │1780 │
│Sclk Pstate │0 │2 │
│Mclk (MHz) │2505 │875 │
│Mclk Pstate │0 │3 │
│Perf Mode │[Not Supported] │5-COMPUTE │
└─────────────┴────────────────┴────────────────┘
and the full list
:~/Desktop/gpu-utils-master$ ./gpu-ls
OS command [nvidia-smi] executable found: [/usr/bin/nvidia-smi]
Detected GPUs: INTEL: 1, NVIDIA: 1, AMD: 1
AMD: amdgpu version: 20.10-1048554
AMD: Wattman features enabled: 0xfffd7fff
3 total GPUs, 1 rw, 1 r-only, 0 w-only
Card Number: 0
Vendor: INTEL
Readable: False
Writable: False
Compute: False
Device ID: {'device': '0x3e91', 'subsystem_device': '0x8694', 'subsystem_vendor': '0x1043', 'vendor': '0x8086'}
Decoded Device ID: 8th Gen Core Processor Gaussian Mixture Model
Card Model: Intel Corporation 8th Gen Core Processor Gaussian Mixture Model
PCIe ID: 00:02.0
Driver: i915
GPU Type: Unsupported
HWmon: None
Card Path: /sys/class/drm/card0/device
System Card Path: /sys/devices/pci0000:00/0000:00:02.0
Card Number: 1
Vendor: NVIDIA
Readable: True
Writable: False
Compute: True
GPU UID: GPU-fcbaadc4-4040-c2e5-d5b6-52d1547bcc64
GPU S/N: [Not Supported]
Device ID: {'device': '0x1381', 'subsystem_device': '0x1073', 'subsystem_vendor': '0x10de', 'vendor': '0x10de'}
Decoded Device ID: GM107 [GeForce GTX 750]
Card Model: GeForce GTX 750
Display Card Model: GeForce GTX 750
Card Index: 0
PCIe ID: 01:00.0
Link Speed: GEN3
Link Width: 8
##################################################
Driver: 390.138
vBIOS Version: 82.07.32.00.32
Compute Platform: OpenCL 1.2 CUDA
Compute Mode: Default
GPU Type: Supported
HWmon: None
Card Path: /sys/class/drm/card1/device
System Card Path: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0
##################################################
Current Power (W): 14.860
Power Cap (W): 38.50
Power Cap Range (W): [30.0, 38.5]
Fan Target Speed (rpm): None
Current Fan PWM (%): 40.000
##################################################
Current GPU Loading (%): 100
Current Memory Loading (%): 36
Current VRAM Usage (%): 89.093
Current VRAM Used (GB): 0.854
Total VRAM (GB): 0.958
Current Temps (C): {'temperature.gpu': 42.0, 'temperature.memory': None}
Current Clk Frequencies (MHz): {'clocks.gr': 1163.0, 'clocks.mem': 2505.0, 'clocks.sm': 1163.0, 'clocks.video': 1046.0}
Maximum Clk Frequencies (MHz): {'clocks.max.gr': 1293.0, 'clocks.max.mem': 2505.0, 'clocks.max.sm': 1293.0}
Current SCLK P-State: [0, '']
Power Profile Mode: [Not Supported]
Card Number: 2
Vendor: AMD
Readable: True
Writable: True
Compute: False
GPU UID: None
Device ID: {'device': '0x731f', 'subsystem_device': '0xe411', 'subsystem_vendor': '0x1da2', 'vendor': '0x1002'}
Decoded Device ID: Radeon RX 5600 XT
Card Model: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev ca)
Display Card Model: Radeon RX 5600 XT
PCIe ID: 04:00.0
Link Speed: 16 GT/s
Link Width: 16
##################################################
Driver: amdgpu
vBIOS Version: 113-5E4111U-X4G
Compute Platform: None
GPU Type: CurvePts
HWmon: /sys/class/drm/card2/device/hwmon/hwmon3
Card Path: /sys/class/drm/card2/device
System Card Path: /sys/devices/pci0000:00/0000:00:01.1/0000:02:00.0/0000:03:00.0/0000:04:00.0
##################################################
Current Power (W): 91.000
Power Cap (W): 160.000
Power Cap Range (W): [0, 192]
Fan Enable: 0
Fan PWM Mode: [2, 'Dynamic']
Fan Target Speed (rpm): 1143
Current Fan Speed (rpm): 1143
Current Fan PWM (%): 34
Fan Speed Range (rpm): [0, 3200]
Fan PWM Range (%): [0, 100]
##################################################
Current GPU Loading (%): 84
Current Memory Loading (%): 58
Current GTT Memory Usage (%): 0.432
Current GTT Memory Used (GB): 0.026
Total GTT Memory (GB): 5.984
Current VRAM Usage (%): 11.969
Current VRAM Used (GB): 0.716
Total VRAM (GB): 5.984
Current Temps (C): {'edge': 54.0, 'junction': 61.0, 'mem': 72.0}
Critical Temps (C): {'edge': 118.0, 'junction': 99.0, 'mem': 99.0}
Current Voltages (V): {'vddgfx': 925}
Current Clk Frequencies (MHz): {'mclk': 875.0, 'sclk': 1780.0}
Current SCLK P-State: [2, '1780Mhz']
SCLK Range: ['800Mhz', '1820Mhz']
Current MCLK P-State: [3, '875Mhz']
MCLK Range: ['625Mhz', '930Mhz']
Power Profile Mode: 5-COMPUTE
Power DPM Force Performance Level: manual
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Looks good! Should probably also make sure gpu-plot and gpu-mon --gui still works.
@KeithMyers Can you try the latest on master with your setup?
from gpu-utils.
csecht
commented on August 28, 2024
Yes, both are working. Nice!
In monitor and plot, for the nvidia fields that can't be reported (VddGFX, P-states), do you want zero or something like, 'n/a', 'n/r', or 'unreadable' ? It's just that, at first glance, '0' can be misleading.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
The SCLK p-states should be valid, but NV's are opposite of AMD, where p-state 0 is highest performance. It is a little complicated to make VddGFX something other than numeric, since gpu-plot is a subprocess of `gpu-mon and communication is through a pipe. I will add to my list of things to do, but I will need to rethink some of the foundation for the plot utility.
from gpu-utils.
KeithMyers
commented on August 28, 2024
Rick, I just ran through the latest Beta-Master #4 from the most recent merge and all the apps ran fine on my Turing cards.
The only thing I could think of doing is to just ignore VddGFX somehow. But again, simple enough to just ignore it in the tables or toggle it off in plot too.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I have attempted to address the vddgfx issue by using a numpy nan as the value. Can you give it a try?
from gpu-utils.
KeithMyers
commented on August 28, 2024
Sorry, that did not work. vddgfx is still present in the tables as it was before with a 0 value.
Also plot still has it present. The vddgfx button is still present and toggles the plot line off as before.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Did you use the latest from master? If so, can you generate a debug log file? I don't see in the updated code where it is being set to zero.
from gpu-utils.
KeithMyers
commented on August 28, 2024
Yes, I used the latest from master. Only two hours since last commit. This commit https://github.com/Ricks-Lab/gpu-utils/commit/a89c0f586b73156820006e105a2d3abd64d5be64
DEBUG:gpu-utils:env.set_args:Command line arguments:
Namespace(about=False, clinfo=False, debug=True, no_fan=False, ppm=False, pstates=False, short=False, table=False)
DEBUG:gpu-utils:env.set_args:Local TZ: PDT
DEBUG:gpu-utils:env.set_args:pciid path set to: /usr/share/misc/pci.ids
DEBUG:gpu-utils:env.set_args:Icon path set to: /home/keith/.local/share/rickslab-gpu-utils/icons
DEBUG:gpu-utils:gpu-ls.main:########## gpu-ls 3.4.11
DEBUG:gpu-utils:env.check_env:Using python: 3.8.2
DEBUG:gpu-utils:env.check_env:Using Linux Kernel: 5.4.0-37-generic
DEBUG:gpu-utils:env.check_env:Using Linux Distro: Ubuntu
DEBUG:gpu-utils:env.check_env:Linux Distro Description: Ubuntu 20.04 LTS
DEBUG:gpu-utils:env.check_env:Ubuntu package query tool: /usr/bin/dpkg
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_NAME: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_VERSION: [OpenCL 1.2 CUDA]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DRIVER_VERSION: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_OPENCL_C_VERSION: [OpenCL C 1.2]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:NV ocl_pcie_id [08:00.0]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_COMPUTE_UNITS: [46]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: [3]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_SIZES: [1024 1024 64]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_GROUP_SIZE: [1024]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_KERNEL_PREFERRED_WORK_GROUP_SIZE_MULTIPLE: [32]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_MEM_ALLOC_SIZE: [2092515328]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:cl_index: {'prf_wg_multiple': '32', 'max_wg_size': '1024', 'prf_wg_size': None, 'max_wi_sizes': '1024 1024 64', 'max_wi_dim': '3', 'max_mem_allocation': '2092515328', 'simd_ins_width': None, 'simd_width': None, 'simd_per_cu': None, 'max_cu': '46', 'device_name': 'GeForce RTX 2080', 'opencl_version': 'OpenCL C 1.2', 'driver_version': '440.100', 'device_version': 'OpenCL 1.2 CUDA'}
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_NAME: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_VERSION: [OpenCL 1.2 CUDA]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DRIVER_VERSION: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_OPENCL_C_VERSION: [OpenCL C 1.2]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:NV ocl_pcie_id [0a:00.0]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_COMPUTE_UNITS: [46]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: [3]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_SIZES: [1024 1024 64]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_GROUP_SIZE: [1024]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_KERNEL_PREFERRED_WORK_GROUP_SIZE_MULTIPLE: [32]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_MEM_ALLOC_SIZE: [2091696128]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:cl_index: {'prf_wg_multiple': '32', 'max_wg_size': '1024', 'prf_wg_size': None, 'max_wi_sizes': '1024 1024 64', 'max_wi_dim': '3', 'max_mem_allocation': '2091696128', 'simd_ins_width': None, 'simd_width': None, 'simd_per_cu': None, 'max_cu': '46', 'device_name': 'GeForce RTX 2080', 'opencl_version': 'OpenCL C 1.2', 'driver_version': '440.100', 'device_version': 'OpenCL 1.2 CUDA'}
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_NAME: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_VERSION: [OpenCL 1.2 CUDA]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DRIVER_VERSION: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_OPENCL_C_VERSION: [OpenCL C 1.2]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:NV ocl_pcie_id [0b:00.0]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_COMPUTE_UNITS: [46]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: [3]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_SIZES: [1024 1024 64]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_GROUP_SIZE: [1024]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_KERNEL_PREFERRED_WORK_GROUP_SIZE_MULTIPLE: [32]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_MEM_ALLOC_SIZE: [2092515328]
DEBUG:gpu-utils:GPUmodule.set_gpu_list:OpenCL map: {'08:00.0': {'prf_wg_multiple': '32', 'max_wg_size': '1024', 'prf_wg_size': None, 'max_wi_sizes': '1024 1024 64', 'max_wi_dim': '3', 'max_mem_allocation': '2092515328', 'simd_ins_width': None, 'simd_width': None, 'simd_per_cu': None, 'max_cu': '46', 'device_name': 'GeForce RTX 2080', 'opencl_version': 'OpenCL C 1.2', 'driver_version': '440.100', 'device_version': 'OpenCL 1.2 CUDA'}, '0a:00.0': {'prf_wg_multiple': '32', 'max_wg_size': '1024', 'prf_wg_size': None, 'max_wi_sizes': '1024 1024 64', 'max_wi_dim': '3', 'max_mem_allocation': '2091696128', 'simd_ins_width': None, 'simd_width': None, 'simd_per_cu': None, 'max_cu': '46', 'device_name': 'GeForce RTX 2080', 'opencl_version': 'OpenCL C 1.2', 'driver_version': '440.100', 'device_version': 'OpenCL 1.2 CUDA'}, '0b:00.0': {'prf_wg_multiple': '32', 'max_wg_size': '1024', 'prf_wg_size': None, 'max_wi_sizes': '1024 1024 64', 'max_wi_dim': '3', 'max_mem_allocation': '2092515328', 'simd_ins_width': None, 'simd_width': None, 'simd_per_cu': None, 'max_cu': '46', 'device_name': 'GeForce RTX 2080', 'opencl_version': 'OpenCL C 1.2', 'driver_version': '440.100', 'device_version': 'OpenCL 1.2 CUDA'}}
DEBUG:gpu-utils:env.read_amdfeaturemask:Could not read AMD Featuremask [[Errno 2] No such file or directory: '/sys/module/amdgpu/parameters/ppfeaturemask']
DEBUG:gpu-utils:GPUmodule.get_gpu_pci_list:Found GPU pci: 08:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)
DEBUG:gpu-utils:GPUmodule.get_gpu_pci_list:Found GPU pci: 0a:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)
DEBUG:gpu-utils:GPUmodule.get_gpu_pci_list:Found GPU pci: 0b:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Found 3 GPUs
DEBUG:gpu-utils:GPUmodule.add:Added GPU Item 5fa902384e50446aac226e81da3d62e7 to GPU List
DEBUG:gpu-utils:GPUmodule.set_gpu_list:GPU: 08:00.0
DEBUG:gpu-utils:GPUmodule.set_gpu_list:lspci output items:
['08:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', '\tSubsystem: eVga.com. Corp. TU104 [GeForce RTX 2080 Rev. A]', '\tKernel driver in use: nvidia', '\tKernel modules: nvidiafb, nouveau, nvidia_drm, nvidia', '']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.1/0000:0a:00.0
device_dir: /sys/class/drm/card1/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.2/0000:0b:00.0
device_dir: /sys/class/drm/card2/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:04.0/0000:08:00.0
device_dir: /sys/class/drm/card0/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:card_path set to: /sys/class/drm/card0/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card dir [/sys/class/drm/card0/device] contents:
['uevent', 'resource3_wc', 'resource5', 'resource3', 'broken_parity_status', 'subsystem_device', 'rom', 'dma_mask_bits', 'vendor', 'resource1', 'i2c-17', 'iommu_group', 'local_cpus', 'firmware_node', 'power', 'class', 'reset', 'i2c-15', 'numa_node', 'resource', 'rescan', 'max_link_width', 'msi_bus', 'device', 'i2c-13', 'boot_vga', 'aer_dev_nonfatal', 'current_link_width', 'driver', 'max_link_speed', 'local_cpulist', 'driver_override', 'subsystem', 'd3cold_allowed', 'irq', 'revision', 'current_link_speed', 'i2c-18', 'resource1_wc', 'aer_dev_correctable', 'consistent_dma_mask_bits', 'resource0', 'i2c-16', 'config', 'ari_enabled', 'msi_irqs', 'remove', 'iommu', 'aer_dev_fatal', 'enable', 'link', 'i2c-14', 'modalias', 'i2c-12', 'subsystem_vendor', 'drm']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:HW file search: []
DEBUG:gpu-utils:GPUmodule.populate_prm_from_dict:prm dict:
{'pcie_id': '08:00.0', 'model': 'NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', 'model_short': 'UNKNOWN', 'vendor': <vendor.NVIDIA: 4>, 'driver': 'nvidiafb, nouveau, nvidia_drm, nvidia', 'card_path': '/sys/class/drm/card0/device', 'sys_card_path': '/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:04.0/0000:08:00.0', 'gpu_type': <type.Supported: 3>, 'hwmon_path': '', 'readable': True, 'writable': False, 'compute': True, 'compute_platform': 'OpenCL 1.2 CUDA'}
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card flags: readable: True, writable: False, type: Supported
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_generic:sensor path set to [/sys/class/drm/card0/device]
DEBUG:gpu-utils:GPUmodule.read_pciid_model:Logger active in module
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=power.limit,power.min_limit,power.max_limit,memory.total,vbios_version,driver_version,compute_mode,name,serial,index,gpu_uuid,power.draw,temperature.gpu,temperature.memory,clocks.gr,clocks.sm,clocks.mem,clocks.video,clocks.max.gr,clocks.max.sm,clocks.max.mem,utilization.gpu,utilization.memory,memory.used,fan.speed,gom.current,pcie.link.width.current,pcie.link.gen.current,pstate --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: [['200.00, 105.00, 292.00, 7982, 90.04.23.00.5F, 440.100, Default, GeForce RTX 2080, [N/A], 0, GPU-089608fe-cba5-4711-bf68-085fd0711d8c, 100.83, 44, N/A, 2010, 2010, 7199, 1860, 2160, 2160, 7000, 100, 4, 1142, 100, [N/A], 4, 2, P2', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: {'power.limit': '200.00', 'power.min_limit': '105.00', 'power.max_limit': '292.00', 'memory.total': '7982', 'vbios_version': '90.04.23.00.5F', 'driver_version': '440.100', 'compute_mode': 'Default', 'name': 'GeForce RTX 2080', 'serial': '[N/A]', 'index': '0', 'gpu_uuid': 'GPU-089608fe-cba5-4711-bf68-085fd0711d8c', 'power.draw': '100.83', 'temperature.gpu': '44', 'temperature.memory': 'N/A', 'clocks.gr': '2010', 'clocks.sm': '2010', 'clocks.mem': '7199', 'clocks.video': '1860', 'clocks.max.gr': '2160', 'clocks.max.sm': '2160', 'clocks.max.mem': '7000', 'utilization.gpu': '100', 'utilization.memory': '4', 'memory.used': '1142', 'fan.speed': '100', 'gom.current': '[N/A]', 'pcie.link.width.current': '4', 'pcie.link.gen.current': '2', 'pstate': 'P2'}
DEBUG:gpu-utils:GPUmodule.add:Added GPU Item 076a672142d94878abf73b72d12a75f0 to GPU List
DEBUG:gpu-utils:GPUmodule.set_gpu_list:GPU: 0a:00.0
DEBUG:gpu-utils:GPUmodule.set_gpu_list:lspci output items:
['0a:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', '\tSubsystem: eVga.com. Corp. TU104 [GeForce RTX 2080 Rev. A]', '\tKernel driver in use: nvidia', '\tKernel modules: nvidiafb, nouveau, nvidia_drm, nvidia', '']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.1/0000:0a:00.0
device_dir: /sys/class/drm/card1/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:card_path set to: /sys/class/drm/card1/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.2/0000:0b:00.0
device_dir: /sys/class/drm/card2/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:04.0/0000:08:00.0
device_dir: /sys/class/drm/card0/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card dir [/sys/class/drm/card1/device] contents:
['uevent', 'resource3_wc', 'resource5', 'i2c-10', 'resource3', 'broken_parity_status', 'subsystem_device', 'rom', 'dma_mask_bits', 'vendor', 'resource1', 'iommu_group', 'local_cpus', 'firmware_node', 'i2c-8', 'power', 'class', 'reset', 'numa_node', 'resource', 'rescan', 'i2c-6', 'max_link_width', 'msi_bus', 'device', 'boot_vga', 'aer_dev_nonfatal', 'current_link_width', 'i2c-11', 'driver', 'max_link_speed', 'local_cpulist', 'driver_override', 'subsystem', 'd3cold_allowed', 'irq', 'revision', 'current_link_speed', 'resource1_wc', 'i2c-9', 'aer_dev_correctable', 'consistent_dma_mask_bits', 'resource0', 'config', 'ari_enabled', 'msi_irqs', 'remove', 'i2c-7', 'iommu', 'aer_dev_fatal', 'enable', 'link', 'i2c-5', 'modalias', 'subsystem_vendor', 'drm']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:HW file search: []
DEBUG:gpu-utils:GPUmodule.populate_prm_from_dict:prm dict:
{'pcie_id': '0a:00.0', 'model': 'NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', 'model_short': 'UNKNOWN', 'vendor': <vendor.NVIDIA: 4>, 'driver': 'nvidiafb, nouveau, nvidia_drm, nvidia', 'card_path': '/sys/class/drm/card1/device', 'sys_card_path': '/sys/devices/pci0000:00/0000:00:03.1/0000:0a:00.0', 'gpu_type': <type.Supported: 3>, 'hwmon_path': '', 'readable': True, 'writable': False, 'compute': True, 'compute_platform': 'OpenCL 1.2 CUDA'}
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card flags: readable: True, writable: False, type: Supported
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_generic:sensor path set to [/sys/class/drm/card1/device]
DEBUG:gpu-utils:GPUmodule.read_pciid_model:Logger active in module
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=power.limit,power.min_limit,power.max_limit,memory.total,vbios_version,driver_version,compute_mode,name,serial,index,gpu_uuid,power.draw,temperature.gpu,temperature.memory,clocks.gr,clocks.sm,clocks.mem,clocks.video,clocks.max.gr,clocks.max.sm,clocks.max.mem,utilization.gpu,utilization.memory,memory.used,fan.speed,gom.current,pcie.link.width.current,pcie.link.gen.current,pstate --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: [['200.00, 105.00, 292.00, 7979, 90.04.23.00.5F, 440.100, Default, GeForce RTX 2080, [N/A], 1, GPU-22b2c6ac-2d49-4863-197c-9c469071178a, 182.93, 44, N/A, 1980, 1980, 7199, 1830, 2160, 2160, 7000, 89, 57, 3765, 100, [N/A], 8, 3, P2', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: {'power.limit': '200.00', 'power.min_limit': '105.00', 'power.max_limit': '292.00', 'memory.total': '7979', 'vbios_version': '90.04.23.00.5F', 'driver_version': '440.100', 'compute_mode': 'Default', 'name': 'GeForce RTX 2080', 'serial': '[N/A]', 'index': '1', 'gpu_uuid': 'GPU-22b2c6ac-2d49-4863-197c-9c469071178a', 'power.draw': '182.93', 'temperature.gpu': '44', 'temperature.memory': 'N/A', 'clocks.gr': '1980', 'clocks.sm': '1980', 'clocks.mem': '7199', 'clocks.video': '1830', 'clocks.max.gr': '2160', 'clocks.max.sm': '2160', 'clocks.max.mem': '7000', 'utilization.gpu': '89', 'utilization.memory': '57', 'memory.used': '3765', 'fan.speed': '100', 'gom.current': '[N/A]', 'pcie.link.width.current': '8', 'pcie.link.gen.current': '3', 'pstate': 'P2'}
DEBUG:gpu-utils:GPUmodule.add:Added GPU Item 77da83d87a2a4660ba76663e8171bf02 to GPU List
DEBUG:gpu-utils:GPUmodule.set_gpu_list:GPU: 0b:00.0
DEBUG:gpu-utils:GPUmodule.set_gpu_list:lspci output items:
['0b:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', '\tSubsystem: eVga.com. Corp. TU104 [GeForce RTX 2080 Rev. A]', '\tKernel driver in use: nvidia', '\tKernel modules: nvidiafb, nouveau, nvidia_drm, nvidia', '']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.1/0000:0a:00.0
device_dir: /sys/class/drm/card1/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.2/0000:0b:00.0
device_dir: /sys/class/drm/card2/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:card_path set to: /sys/class/drm/card2/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:04.0/0000:08:00.0
device_dir: /sys/class/drm/card0/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card dir [/sys/class/drm/card2/device] contents:
['uevent', 'resource3_wc', 'resource5', 'i2c-20', 'resource3', 'i2c-19', 'broken_parity_status', 'subsystem_device', 'rom', 'dma_mask_bits', 'vendor', 'resource1', 'iommu_group', 'local_cpus', 'firmware_node', 'power', 'i2c-25', 'class', 'reset', 'numa_node', 'resource', 'rescan', 'max_link_width', 'msi_bus', 'i2c-23', 'device', 'boot_vga', 'aer_dev_nonfatal', 'i2c-21', 'current_link_width', 'driver', 'max_link_speed', 'local_cpulist', 'driver_override', 'subsystem', 'd3cold_allowed', 'irq', 'revision', 'current_link_speed', 'resource1_wc', 'aer_dev_correctable', 'consistent_dma_mask_bits', 'resource0', 'config', 'ari_enabled', 'msi_irqs', 'remove', 'iommu', 'aer_dev_fatal', 'i2c-24', 'enable', 'link', 'i2c-22', 'modalias', 'subsystem_vendor', 'drm']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:HW file search: []
DEBUG:gpu-utils:GPUmodule.populate_prm_from_dict:prm dict:
{'pcie_id': '0b:00.0', 'model': 'NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', 'model_short': 'UNKNOWN', 'vendor': <vendor.NVIDIA: 4>, 'driver': 'nvidiafb, nouveau, nvidia_drm, nvidia', 'card_path': '/sys/class/drm/card2/device', 'sys_card_path': '/sys/devices/pci0000:00/0000:00:03.2/0000:0b:00.0', 'gpu_type': <type.Supported: 3>, 'hwmon_path': '', 'readable': True, 'writable': False, 'compute': True, 'compute_platform': 'OpenCL 1.2 CUDA'}
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card flags: readable: True, writable: False, type: Supported
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_generic:sensor path set to [/sys/class/drm/card2/device]
DEBUG:gpu-utils:GPUmodule.read_pciid_model:Logger active in module
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=power.limit,power.min_limit,power.max_limit,memory.total,vbios_version,driver_version,compute_mode,name,serial,index,gpu_uuid,power.draw,temperature.gpu,temperature.memory,clocks.gr,clocks.sm,clocks.mem,clocks.video,clocks.max.gr,clocks.max.sm,clocks.max.mem,utilization.gpu,utilization.memory,memory.used,fan.speed,gom.current,pcie.link.width.current,pcie.link.gen.current,pstate --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: [['200.00, 105.00, 292.00, 7982, 90.04.23.00.5F, 440.100, Default, GeForce RTX 2080, [N/A], 2, GPU-6933bcb7-7072-2181-a92f-0e5c42c3fa0d, 202.45, 50, N/A, 1935, 1935, 7199, 1785, 2160, 2160, 7000, 97, 24, 305, 100, [N/A], 8, 3, P2', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: {'power.limit': '200.00', 'power.min_limit': '105.00', 'power.max_limit': '292.00', 'memory.total': '7982', 'vbios_version': '90.04.23.00.5F', 'driver_version': '440.100', 'compute_mode': 'Default', 'name': 'GeForce RTX 2080', 'serial': '[N/A]', 'index': '2', 'gpu_uuid': 'GPU-6933bcb7-7072-2181-a92f-0e5c42c3fa0d', 'power.draw': '202.45', 'temperature.gpu': '50', 'temperature.memory': 'N/A', 'clocks.gr': '1935', 'clocks.sm': '1935', 'clocks.mem': '7199', 'clocks.video': '1785', 'clocks.max.gr': '2160', 'clocks.max.sm': '2160', 'clocks.max.mem': '7000', 'utilization.gpu': '97', 'utilization.memory': '24', 'memory.used': '305', 'fan.speed': '100', 'gom.current': '[N/A]', 'pcie.link.width.current': '8', 'pcie.link.gen.current': '3', 'pstate': 'P2'}
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=power.limit,power.min_limit,power.max_limit,memory.total,vbios_version,driver_version,compute_mode,name,serial,index,gpu_uuid,power.draw,temperature.gpu,temperature.memory,clocks.gr,clocks.sm,clocks.mem,clocks.video,clocks.max.gr,clocks.max.sm,clocks.max.mem,utilization.gpu,utilization.memory,memory.used,fan.speed,gom.current,pcie.link.width.current,pcie.link.gen.current,pstate --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: [['200.00, 105.00, 292.00, 7982, 90.04.23.00.5F, 440.100, Default, GeForce RTX 2080, [N/A], 0, GPU-089608fe-cba5-4711-bf68-085fd0711d8c, 101.24, 44, N/A, 2010, 2010, 7199, 1860, 2160, 2160, 7000, 100, 4, 1142, 100, [N/A], 4, 2, P2', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: {'power.limit': '200.00', 'power.min_limit': '105.00', 'power.max_limit': '292.00', 'memory.total': '7982', 'vbios_version': '90.04.23.00.5F', 'driver_version': '440.100', 'compute_mode': 'Default', 'name': 'GeForce RTX 2080', 'serial': '[N/A]', 'index': '0', 'gpu_uuid': 'GPU-089608fe-cba5-4711-bf68-085fd0711d8c', 'power.draw': '101.24', 'temperature.gpu': '44', 'temperature.memory': 'N/A', 'clocks.gr': '2010', 'clocks.sm': '2010', 'clocks.mem': '7199', 'clocks.video': '1860', 'clocks.max.gr': '2160', 'clocks.max.sm': '2160', 'clocks.max.mem': '7000', 'utilization.gpu': '100', 'utilization.memory': '4', 'memory.used': '1142', 'fan.speed': '100', 'gom.current': '[N/A]', 'pcie.link.width.current': '4', 'pcie.link.gen.current': '2', 'pstate': 'P2'}
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=power.limit,power.min_limit,power.max_limit,memory.total,vbios_version,driver_version,compute_mode,name,serial,index,gpu_uuid,power.draw,temperature.gpu,temperature.memory,clocks.gr,clocks.sm,clocks.mem,clocks.video,clocks.max.gr,clocks.max.sm,clocks.max.mem,utilization.gpu,utilization.memory,memory.used,fan.speed,gom.current,pcie.link.width.current,pcie.link.gen.current,pstate --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: [['200.00, 105.00, 292.00, 7979, 90.04.23.00.5F, 440.100, Default, GeForce RTX 2080, [N/A], 1, GPU-22b2c6ac-2d49-4863-197c-9c469071178a, 187.93, 44, N/A, 1980, 1980, 7199, 1830, 2160, 2160, 7000, 89, 57, 3765, 100, [N/A], 8, 3, P2', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: {'power.limit': '200.00', 'power.min_limit': '105.00', 'power.max_limit': '292.00', 'memory.total': '7979', 'vbios_version': '90.04.23.00.5F', 'driver_version': '440.100', 'compute_mode': 'Default', 'name': 'GeForce RTX 2080', 'serial': '[N/A]', 'index': '1', 'gpu_uuid': 'GPU-22b2c6ac-2d49-4863-197c-9c469071178a', 'power.draw': '187.93', 'temperature.gpu': '44', 'temperature.memory': 'N/A', 'clocks.gr': '1980', 'clocks.sm': '1980', 'clocks.mem': '7199', 'clocks.video': '1830', 'clocks.max.gr': '2160', 'clocks.max.sm': '2160', 'clocks.max.mem': '7000', 'utilization.gpu': '89', 'utilization.memory': '57', 'memory.used': '3765', 'fan.speed': '100', 'gom.current': '[N/A]', 'pcie.link.width.current': '8', 'pcie.link.gen.current': '3', 'pstate': 'P2'}
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=power.limit,power.min_limit,power.max_limit,memory.total,vbios_version,driver_version,compute_mode,name,serial,index,gpu_uuid,power.draw,temperature.gpu,temperature.memory,clocks.gr,clocks.sm,clocks.mem,clocks.video,clocks.max.gr,clocks.max.sm,clocks.max.mem,utilization.gpu,utilization.memory,memory.used,fan.speed,gom.current,pcie.link.width.current,pcie.link.gen.current,pstate --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: [['200.00, 105.00, 292.00, 7982, 90.04.23.00.5F, 440.100, Default, GeForce RTX 2080, [N/A], 2, GPU-6933bcb7-7072-2181-a92f-0e5c42c3fa0d, 202.45, 50, N/A, 1935, 1935, 7199, 1785, 2160, 2160, 7000, 97, 24, 305, 100, [N/A], 8, 3, P2', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: {'power.limit': '200.00', 'power.min_limit': '105.00', 'power.max_limit': '292.00', 'memory.total': '7982', 'vbios_version': '90.04.23.00.5F', 'driver_version': '440.100', 'compute_mode': 'Default', 'name': 'GeForce RTX 2080', 'serial': '[N/A]', 'index': '2', 'gpu_uuid': 'GPU-6933bcb7-7072-2181-a92f-0e5c42c3fa0d', 'power.draw': '202.45', 'temperature.gpu': '50', 'temperature.memory': 'N/A', 'clocks.gr': '1935', 'clocks.sm': '1935', 'clocks.mem': '7199', 'clocks.video': '1785', 'clocks.max.gr': '2160', 'clocks.max.sm': '2160', 'clocks.max.mem': '7000', 'utilization.gpu': '97', 'utilization.memory': '24', 'memory.used': '305', 'fan.speed': '100', 'gom.current': '[N/A]', 'pcie.link.width.current': '8', 'pcie.link.gen.current': '3', 'pstate': 'P2'}
from gpu-utils.
KeithMyers
commented on August 28, 2024
┌─────────────┬────────────────┬────────────────┬────────────────┐
│Card # │card0 │card1 │card2 │
├─────────────┼────────────────┼────────────────┼────────────────┤
│Model │GeForce RTX 2080│GeForce RTX 2080│GeForce RTX 2080│
│GPU Load % │100 │86 │96 │
│Mem Load % │4 │68 │24 │
│VRAM Usage % │10.06 │47.299 │3.821 │
│GTT Usage % │None │None │None │
│Power (W) │100.97 │190.97 │197.33 │
│Power Cap (W)│200.00 │200.00 │200.00 │
│Energy (kWh) │0.0 │0.0 │0.0 │
│T (C) │44.0 │44.0 │50.0 │
│VddGFX (mV) │0 │0 │0 │
│Fan Spd (%) │100.0 │100.0 │100.0 │
│Sclk (MHz) │2010 │1980 │1920 │
│Sclk Pstate │2 │2 │2 │
│Mclk (MHz) │7199 │7199 │7199 │
│Mclk Pstate │2 │2 │2 │
│Perf Mode │[N/A] │[N/A] │[N/A] │
└─────────────┴────────────────┴────────────────┴────────────────┘
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Perhaps it is running the tool from your path instead of the one your local copy of the repository:
DEBUG:gpu-utils:gpu-ls.main:########## gpu-ls 3.4.11
Your debug log is showing version 3.4.11, but master is 3.4.12. Here is the first few lines of my debug log:
DEBUG:gpu-utils:env.set_args:Command line arguments:
Namespace(about=False, clinfo=False, debug=True, no_fan=False, ppm=False, pstates=False, short=False, table=False)
DEBUG:gpu-utils:env.set_args:Local TZ: CST
DEBUG:gpu-utils:env.set_args:pciid path set to: /usr/share/misc/pci.ids
DEBUG:gpu-utils:env.set_args:Icon path set to: /home/rick/pydev/gpu-utils/GPUmodules/../icons
DEBUG:gpu-utils:gpu-ls.main:########## gpu-ls 3.4.12
I suggest to git clone from master with:
git clone https://github.com/Ricks-Lab/gpu-utils.git
To verify the version you are running execute gpu-ls --about
from gpu-utils.
KeithMyers
commented on August 28, 2024
OK, used git.
Author: RueiKe
Copyright: Copyright (C) 2019 RicksLab
Credits:
Craig Echt - Testing, Debug, Verification, and Documentation
Keith Myers - Testing, Debug, Verification of NV Capability
License: GNU General Public License
Version: 3.4.12
Maintainer: RueiKe
Status: Development Status :: 4 - Beta
Now I have nan for vddgfx in the table. And the vddgfx does not show up in plot now.
DEBUG:gpu-utils:env.set_args:Command line arguments:
Namespace(about=False, clinfo=False, debug=True, no_fan=False, ppm=False, pstates=False, short=False, table=False)
DEBUG:gpu-utils:env.set_args:Local TZ: PDT
DEBUG:gpu-utils:env.set_args:pciid path set to: /usr/share/misc/pci.ids
DEBUG:gpu-utils:env.set_args:Icon path set to: /home/keith/Downloads/gpu-utils/GPUmodules/../icons
DEBUG:gpu-utils:gpu-ls.main:########## gpu-ls 3.4.12
DEBUG:gpu-utils:env.check_env:Using python: 3.8.2
DEBUG:gpu-utils:env.check_env:Using Linux Kernel: 5.4.0-37-generic
DEBUG:gpu-utils:env.check_env:Using Linux Distro: Ubuntu
DEBUG:gpu-utils:env.check_env:Linux Distro Description: Ubuntu 20.04 LTS
DEBUG:gpu-utils:env.check_env:Ubuntu package query tool: /usr/bin/dpkg
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_NAME: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_VERSION: [OpenCL 1.2 CUDA]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DRIVER_VERSION: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_OPENCL_C_VERSION: [OpenCL C 1.2]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:NV ocl_pcie_id [08:00.0]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_COMPUTE_UNITS: [46]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: [3]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_SIZES: [1024 1024 64]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_GROUP_SIZE: [1024]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_KERNEL_PREFERRED_WORK_GROUP_SIZE_MULTIPLE: [32]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_MEM_ALLOC_SIZE: [2092515328]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:cl_index: {'prf_wg_multiple': '32', 'max_wg_size': '1024', 'prf_wg_size': None, 'max_wi_sizes': '1024 1024 64', 'max_wi_dim': '3', 'max_mem_allocation': '2092515328', 'simd_ins_width': None, 'simd_width': None, 'simd_per_cu': None, 'max_cu': '46', 'device_name': 'GeForce RTX 2080', 'opencl_version': 'OpenCL C 1.2', 'driver_version': '440.100', 'device_version': 'OpenCL 1.2 CUDA'}
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_NAME: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_VERSION: [OpenCL 1.2 CUDA]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DRIVER_VERSION: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_OPENCL_C_VERSION: [OpenCL C 1.2]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:NV ocl_pcie_id [0a:00.0]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_COMPUTE_UNITS: [46]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: [3]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_SIZES: [1024 1024 64]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_GROUP_SIZE: [1024]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_KERNEL_PREFERRED_WORK_GROUP_SIZE_MULTIPLE: [32]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_MEM_ALLOC_SIZE: [2091696128]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:cl_index: {'prf_wg_multiple': '32', 'max_wg_size': '1024', 'prf_wg_size': None, 'max_wi_sizes': '1024 1024 64', 'max_wi_dim': '3', 'max_mem_allocation': '2091696128', 'simd_ins_width': None, 'simd_width': None, 'simd_per_cu': None, 'max_cu': '46', 'device_name': 'GeForce RTX 2080', 'opencl_version': 'OpenCL C 1.2', 'driver_version': '440.100', 'device_version': 'OpenCL 1.2 CUDA'}
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_NAME: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_VERSION: [OpenCL 1.2 CUDA]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DRIVER_VERSION: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_OPENCL_C_VERSION: [OpenCL C 1.2]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:NV ocl_pcie_id [0b:00.0]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_COMPUTE_UNITS: [46]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: [3]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_ITEM_SIZES: [1024 1024 64]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_WORK_GROUP_SIZE: [1024]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_KERNEL_PREFERRED_WORK_GROUP_SIZE_MULTIPLE: [32]
DEBUG:gpu-utils:GPUmodule.read_gpu_opencl_data:openCL map CL_DEVICE_MAX_MEM_ALLOC_SIZE: [2092515328]
DEBUG:gpu-utils:GPUmodule.set_gpu_list:OpenCL map: {'08:00.0': {'prf_wg_multiple': '32', 'max_wg_size': '1024', 'prf_wg_size': None, 'max_wi_sizes': '1024 1024 64', 'max_wi_dim': '3', 'max_mem_allocation': '2092515328', 'simd_ins_width': None, 'simd_width': None, 'simd_per_cu': None, 'max_cu': '46', 'device_name': 'GeForce RTX 2080', 'opencl_version': 'OpenCL C 1.2', 'driver_version': '440.100', 'device_version': 'OpenCL 1.2 CUDA'}, '0a:00.0': {'prf_wg_multiple': '32', 'max_wg_size': '1024', 'prf_wg_size': None, 'max_wi_sizes': '1024 1024 64', 'max_wi_dim': '3', 'max_mem_allocation': '2091696128', 'simd_ins_width': None, 'simd_width': None, 'simd_per_cu': None, 'max_cu': '46', 'device_name': 'GeForce RTX 2080', 'opencl_version': 'OpenCL C 1.2', 'driver_version': '440.100', 'device_version': 'OpenCL 1.2 CUDA'}, '0b:00.0': {'prf_wg_multiple': '32', 'max_wg_size': '1024', 'prf_wg_size': None, 'max_wi_sizes': '1024 1024 64', 'max_wi_dim': '3', 'max_mem_allocation': '2092515328', 'simd_ins_width': None, 'simd_width': None, 'simd_per_cu': None, 'max_cu': '46', 'device_name': 'GeForce RTX 2080', 'opencl_version': 'OpenCL C 1.2', 'driver_version': '440.100', 'device_version': 'OpenCL 1.2 CUDA'}}
DEBUG:gpu-utils:env.read_amdfeaturemask:Could not read AMD Featuremask [[Errno 2] No such file or directory: '/sys/module/amdgpu/parameters/ppfeaturemask']
DEBUG:gpu-utils:GPUmodule.get_gpu_pci_list:Found GPU pci: 08:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)
DEBUG:gpu-utils:GPUmodule.get_gpu_pci_list:Found GPU pci: 0a:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)
DEBUG:gpu-utils:GPUmodule.get_gpu_pci_list:Found GPU pci: 0b:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Found 3 GPUs
DEBUG:gpu-utils:GPUmodule.add:Added GPU Item 3437d7451f0e4b5c8d11b371c7b4ca72 to GPU List
DEBUG:gpu-utils:GPUmodule.set_gpu_list:GPU: 08:00.0
DEBUG:gpu-utils:GPUmodule.set_gpu_list:lspci output items:
['08:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', '\tSubsystem: eVga.com. Corp. TU104 [GeForce RTX 2080 Rev. A]', '\tKernel driver in use: nvidia', '\tKernel modules: nvidiafb, nouveau, nvidia_drm, nvidia', '']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.1/0000:0a:00.0
device_dir: /sys/class/drm/card1/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.2/0000:0b:00.0
device_dir: /sys/class/drm/card2/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:04.0/0000:08:00.0
device_dir: /sys/class/drm/card0/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:card_path set to: /sys/class/drm/card0/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card dir [/sys/class/drm/card0/device] contents:
['uevent', 'resource3_wc', 'resource5', 'resource3', 'broken_parity_status', 'subsystem_device', 'rom', 'dma_mask_bits', 'vendor', 'resource1', 'i2c-17', 'iommu_group', 'local_cpus', 'firmware_node', 'power', 'class', 'reset', 'i2c-15', 'numa_node', 'resource', 'rescan', 'max_link_width', 'msi_bus', 'device', 'i2c-13', 'boot_vga', 'aer_dev_nonfatal', 'current_link_width', 'driver', 'max_link_speed', 'local_cpulist', 'driver_override', 'subsystem', 'd3cold_allowed', 'irq', 'revision', 'current_link_speed', 'i2c-18', 'resource1_wc', 'aer_dev_correctable', 'consistent_dma_mask_bits', 'resource0', 'i2c-16', 'config', 'ari_enabled', 'msi_irqs', 'remove', 'iommu', 'aer_dev_fatal', 'enable', 'link', 'i2c-14', 'modalias', 'i2c-12', 'subsystem_vendor', 'drm']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:HW file search: []
DEBUG:gpu-utils:GPUmodule.populate_prm_from_dict:prm dict:
{'pcie_id': '08:00.0', 'model': 'NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', 'vendor': <vendor.NVIDIA: 4>, 'driver': 'nvidiafb, nouveau, nvidia_drm, nvidia', 'card_path': '/sys/class/drm/card0/device', 'sys_card_path': '/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:04.0/0000:08:00.0', 'gpu_type': <type.Supported: 3>, 'hwmon_path': '', 'readable': True, 'writable': False, 'compute': True, 'compute_platform': 'OpenCL 1.2 CUDA'}
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card flags: readable: True, writable: False, type: Supported
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_generic:sensor path set to [/sys/class/drm/card0/device]
DEBUG:gpu-utils:GPUmodule.read_pciid_model:Logger active in module
DEBUG:gpu-utils:GPUmodule.add:Added GPU Item df3c1c89015f4441b2c8c9551f69795e to GPU List
DEBUG:gpu-utils:GPUmodule.set_gpu_list:GPU: 0a:00.0
DEBUG:gpu-utils:GPUmodule.set_gpu_list:lspci output items:
['0a:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', '\tSubsystem: eVga.com. Corp. TU104 [GeForce RTX 2080 Rev. A]', '\tKernel driver in use: nvidia', '\tKernel modules: nvidiafb, nouveau, nvidia_drm, nvidia', '']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.1/0000:0a:00.0
device_dir: /sys/class/drm/card1/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:card_path set to: /sys/class/drm/card1/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.2/0000:0b:00.0
device_dir: /sys/class/drm/card2/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:04.0/0000:08:00.0
device_dir: /sys/class/drm/card0/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card dir [/sys/class/drm/card1/device] contents:
['uevent', 'resource3_wc', 'resource5', 'i2c-10', 'resource3', 'broken_parity_status', 'subsystem_device', 'rom', 'dma_mask_bits', 'vendor', 'resource1', 'iommu_group', 'local_cpus', 'firmware_node', 'i2c-8', 'power', 'class', 'reset', 'numa_node', 'resource', 'rescan', 'i2c-6', 'max_link_width', 'msi_bus', 'device', 'boot_vga', 'aer_dev_nonfatal', 'current_link_width', 'i2c-11', 'driver', 'max_link_speed', 'local_cpulist', 'driver_override', 'subsystem', 'd3cold_allowed', 'irq', 'revision', 'current_link_speed', 'resource1_wc', 'i2c-9', 'aer_dev_correctable', 'consistent_dma_mask_bits', 'resource0', 'config', 'ari_enabled', 'msi_irqs', 'remove', 'i2c-7', 'iommu', 'aer_dev_fatal', 'enable', 'link', 'i2c-5', 'modalias', 'subsystem_vendor', 'drm']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:HW file search: []
DEBUG:gpu-utils:GPUmodule.populate_prm_from_dict:prm dict:
{'pcie_id': '0a:00.0', 'model': 'NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', 'vendor': <vendor.NVIDIA: 4>, 'driver': 'nvidiafb, nouveau, nvidia_drm, nvidia', 'card_path': '/sys/class/drm/card1/device', 'sys_card_path': '/sys/devices/pci0000:00/0000:00:03.1/0000:0a:00.0', 'gpu_type': <type.Supported: 3>, 'hwmon_path': '', 'readable': True, 'writable': False, 'compute': True, 'compute_platform': 'OpenCL 1.2 CUDA'}
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card flags: readable: True, writable: False, type: Supported
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_generic:sensor path set to [/sys/class/drm/card1/device]
DEBUG:gpu-utils:GPUmodule.read_pciid_model:Logger active in module
DEBUG:gpu-utils:GPUmodule.add:Added GPU Item b1fd1aecf1cf47e29e345cbedebc95de to GPU List
DEBUG:gpu-utils:GPUmodule.set_gpu_list:GPU: 0b:00.0
DEBUG:gpu-utils:GPUmodule.set_gpu_list:lspci output items:
['0b:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', '\tSubsystem: eVga.com. Corp. TU104 [GeForce RTX 2080 Rev. A]', '\tKernel driver in use: nvidia', '\tKernel modules: nvidiafb, nouveau, nvidia_drm, nvidia', '']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.1/0000:0a:00.0
device_dir: /sys/class/drm/card1/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:03.2/0000:0b:00.0
device_dir: /sys/class/drm/card2/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:card_path set to: /sys/class/drm/card2/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:sysfpath: /sys/devices/pci0000:00/0000:00:01.3/0000:02:00.2/0000:03:04.0/0000:08:00.0
device_dir: /sys/class/drm/card0/device
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card dir [/sys/class/drm/card2/device] contents:
['uevent', 'resource3_wc', 'resource5', 'i2c-20', 'resource3', 'i2c-19', 'broken_parity_status', 'subsystem_device', 'rom', 'dma_mask_bits', 'vendor', 'resource1', 'iommu_group', 'local_cpus', 'firmware_node', 'power', 'i2c-25', 'class', 'reset', 'numa_node', 'resource', 'rescan', 'max_link_width', 'msi_bus', 'i2c-23', 'device', 'boot_vga', 'aer_dev_nonfatal', 'i2c-21', 'current_link_width', 'driver', 'max_link_speed', 'local_cpulist', 'driver_override', 'subsystem', 'd3cold_allowed', 'irq', 'revision', 'current_link_speed', 'resource1_wc', 'aer_dev_correctable', 'consistent_dma_mask_bits', 'resource0', 'config', 'ari_enabled', 'msi_irqs', 'remove', 'iommu', 'aer_dev_fatal', 'i2c-24', 'enable', 'link', 'i2c-22', 'modalias', 'subsystem_vendor', 'drm']
DEBUG:gpu-utils:GPUmodule.set_gpu_list:HW file search: []
DEBUG:gpu-utils:GPUmodule.populate_prm_from_dict:prm dict:
{'pcie_id': '0b:00.0', 'model': 'NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)', 'vendor': <vendor.NVIDIA: 4>, 'driver': 'nvidiafb, nouveau, nvidia_drm, nvidia', 'card_path': '/sys/class/drm/card2/device', 'sys_card_path': '/sys/devices/pci0000:00/0000:00:03.2/0000:0b:00.0', 'gpu_type': <type.Supported: 3>, 'hwmon_path': '', 'readable': True, 'writable': False, 'compute': True, 'compute_platform': 'OpenCL 1.2 CUDA'}
DEBUG:gpu-utils:GPUmodule.set_gpu_list:Card flags: readable: True, writable: False, type: Supported
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_generic:sensor path set to [/sys/class/drm/card2/device]
DEBUG:gpu-utils:GPUmodule.read_pciid_model:Logger active in module
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=power.limit --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['200.00', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [200.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.limit], result: [200.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=power.min_limit --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['105.00', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [105.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.min_limit], result: [105.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=power.max_limit --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['292.00', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [292.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.max_limit], result: [292.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=memory.total --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['7982', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [7982]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [memory.total], result: [7982]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=vbios_version --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['90.04.23.00.5F', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [90.04.23.00.5F]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [vbios_version], result: [90.04.23.00.5F]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=driver_version --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['440.100', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [driver_version], result: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=compute_mode --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['Default', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [Default]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [compute_mode], result: [Default]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=name --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['GeForce RTX 2080', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [name], result: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=serial --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['[N/A]', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [serial], result: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=index --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['0', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [0]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [index], result: [0]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=gpu_uuid --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['GPU-089608fe-cba5-4711-bf68-085fd0711d8c', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [GPU-089608fe-cba5-4711-bf68-085fd0711d8c]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [gpu_uuid], result: [GPU-089608fe-cba5-4711-bf68-085fd0711d8c]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=power.draw --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['100.45', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [100.45]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.draw], result: [100.45]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=temperature.gpu --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['42', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [42]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [temperature.gpu], result: [42]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=temperature.memory --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['N/A', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [N/A]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [temperature.memory], result: [N/A]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=clocks.gr --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['2010', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [2010]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.gr], result: [2010]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=clocks.sm --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['2010', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [2010]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.sm], result: [2010]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=clocks.mem --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['7199', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [7199]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.mem], result: [7199]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=clocks.video --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['1860', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [1860]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.video], result: [1860]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=clocks.max.gr --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['2160', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.max.gr], result: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=clocks.max.sm --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['2160', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.max.sm], result: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=clocks.max.mem --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['7000', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [7000]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.max.mem], result: [7000]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=utilization.gpu --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['100', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [utilization.gpu], result: [100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=utilization.memory --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['4', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [4]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [utilization.memory], result: [4]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=memory.used --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['1029', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [1029]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [memory.used], result: [1029]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=fan.speed --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['100', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [fan.speed], result: [100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=gom.current --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['[N/A]', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [gom.current], result: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=pcie.link.width.current --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['4', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [4]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [pcie.link.width.current], result: [4]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=pcie.link.gen.current --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['2', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [2]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [pcie.link.gen.current], result: [2]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 08:00.0 --query-gpu=pstate --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['P2', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [P2]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [pstate], result: [P2]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: {'power.limit': '200.00', 'power.min_limit': '105.00', 'power.max_limit': '292.00', 'memory.total': '7982', 'vbios_version': '90.04.23.00.5F', 'driver_version': '440.100', 'compute_mode': 'Default', 'name': 'GeForce RTX 2080', 'serial': '[N/A]', 'index': '0', 'gpu_uuid': 'GPU-089608fe-cba5-4711-bf68-085fd0711d8c', 'power.draw': '100.45', 'temperature.gpu': '42', 'temperature.memory': 'N/A', 'clocks.gr': '2010', 'clocks.sm': '2010', 'clocks.mem': '7199', 'clocks.video': '1860', 'clocks.max.gr': '2160', 'clocks.max.sm': '2160', 'clocks.max.mem': '7000', 'utilization.gpu': '100', 'utilization.memory': '4', 'memory.used': '1029', 'fan.speed': '100', 'gom.current': '[N/A]', 'pcie.link.width.current': '4', 'pcie.link.gen.current': '2', 'pstate': 'P2'}
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=power.limit --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['200.00', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [200.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.limit], result: [200.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=power.min_limit --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['105.00', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [105.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.min_limit], result: [105.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=power.max_limit --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['292.00', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [292.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.max_limit], result: [292.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=memory.total --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['7979', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [7979]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [memory.total], result: [7979]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=vbios_version --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['90.04.23.00.5F', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [90.04.23.00.5F]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [vbios_version], result: [90.04.23.00.5F]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=driver_version --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['440.100', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [driver_version], result: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=compute_mode --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['Default', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [Default]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [compute_mode], result: [Default]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=name --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['GeForce RTX 2080', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [name], result: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=serial --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['[N/A]', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [serial], result: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=index --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['1', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [1]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [index], result: [1]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=gpu_uuid --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['GPU-22b2c6ac-2d49-4863-197c-9c469071178a', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [GPU-22b2c6ac-2d49-4863-197c-9c469071178a]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [gpu_uuid], result: [GPU-22b2c6ac-2d49-4863-197c-9c469071178a]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=power.draw --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['163.50', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [163.50]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.draw], result: [163.50]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=temperature.gpu --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['40', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [40]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [temperature.gpu], result: [40]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=temperature.memory --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['N/A', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [N/A]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [temperature.memory], result: [N/A]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=clocks.gr --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['1980', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [1980]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.gr], result: [1980]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=clocks.sm --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['1980', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [1980]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.sm], result: [1980]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=clocks.mem --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['7199', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [7199]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.mem], result: [7199]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=clocks.video --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['1830', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [1830]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.video], result: [1830]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=clocks.max.gr --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['2160', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.max.gr], result: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=clocks.max.sm --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['2160', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.max.sm], result: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=clocks.max.mem --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['7000', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [7000]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.max.mem], result: [7000]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=utilization.gpu --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['98', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [98]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [utilization.gpu], result: [98]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=utilization.memory --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['43', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [43]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [utilization.memory], result: [43]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=memory.used --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['1242', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [1242]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [memory.used], result: [1242]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=fan.speed --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['100', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [fan.speed], result: [100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=gom.current --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['[N/A]', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [gom.current], result: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=pcie.link.width.current --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['8', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [8]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [pcie.link.width.current], result: [8]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=pcie.link.gen.current --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['3', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [3]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [pcie.link.gen.current], result: [3]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0a:00.0 --query-gpu=pstate --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['P2', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [P2]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [pstate], result: [P2]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: {'power.limit': '200.00', 'power.min_limit': '105.00', 'power.max_limit': '292.00', 'memory.total': '7979', 'vbios_version': '90.04.23.00.5F', 'driver_version': '440.100', 'compute_mode': 'Default', 'name': 'GeForce RTX 2080', 'serial': '[N/A]', 'index': '1', 'gpu_uuid': 'GPU-22b2c6ac-2d49-4863-197c-9c469071178a', 'power.draw': '163.50', 'temperature.gpu': '40', 'temperature.memory': 'N/A', 'clocks.gr': '1980', 'clocks.sm': '1980', 'clocks.mem': '7199', 'clocks.video': '1830', 'clocks.max.gr': '2160', 'clocks.max.sm': '2160', 'clocks.max.mem': '7000', 'utilization.gpu': '98', 'utilization.memory': '43', 'memory.used': '1242', 'fan.speed': '100', 'gom.current': '[N/A]', 'pcie.link.width.current': '8', 'pcie.link.gen.current': '3', 'pstate': 'P2'}
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=power.limit --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['200.00', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [200.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.limit], result: [200.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=power.min_limit --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['105.00', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [105.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.min_limit], result: [105.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=power.max_limit --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['292.00', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [292.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.max_limit], result: [292.00]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=memory.total --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['7982', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [7982]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [memory.total], result: [7982]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=vbios_version --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['90.04.23.00.5F', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [90.04.23.00.5F]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [vbios_version], result: [90.04.23.00.5F]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=driver_version --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['440.100', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [driver_version], result: [440.100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=compute_mode --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['Default', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [Default]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [compute_mode], result: [Default]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=name --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['GeForce RTX 2080', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [name], result: [GeForce RTX 2080]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=serial --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['[N/A]', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [serial], result: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=index --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['2', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [2]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [index], result: [2]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=gpu_uuid --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['GPU-6933bcb7-7072-2181-a92f-0e5c42c3fa0d', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [GPU-6933bcb7-7072-2181-a92f-0e5c42c3fa0d]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [gpu_uuid], result: [GPU-6933bcb7-7072-2181-a92f-0e5c42c3fa0d]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=power.draw --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['194.95', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [194.95]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [power.draw], result: [194.95]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=temperature.gpu --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['48', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [48]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [temperature.gpu], result: [48]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=temperature.memory --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['N/A', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [N/A]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [temperature.memory], result: [N/A]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=clocks.gr --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['1920', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [1920]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.gr], result: [1920]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=clocks.sm --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['1935', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [1935]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.sm], result: [1935]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=clocks.mem --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['7199', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [7199]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.mem], result: [7199]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=clocks.video --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['1785', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [1785]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.video], result: [1785]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=clocks.max.gr --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['2160', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.max.gr], result: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=clocks.max.sm --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['2160', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.max.sm], result: [2160]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=clocks.max.mem --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['7000', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [7000]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [clocks.max.mem], result: [7000]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=utilization.gpu --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['97', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [97]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [utilization.gpu], result: [97]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=utilization.memory --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['24', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [24]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [utilization.memory], result: [24]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=memory.used --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['307', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [307]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [memory.used], result: [307]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=fan.speed --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['100', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [fan.speed], result: [100]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=gom.current --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['[N/A]', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [gom.current], result: [[N/A]]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=pcie.link.width.current --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['8', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [8]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [pcie.link.width.current], result: [8]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=pcie.link.gen.current --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['3', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [3]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [pcie.link.gen.current], result: [3]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV command:
/usr/bin/nvidia-smi -i 0b:00.0 --query-gpu=pstate --format=csv,noheader,nounits
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query result: [['P2', '']]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_nv:NV query response: [P2]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query (each-call) query item [pstate], result: [P2]
DEBUG:gpu-utils:GPUmodule.read_gpu_sensor_set_nv:NV query result: {'power.limit': '200.00', 'power.min_limit': '105.00', 'power.max_limit': '292.00', 'memory.total': '7982', 'vbios_version': '90.04.23.00.5F', 'driver_version': '440.100', 'compute_mode': 'Default', 'name': 'GeForce RTX 2080', 'serial': '[N/A]', 'index': '2', 'gpu_uuid': 'GPU-6933bcb7-7072-2181-a92f-0e5c42c3fa0d', 'power.draw': '194.95', 'temperature.gpu': '48', 'temperature.memory': 'N/A', 'clocks.gr': '1920', 'clocks.sm': '1935', 'clocks.mem': '7199', 'clocks.video': '1785', 'clocks.max.gr': '2160', 'clocks.max.sm': '2160', 'clocks.max.mem': '7000', 'utilization.gpu': '97', 'utilization.memory': '24', 'memory.used': '307', 'fan.speed': '100', 'gom.current': '[N/A]', 'pcie.link.width.current': '8', 'pcie.link.gen.current': '3', 'pstate': 'P2'}
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Is gpu-ls noticeably slower now that it reads one sensor at a time for the first read?
@csecht I will release it after you have a chance to check it out on your system.
from gpu-utils.
KeithMyers
commented on August 28, 2024
Yes, I would guess maybe 2X as long to read the cards on initial running compared to the previous version.
But on my system that only amounts to about another second. Not worried about it.
from gpu-utils.
csecht
commented on August 28, 2024
On my system it is only a slight stutter, which I hadn't really noticed before. For some reason, when running the old NVIDIA card on E@H pulsar #1 tasks, my Firefox browser really slows down. To browse sites, I need to suspend tasks. gpu-utils runs well, though not as zippy as previously.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
The extra one time reads are only for NV as the mechanism for AMD always required this. The first read will disable unreadable sensors, so the additional reads by plot and mon will just read valid sensors.
Have you checked out if the vddgfx fixes look good on your system?
from gpu-utils.
csecht
commented on August 28, 2024
Yes, that works well and looks good. Good to know about NVIDIA p-states having 0 as highest. The text for vddgfx helps, but, as an aside, what does 'nan' stand for?
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
It stands for not a number. It is a datatype used in numpy to indicate a float value that can not be described with a numeric value, like infinite.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I have one more change before I call this release complete. For the first sensor read, I will classify the card as unreadable if no sensors can be read. I will request verification here when it is complete.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I just pushed 3.4.13 which will set NV card readability to False if no parameters can be read. Let me know if you see any issues with the latest on master.
from gpu-utils.
csecht
commented on August 28, 2024
Everythings works, except what is noted below.
Found a possible bug, something I thought was working a while back, but am not sure. Now, however, clinfo data does not show for the RX 5600 XT card, but does for NVIDIA on the same host (debug file attached). clinfo does show for both two RX 570 cards on my other host.
$ ./gpu-ls --clinfo
OS command [nvidia-smi] executable found: [/usr/bin/nvidia-smi]
Detected GPUs: INTEL: 1, NVIDIA: 1, AMD: 1
AMD: amdgpu version: 20.10-1048554
AMD: Wattman features enabled: 0xfffd7fff
3 total GPUs, 1 rw, 1 r-only, 0 w-only
Card Number: 0
Vendor: INTEL
Readable: False
Writable: False
Compute: False
Device ID: {'device': '0x3e91', 'subsystem_device': '0x8694', 'subsystem_vendor': '0x1043', 'vendor': '0x8086'}
Decoded Device ID: 8th Gen Core Processor Gaussian Mixture Model
Card Model: Intel Corporation 8th Gen Core Processor Gaussian Mixture Model
PCIe ID: 00:02.0
Driver: i915
GPU Type: Unsupported
HWmon: None
Card Path: /sys/class/drm/card0/device
System Card Path: /sys/devices/pci0000:00/0000:00:02.0
Card Number: 1
Vendor: NVIDIA
Readable: True
Writable: False
Compute: True
GPU UID: GPU-fcbaadc4-4040-c2e5-d5b6-52d1547bcc64
GPU S/N: [Not Supported]
Device ID: {'device': '0x1381', 'subsystem_device': '0x1073', 'subsystem_vendor': '0x10de', 'vendor': '0x10de'}
Decoded Device ID: GM107 [GeForce GTX 750]
Card Model: GeForce GTX 750
Display Card Model: GeForce GTX 750
Card Index: 0
PCIe ID: 01:00.0
Link Speed: GEN3
Link Width: 8
##################################################
Driver: 390.138
vBIOS Version: 82.07.32.00.32
Compute Platform: OpenCL 1.2 CUDA
Compute Mode: Default
GPU Type: Supported
HWmon: None
Card Path: /sys/class/drm/card1/device
System Card Path: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0
##################################################
Current Power (W): 17.180
Power Cap (W): 38.50
Power Cap Range (W): [30.0, 38.5]
Fan Target Speed (rpm): None
Current Fan PWM (%): 40.000
##################################################
Current GPU Loading (%): 100
Current Memory Loading (%): 34
Current VRAM Usage (%): 90.214
Current VRAM Used (GB): 0.864
Total VRAM (GB): 0.958
Current Temps (C): {'temperature.gpu': 47.0, 'temperature.memory': None}
Current Clk Frequencies (MHz): {'clocks.gr': 1163.0, 'clocks.mem': 2505.0, 'clocks.sm': 1163.0, 'clocks.video': 1046.0}
Maximum Clk Frequencies (MHz): {'clocks.max.gr': 1293.0, 'clocks.max.mem': 2505.0, 'clocks.max.sm': 1293.0}
Current SCLK P-State: [0, '']
Power Profile Mode: [Not Supported]
##################################################
Device OpenCL C Version: OpenCL C 1.2
Device Name: GeForce GTX 750
Device Version: OpenCL 1.2 CUDA
Driver Version: 390.138
Max Compute Units: 4
SIMD per CU: 2
SIMD Width: 32
SIMD Instruction Width: 1
CL Max Memory Allocation: 257261568
Max Work Item Dimensions: 3
Max Work Item Sizes: 1024 1024 64
Max Work Group Size: 1024
Preferred Work Group Size: 256
Preferred Work Group Multiple: 32
Card Number: 2
Vendor: AMD
Readable: True
Writable: True
Compute: False
GPU UID: None
Device ID: {'device': '0x731f', 'subsystem_device': '0xe411', 'subsystem_vendor': '0x1da2', 'vendor': '0x1002'}
Decoded Device ID: Radeon RX 5600 XT
Card Model: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev ca)
Display Card Model: Radeon RX 5600 XT
PCIe ID: 04:00.0
Link Speed: 16 GT/s
Link Width: 16
##################################################
Driver: amdgpu
vBIOS Version: 113-5E4111U-X4G
Compute Platform: None
GPU Type: CurvePts
HWmon: /sys/class/drm/card2/device/hwmon/hwmon3
Card Path: /sys/class/drm/card2/device
System Card Path: /sys/devices/pci0000:00/0000:00:01.1/0000:02:00.0/0000:03:00.0/0000:04:00.0
##################################################
Current Power (W): 117.000
Power Cap (W): 160.000
Power Cap Range (W): [0, 192]
Fan Enable: 0
Fan PWM Mode: [2, 'Dynamic']
Fan Target Speed (rpm): 1026
Current Fan Speed (rpm): 1026
Current Fan PWM (%): 31
Fan Speed Range (rpm): [0, 3200]
Fan PWM Range (%): [0, 100]
##################################################
Current GPU Loading (%): 92
Current Memory Loading (%): 37
Current GTT Memory Usage (%): 0.432
Current GTT Memory Used (GB): 0.026
Total GTT Memory (GB): 5.984
Current VRAM Usage (%): 11.969
Current VRAM Used (GB): 0.716
Total VRAM (GB): 5.984
Current Temps (C): {'edge': 59.0, 'junction': 67.0, 'mem': 82.0}
Critical Temps (C): {'edge': 118.0, 'junction': 99.0, 'mem': 99.0}
Current Voltages (V): {'vddgfx': 887}
Current Clk Frequencies (MHz): {'mclk': 875.0, 'sclk': 1700.0}
Current SCLK P-State: [2, '1700Mhz']
SCLK Range: ['800Mhz', '1820Mhz']
Current MCLK P-State: [3, '875Mhz']
MCLK Range: ['625Mhz', '930Mhz']
Power Profile Mode: 0-BOOTUP_DEFAULT
Power DPM Force Performance Level: manual
This may be related to the clinfo issue; Why does the Navi10 card show Compute: False, when it does run the COMPUTE PPM? The NVIDIA and the RX570 cards all show Compute: True.
Card Number: 2
Vendor: AMD
Readable: True
Writable: True
Compute: False
Device ID: {'device': '0x731f', 'subsystem_device': '0xe411', 'subsystem_vendor': '0x1da2', 'vendor': '0x1002'}
Decoded Device ID: Radeon RX 5600 XT
PCIe ID: 04:00.0
GPU Type: CurvePts
HWmon: /sys/class/drm/card2/device/hwmon/hwmon3
Card Path: /sys/class/drm/card2/device
System Card Path: /sys/devices/pci0000:00/0000:00:01.1/0000:02:00.0/0000:03:00.0/0000:04:00.0
from gpu-utils.
csecht
commented on August 28, 2024
I can work on updating the User Guide tomorrow. Which examples and screenshots do you want to show the hybrid AMD/NV system?
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Can you verify if it is possibly using an nvidia specific clinfo? which clinfo
And use the clinfo command line to see if the AMD card shows up?
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Maybe there is something that I did not anticipate in an AMD/NV system. Can you provide the output of clinfo --raw
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I can work on updating the User Guide tomorrow. Which examples and screenshots do you want to show the hybrid AMD/NV system?
I think it would be good to demonstrate the increased compatibility where ever possible. If there is some point that needs to made with another example that is only AMD, I think that should be prioritized over showing the hybrid setup. I think at least the plot image is necessary to make the point.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
This may be related to the clinfo issue; Why does the Navi10 card show Compute: False, when it does run the COMPUTE PPM? The NVIDIA and the RX570 cards all show Compute: True.
Compute capability is determined from the output of clinfo --raw. The ppm compute mode is only a performance mode that impacts how the card changes performance states and does not influence compute mode being available or not. Getting the clinfo --raw output will be critical in understanding the issue.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I think I have found the issue and pushed a fix. I found that the utility was only looking at the clinfo index, but the index starts from zero for each vendor. Now it looks at both vendor and index.
from gpu-utils.
csecht
commented on August 28, 2024
Yes, good, that fixed the clinfo option for the AMD card and its compute true status. gpu-ls --clinfo now works for all cards in:
Version: 3.4.13
Maintainer: RueiKe
Status: Development Status :: 4 - Beta
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
I have released the latest to PyPI!
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
@csecht I have merged the pull request for the User Guide updates. My only concern is that it looks like long model names are not truncated in gpu-pac. I have included truncation so that the interface works with more cards. Let me know of any concerns. Also, it would be good to change the pac image since it still indicates the old amdgpu name.
from gpu-utils.
csecht
commented on August 28, 2024
That PAC screenshot I used was from before pci-id database updated (with the request I had made earlier for that Navi10 card). By the time the updated pci-id displayed the short model name (Radeon RX 5600 XT), I had taken the RX 570 card out of that machine and so lost the opportunity to show both cards types with their short model names in the one PAC window. So we can leave that slightly outdated PAC graphic with the long name as is or replace it with two separate PAC screenshots for each card type (with their short names). It’s good though to use truncation, because no doubt there are other cards without short model names in the database.
… On Jul 5, 2020, at 7:57 PM, Rick ***@***.***> wrote:
@csecht <https://github.com/csecht> I have merged the pull request <#93> for the User Guide updates. My only concern is that it looks like long model names are not truncated in gpu-pac. I have included truncation so that the interface works with more cards. Let me know of any concerns.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALMVCQULSKHL62VDQKTYGVDR2EOO7ANCNFSM4OGEFXNA>.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Thanks for the explanation. Maybe it is best to leave it as it is until either of us has a better setup that demonstrates gpu-util capability.
from gpu-utils.
Ricks-Lab
commented on August 28, 2024
Officially released v3.5.0!
from gpu-utils.
Related Issues (20)
- Feature Request: Support values from sysfs gpu_metrics
- index out of bound error HOT 4
- Can not read parameter and list index out of range HOT 5
- Tool doesn't see GPUs when PCI address has multiple domains HOT 9
- Add GDDR6X memory temps to the sensor readouts for Nvidia cards
- unsupported operand type(s) for *: 'float' and 'NoneType' in GPUmodule.py HOT 29
- Ubuntu 22.04 Debian Package - Invalid Icon Path HOT 1
- Warning: apt-key is deprecated in Ubuntu 22.04 HOT 1
- env.py: conversion of hexadecimal to int fails HOT 2
- Wrong vendor for on-board GPU HOT 1
- AMD Ryzen 5 5700G with Cezanne not working HOT 5
- gpu-mon requires gtk modules even when --gui is not used HOT 10
- ValueError: invalid literal for int() with base 10 at GPUmodules.py line 1236 in read_gpu_pstates HOT 10
- RX7900 (gfx11) Cards Fan Control is Not Functional HOT 10
- When using gpu-pac I receive an error HOT 2
- Support for MacOS-X ? HOT 2
- ValueError: invalid literal for int() with base 10: HOT 12
- VRAM and GTT memory usage reported as None HOT 5
- Q: had it been tested w/ latest Debian bpo Kernel? HOT 14
- PermissionError: [Errno 1] Operation not permitted HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gpu-utils.