On 2024-09-28 01:11, Cordell Bloor wrote:
> "Killed" disappeared when I ran it myself in both cases. However, it did
> get further with vm.overcommit_memory=0:
Hm, odd. The OOM killer does kill rocfft-test, from dmesg:
> [ 633.776686] Out of memory: Killed process 4053 (rocfft-test)
and I would
Hi Christian,
On 2024-09-27 16:11, Christian Kastner wrote:
Am I interpreting this right that the "Killed" disappeared? If so, then the
issue should be reproducible by re-enabling vm.overcommit_memory=0.
"Killed" disappeared when I ran it myself in both cases. However, it did
get further wit
On 2024-09-27 23:34, Cordell Bloor wrote:
>> $ sudo sysctl kernel.dmesg_restrict=0
>> $ sudo sysctl vm.overcommit_memory=2
> The log output after applying both changes:
>
> [ RUN ]
> pow2_1D/accuracy_test.vs_fftw/complex_forward_len_67108864_single_op_batch_1_istride_1_CI_ostride_1_CI_id
Hi Christian,
I appreciate your help. Those were good suggestions.
On 2024-09-27 13:40, Christian Kastner wrote:
558s dmesg: read kernel buffer failed: Operation not permitted
This isn't from the test, this is our test runner that tries to capture
dmesg before and after [3] each test, for debu
Hi Cory,
On 2024-09-27 20:52, Cordell Bloor wrote:
> The rocfft tests are crashing on gfx1035 after updating the kernel from
> bookworm to bookworm-backports (6.1 to 6.10). This can be seen be comparing
> these two nearly identical runs from before [1] and after [2] installing a new
> kernel.
>
>
Package: librocfft0-tests
Version: 6.1.2-1
Severity: normal
X-Debbugs-Cc: c...@slerp.xyz
Dear Maintainer,
The rocfft tests are crashing on gfx1035 after updating the kernel from
bookworm to bookworm-backports (6.1 to 6.10). This can be seen be comparing
these two nearly identical runs from before
6 matches
Mail list logo
