lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <75d7d31d-3637-090d-0061-ccb8d17388e4@alu.unizg.hr>
Date:   Sun, 11 Jun 2023 01:05:44 +0200
From:   Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr>
To:     alsa-devel@...a-project.org, linux-kselftest@...r.kernel.org
Cc:     Mark Brown <broonie@...nel.org>, Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>, Shuah Khan <shuah@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: [BUG] selftests: alsa: pcm-test: premature timeout severs the test

Hi,

On several platforms, and for some time, I've noticed alsa: pcm-test TIMEOUT.
I have tried to increase the timeout in selftests/alsa/settings: timeout=300,
so I think there is no more purpose to further increase it, so something appears
generally stuck.

The test runs up to "default.time4.1.8 section where it hangs for more than
200 seconds, possibly indefinitely.

The output of the selftest is:

# # default.time3.1.8.0.PLAYBACK - 44.1kHz stereo large periods
# # default.time3.1.8.0.PLAYBACK hw_params.RW_INTERLEAVED.S16_LE.44100.2.22496.202464 sw_params.202464
# ok 61 default.time3.0.3.0.PLAYBACK
# # default.time4.0.3.0.PLAYBACK - 48kHz stereo small periods
# # default.time4.0.3.0.PLAYBACK hw_params.RW_INTERLEAVED.S16_LE.48000.2.512.4096 sw_params.4096
# ok 62 default.time4.0.3.0.PLAYBACK
# # default.time5.0.3.0.PLAYBACK - 48kHz stereo large periods
# # default.time5.0.3.0.PLAYBACK hw_params.RW_INTERLEAVED.S16_LE.48000.2.24000.192000 sw_params.192000
# ok 63 default.time5.0.3.0.PLAYBACK
# # default.time6.0.3.0.PLAYBACK - 48kHz 6 channel large periods
# # default.time6.0.3.0.PLAYBACK hw_params.RW_INTERLEAVED.S16_LE.48000.2.48000.576000 sw_params.576000
# ok 64 default.time6.0.3.0.PLAYBACK
# # default.time7.0.3.0.PLAYBACK - 96kHz stereo large periods
# # default.time7.0.3.0.PLAYBACK hw_params.RW_INTERLEAVED.S16_LE.96000.2.48000.192000 sw_params.192000
# not ok 65 default.time3.1.8.0.PLAYBACK
# # time mismatch: expected 4000ms got 17005
# # default.time4.1.8.#
not ok 2 selftests: alsa: pcm-test # TIMEOUT 300 seconds

The platform is AMD Ryzen 9 assembled box with AsRock mainboard. Config and Lshw attached.

CONTINUED:

Just to test further, I have increased timeout even further, to 400 seconds.
Only then the test passed, but with numerous errors, and this is Ryzen 9, so
I guess it can only be worse on hardware like i3 or i5.

But many subtests failed, so I am submitting the entire test log (due to mailing list
constraints to 100K size of attachments, it is compressed).

Best regards,
Mirsad

--------------
diff -u /dev/null tools/testing/selftests/alsa/settings
--- /dev/null	2023-06-11 00:36:30.651447094 +0200
+++ tools/testing/selftests/alsa/settings	2023-06-11 00:37:32.067504069 +0200
@@ -0,0 +1 @@
+timeout=400
Download attachment "alsa-pcm-test.log.xz" of type "application/x-xz" (5920 bytes)

Download attachment "config-6.4.0-rc5-kmlk-netdbg-iwlwifi-00305-g022ce8862dff.xz" of type "application/x-xz" (57708 bytes)

Download attachment "lshw.txt.xz" of type "application/x-xz" (6568 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ