[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120619004956.GA15859@openwall.com>
Date: Tue, 19 Jun 2012 04:49:56 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: bf-opencl
On Tue, Jun 19, 2012 at 04:25:21AM +0400, Solar Designer wrote:
> ...Oh, I got "ASIC hang" after:
>
> guesses: 345 time: 0:00:03:28 0.00% c/s: 5449 trying: 123456 - random
>
> Whatever. I'll bring it back to stock clocks (925 MHz core).
>
> BTW, 1300 MHz resulted in John's self-test failure, and 1250 MHz worked
> for 3.5 minutes as you can see. I don't know if the "ASIC hang" was
> related to the overclock or not.
This is unclear. I tried running the same test at stock clocks, and it
worked fine for about 15 minutes:
guesses: 1199 time: 0:00:14:26 28.25% (ETA: Tue Jun 19 05:17:59 2012) c/s: 4111 trying: rangers - 222222
but then the entire machine locked up (stopped responding to ping) and
rebooted, maybe due to:
kernel.panic = 20
kernel.panic_on_oops = 1
kernel.softlockup_panic = 1
kernel.hung_task_panic = 1
kernel.hung_task_timeout_secs = 300
It was probably not the hung_task_panic, but it could have been an Oops.
There's nothing about this in the logs.
So maybe bf-opencl still triggers problems with the AMD driver for 7970.
Alexander
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.
