Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 13 Aug 2013 11:48:31 +0200
From: Katja Malvoni <>
Subject: Re: Parallella: bcrypt

On Tue, Aug 13, 2013 at 12:35 AM, Yaniv Sapir <> wrote:

> Register f0444 is a special undocumented register that tells us a few
> things about the core's status. However, the value you see does not point
> to a specific problem. The STATUS reg does not show a problem either. Can
> you please tell me the value of the reg. f040c?

F040C is zero for all cores.

> The one thing I'd suspect is using the e_reset_core() call while a global
> address load or fetch are in progress. In this case, you can cause a system
> lockup if the state machines get reset while the data is in the writeback
> stage. Do you have any situation like this in there?

No, I don't. I'm using e_reset_system() before computation starts and that
is the only reset.

>  I also would like to know the contents of the IVT of the stuck core. Is
> it the same as the other cores?

IVT is address 0 of core? If yes, it's 0x00002ce8 and it's same for stuck
core and for others.


Content of type "text/html" skipped

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.