Hi Daniel,
On 2019-05-12 9:44 p.m., Daniel Kasak wrote:
> [CAUTION: External Email]
> Hi all. I had version 2.2.0 of the ROCM stack running on a 5.0.x and
> 5.1.0 kernel. Things were going great with various boinc GPU tasks.
> But there is a setiathome GPU task which reliably gives me a hard
>
Dear Daniel,
On 05/16/2019 01:52 PM, Daniel Kasak wrote:
> On Thu, May 16, 2019 at 11:43 AM Alex Deucher wrote:
>
>> On Wed, May 15, 2019 at 8:33 PM Daniel Kasak
>> wrote:
>>>
>>> On Mon, May 13, 2019 at 11:44 AM Daniel Kasak
>> wrote:
Hi all. I had version 2.2.0 of the ROCM stack r
On Thu, May 16, 2019 at 11:43 AM Alex Deucher wrote:
> On Wed, May 15, 2019 at 8:33 PM Daniel Kasak
> wrote:
> >
> > On Mon, May 13, 2019 at 11:44 AM Daniel Kasak
> wrote:
> >>
> >> Hi all. I had version 2.2.0 of the ROCM stack running on a 5.0.x and
> 5.1.0 kernel. Things were going great with
On Wed, May 15, 2019 at 8:33 PM Daniel Kasak wrote:
>
> On Mon, May 13, 2019 at 11:44 AM Daniel Kasak wrote:
>>
>> Hi all. I had version 2.2.0 of the ROCM stack running on a 5.0.x and 5.1.0
>> kernel. Things were going great with various boinc GPU tasks. But there is a
>> setiathome GPU task wh
On Mon, May 13, 2019 at 11:44 AM Daniel Kasak
wrote:
> Hi all. I had version 2.2.0 of the ROCM stack running on a 5.0.x and 5.1.0
> kernel. Things were going great with various boinc GPU tasks. But there is
> a setiathome GPU task which reliably gives me a hard lockup within about 30
> minutes of
Hi all. I had version 2.2.0 of the ROCM stack running on a 5.0.x and 5.1.0
kernel. Things were going great with various boinc GPU tasks. But there is
a setiathome GPU task which reliably gives me a hard lockup within about 30
minutes of running. I actually had to do *two* emergency re-installs over
