| 1 |
On Tuesday, 14 November 2017 06:37:35 GMT R0b0t1 wrote: |
| 2 |
|
| 3 |
> On Mon, Nov 13, 2017 at 9:46 AM, Peter Humphrey <peter@××××××××××××.uk> |
| 4 |
wrote: |
| 5 |
> > On Monday, 13 November 2017 15:12:56 GMT Daniel Frey wrote: |
| 6 |
> >> On 11/13/17 02:59, Peter Humphrey wrote: |
| 7 |
> >> > I'm hunting a problem with cooling in this box, and I've got as far |
| 8 |
> >> > as suspecting my new AMD WX 5100 GPU. |
| 9 |
> >> > |
| 10 |
> >> > One of my BOINC projects causes the GPU temperature, as shown by |
| 11 |
> >> > gkrellm, to shoot up to 75C or more and cause intolerable system |
| 12 |
> >> > cooling noise. If I suspend that project but leave the other seven |
| 13 |
> >> > running, the temperature returns to what I hope is a normal 55C. |
| 14 |
> >> > Those seven projects are supposed to use the GPU, but I'm not sure |
| 15 |
> >> > whether they do in fact. |
| 16 |
> >> > |
| 17 |
> >> > Is there any way I can monitor what is using the GPU, to find out? |
| 18 |
> >> |
| 19 |
> >> I don't know if there's a utility for consumer level cards that can do |
| 20 |
> >> this. I do remember for Nvidia there's nvidia-smi but I don't think it |
| 21 |
> >> will list processes for desktop cards. |
| 22 |
> > |
| 23 |
> > This isn't consumer grade (look it up in your local shops ;-) ): |
| 24 |
> > |
| 25 |
> > # lspci -v -s 01:00.0 |
| 26 |
> > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. |
| 27 |
> > [AMD/ATI] |
| 28 |
> > Ellesmere [Radeon Pro WX 5100] (prog-if 00 [VGA controller]) |
| 29 |
[...] |
| 30 |
> >> The only other generic ones I can think of are cuda-z and gputop. Have |
| 31 |
> >> you tried one of those? Although I don't think it'll give you the |
| 32 |
> >> information you need either. |
| 33 |
> > |
| 34 |
> > As it's AMD, not nVidia, nvidia-smi and cuda aren't suitable. I hadn't |
| 35 |
> > heard of GPU Top - thanks. I'll have a look at it. |
| 36 |
> > |
| 37 |
> > I forgot to add that I'm using the proprietary |
| 38 |
> > dev-libs/amdgpu-pro-opencl |
| 39 |
> > because mesa hasn't caught up yet. |
| 40 |
> |
| 41 |
> The level of detail you want will likely necessitate the use of a GPU |
| 42 |
> debugger. AMD provides CodeXL, located at |
| 43 |
> https://gpuopen.com/compute-product/codexl/. I suggest looking at the |
| 44 |
> profiling features. |
| 45 |
|
| 46 |
That does look interesting - many thanks. |
| 47 |
|
| 48 |
> You may want to communicate your findings to the relevant BOINC projects. |
| 49 |
|
| 50 |
Of course. |
| 51 |
|
| 52 |
-- |
| 53 |
Regards, |
| 54 |
Peter. |
Archives