The silent_stream_disable() function introduced by the commit
b1a5039759cb (“ALSA: hda/hdmi: fix silent stream for first playback to
DP”) takes the per_pin->lock mutex, but it unlocks the wrong one,
spec->pcm_lock, which causes a deadlock. This patch corrects it.
Fixes: b1a5039759cb (“ALSA: hda/hdmi: fix silent stream for first playback to DP”)
Reported-by: Jan Alexander Steffens (heftig)
Cc:
Signed-off-by: Takashi Iwai
/* update ELD and jack state via audio component */
2.26.2
Turned out it was already reported but I couldn’t find it until I bisected 5.11 in search of a culprit.
Tested both 5.11-rc1 and 5.10.4, the issue is resolved.
I guess I have no access to MJ Gitlab to make a PR, hence I post it here. Pinging @nightmare-2021
As it was reported by an Arch maintainer, I guess Arch will have it included soon (or already has it, I didn’t check).
Linux kernel `5.11.rc2.d0103.ge71ba94-1` made my audio DAC to produce several clicks during PC startup
$ uname -r
5.11.0-1-MANJARO
$ pacman -Qi linux511
Name : linux511
Version : 5.11.rc2.d0103.ge71ba94-1
Description : The Linux511 kernel and modules
...
During startup I hear 3 clicks from loudspeakers in the other side connected to external audio DAC. Very easy to hear: the volume of the clicks has full loudness of system audio.
I did not remember that such effect ever was on any 5.x kernel family before 5.11.
Also while loading current
$ pacman -Qi linux510
Name : linux510
Version : 5.10.5-1
there was no any startup click.
Just installed
$ pacman -Qi linux-firmware
Name : linux-firmware
Version : 20210108.r1809.060ad8b-1
Description : Firmware files for Linux (Manjaro Overlay Package)
But startup clicks remains.
Also while clicks happens the audio DAC’s display shows frequent changing of signal type: at least DSD/PCM and probably sampling frequency (it is changing too fast).
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Package (1) Old Version New Version Net Change Download Size
core/linux510 5.10.5-1 5.10.6-1 0.00 MiB 84.43 MiB
Total Download Size: 84.43 MiB
Total Installed Size: 149.60 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
linux510-5.10.6-1-x86_64 84.4 MiB 3.29 MiB/s 00:26 [####################################################################] 100%
(1/1) checking keys in keyring [####################################################################] 100%
(1/1) checking package integrity [####################################################################] 100%
(1/1) loading package files [####################################################################] 100%
(1/1) checking for file conflicts [####################################################################] 100%
(1/1) checking available disk space [####################################################################] 100%
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/build/
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/build/vmlinux
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/extramodules
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/aegis128-aesni.ko.xz
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/aesni-intel.ko.xz
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/blake2s-x86_64.ko.xz
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/blowfish-x86_64.ko.xz
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/camellia-aesni-avx-x86_64.ko.xz
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/camellia-aesni-avx2.ko.xz
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/camellia-x86_64.ko.xz
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/cast5-avx-x86_64.ko.xz
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/cast6-avx-x86_64.ko.xz
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/chacha-x86_64.ko.xz
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/crc32-pclmul.ko.xz
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/kernel/arch/x86/crypto/crc32c-intel.ko.xz
...
tonns os lines starting w/ warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/
...
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/modules.symbols
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/modules.symbols.bin
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/pkgbase
warning: could not get file information for usr/lib/modules/5.10.5-1-MANJARO/vmlinuz
:: Running pre-transaction hooks...
(1/2) Removing linux initcpios...
(2/2) Save Linux kernel modules
:: Processing package changes...
(1/1) upgrading linux510 [####################################################################] 100%
:: Running post-transaction hooks...
(1/5) Arming ConditionNeedsUpdate...
(2/5) Updating module dependencies...
(3/5) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: 5.10.6-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect
==> Starting build: 5.10.6-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64-fallback.img
==> Image generation successful
(4/5) Updating Grub-Bootmenu
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.11-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.11-x86_64.img
Found initrd fallback image: /boot/initramfs-5.11-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Adding boot menu entry for UEFI Firmware Settings ...
done
(5/5) Restore Linux kernel modules
==> Warning:
-> Kernel has been updated. Modules of the current kernel
-> have been backed up so you can continue to use your
-> computer. However, the new kernel will only work
-> at next boot.
$
@phush0, you forgot to mention the version you are installing.
I am installing now:
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Package (1) Old Version New Version Net Change Download Size
core/linux510 5.10.6-1 5.10.6-2 -0.01 MiB 84.42 MiB
This new version installation was clean from such warnings.
Net Change: -0.01 MiB
Reminds me the 10-year old anecdote:
- Why Windows XP SP3 has less size than SP2 installation image? (probably 591 MiB (SP3) vs more than 600 MiB (SP2)) - They had cut out a bugs.
Package (12) Old Version New Version Net Change Download Size
...
community/telegram-desktop 2.5.4.r4.g838a3b23c-1 2.5.5.r0.g838a3b23c-1 0.00 MiB 24.27 MiB
...
wget-1.21.1-1-x86_64 740.9 KiB 1965 KiB/s 00:00 [####################################################################] 100%
error: failed retrieving file 'telegram-desktop-2.5.5.r0.g838a3b23c-1-x86_64.pkg.tar.zst' from manjaro.mirrors.lavatech.top : The requested URL returned error: 404
warning: failed to retrieve some files
...
EDIT: now fixed
EDIT 2: does that errors cases (then an item is present in db, but absent on server) are reported automatically to server’s admins, so end users have no need to post about that?
If not, then would it be hard to make it automated? It is once, but for all time and errors are visible instantly as they appears at the moment of a first user meet it.
Can’t say if it was due to an update or rather to me (even though I cannot see what, and don’t remember messing around this) but Timeshift icon has gone AWOL some days ago in my Gnome setup.
Browsing in overview/activities, or once launched in Dash to dock, Timeshift icon was missing (invisible).
Even the entry in Manjaro Hello / Applications has a crossed x instead of icon.
In /usr/share/applications, theTimeshift.desktop was blank. I had to manually put back the icon from /usr/share/icons/something.
In my 2 other setups KDE and Cinnamon, Timeshift icon was there in the start menu, as well as on the panel once launched.