FS#61320 - [systemd] mpv spits "cannot lock down memory" when using jack after upgrading to 240

Attached to Project: Arch Linux
Opened by Tom Yan (tom.ty89) - Wednesday, 09 January 2019, 10:31 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 13:07 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The full "error" is:
cannot lock down memory for RT thread (Cannot allocate memory)

It is only spitted by mpv but not jackd. It does not prevent anything from actually working. Reverting systemd to 239.370-1 makes it go away.


Additional info:
* package version(s) 240.0-3
* config and/or log files etc.


Steps to reproduce:
Start jackd (from "jack1") and play something with `mpv -ao jack`.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 10 December 2019, 13:07 GMT
Reason for closing:  Fixed
Comment by Tom Yan (tom.ty89) - Wednesday, 09 January 2019, 11:12 GMT
Apparently the problem is more serious. It gives qemu/vfio hiccup as well:
qemu-system-x86_64: -device vfio-pci,host=00:1b.0: VFIO_MAP_DMA: -12
qemu-system-x86_64: -device vfio-pci,host=00:1b.0: vfio_dma_map(0x7fd6ff891640, 0x0, 0x80000000, 0x7fd4f7e00000) = -12 (Cannot allocate memory)
qemu-system-x86_64: -device vfio-pci,host=00:1b.0: VFIO_MAP_DMA: -12
qemu-system-x86_64: -device vfio-pci,host=00:1b.0: vfio_dma_map(0x7fd6ff891640, 0x100000000, 0x180000000, 0x7fd577e00000) = -12 (Cannot allocate memory)
qemu-system-x86_64: -device vfio-pci,host=00:1b.0: vfio 0000:00:1b.0: failed to setup container for group 5: memory listener initialization failed for container: Cannot allocate memory
Comment by Tom Yan (tom.ty89) - Wednesday, 09 January 2019, 11:15 GMT
Just to clarify, qemu/the VM cannot be started because of the above errors.
Comment by Tom Yan (tom.ty89) - Thursday, 10 January 2019, 20:57 GMT
Filed a bug report to upstream with some more details: https://github.com/systemd/systemd/issues/11386

Loading...