summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/socket/1823790
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/gemma3:12b/socket/1823790')
-rw-r--r--results/classifier/gemma3:12b/socket/182379022
1 files changed, 22 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/socket/1823790 b/results/classifier/gemma3:12b/socket/1823790
new file mode 100644
index 00000000..6b3400d3
--- /dev/null
+++ b/results/classifier/gemma3:12b/socket/1823790
@@ -0,0 +1,22 @@
+
+QEMU mishandling of SO_PEERSEC forces systemd into tight loop
+
+While building Debian images for embedded ARM target systems I detected that QEMU seems to force newer systemd daemons into a tight loop.
+
+My setup is the following:
+
+Host machine: Ubuntu 18.04, amd64
+LXD container: Debian Buster, arm64, systemd 241
+QEMU: qemu-aarch64-static, 4.0.0-rc2 (custom build) and 3.1.0 (Debian 1:3.1+dfsg-7)
+
+To easily reproduce the issue I have created the following repository:
+https://github.com/lueschem/edi-qemu
+
+The call where systemd gets looping is the following:
+2837 getsockopt(3,1,31,274891889456,274887218756,274888927920) = -1 errno=34 (Numerical result out of range)
+
+Furthermore I also verified that the issue is not related to LXD.
+The same behavior can be reproduced using systemd-nspawn.
+
+This issue reported against systemd seems to be related:
+https://github.com/systemd/systemd/issues/11557
\ No newline at end of file