[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+E3k92A97gSr+aW_jLh61Ari6c3gXeWXKm7SmY8crcUdR_J8A@mail.gmail.com>
Date: Sat, 11 Oct 2014 17:21:36 -0800
From: Royce Williams <royce@...ho.org>
To: john-users@...ts.openwall.com
Subject: Re: thanks for GPU temp and fan speed in status line
On Sat, Oct 11, 2014 at 4:37 PM, magnum <john.magnum@...hmail.com> wrote:
> On 2014-10-11 07:55, Royce Williams wrote:
>>
>> On Fri, Oct 10, 2014 at 6:11 PM, magnum <john.magnum@...hmail.com> wrote:
>>>
>>> BTW could you please post the full output of --list=cuda-devices
>>
>>
>> As of: commit d243b8f06e45e411dc56bccab975b3b05243bca3
>> ... the opencl temp and fan still look like I expect it to for temp
>> and fan, but the cuda looks swapped:
>>
>> NVML id: 1
>> Fan speed: 32%
>> Temperature: 28°C
>> Utilization: n/a
>
> I'm glad we did this, lol. After going through hoops mapping CUDA-id to
> NVML-id (after all, we did *print* the right one), we still called
> get_temp() using the CUDA id. Doh! I'm glad we can iron these things out
> with your help. It's fixed in latest commit.
Glad to help. Pulled, and looks good:
$ ./john --list=cuda-devices | egrep 'Name|Fan|temp'
Name: GeForce GTX 750 Ti
Fan speed: 32%
GPU temp: 30°C
Name: GeForce GTX 480
Fan speed: 50%
GPU temp: 75°C
> This bug only affected --list though, not status lines. Just for peace of
> mind, could you run a brief crack against some test hash using a CUDA format
> and double-check that it prints the correct temp/fan values in the status
> line too?
I can't verify this at this time because I can't seem to get john to
produce a status line on this run. This happens to me once in a while
on a variety of platforms, but I've never really understood why (may
be a FAQ item, but I couldn't find it when I last checked).
$ ./john --format=phpass-cuda test.phpass
Loaded 1 password hash (phpass-cuda [MD5 CUDA])
Press 'q' or Ctrl-C to abort, almost any other key for status
[this whitespace is me pressing "enter" to no effect,
even after waiting a few minutes]
Session aborted
I know it's running, because if I ask for an independent status, I get
one (though it does not contain any GPU info):
$ ./john--status
0g 0:00:02:01 3/3 0g/s 48480p/s 48480c/s 48480C/s
Royce
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
