summary refs log tree commit diff stats
path: root/results/classifier/no-thinking-deepseek-r1:32b/output/syscall/1861341
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/no-thinking-deepseek-r1:32b/output/syscall/1861341')
-rw-r--r--results/classifier/no-thinking-deepseek-r1:32b/output/syscall/186134133
1 files changed, 33 insertions, 0 deletions
diff --git a/results/classifier/no-thinking-deepseek-r1:32b/output/syscall/1861341 b/results/classifier/no-thinking-deepseek-r1:32b/output/syscall/1861341
new file mode 100644
index 000000000..d39d7f69d
--- /dev/null
+++ b/results/classifier/no-thinking-deepseek-r1:32b/output/syscall/1861341
@@ -0,0 +1,33 @@
+
+
+
+ARM QEMU: Unknown syscall 397
+
+QEMU is reporting 
+
+```
+Unknown syscall 397
+```
+
+(statx if I read tables right) when used via flatpak for ARM images on x86_64. This has been reproduced on Fedora and Gentoo.
+
+To reproduce:
+
+- get flatpak KDE 5.12 for arm: 
+
+flatpak install --user org.kde.Sdk/arm/5.12 org.kde.Platform/arm/5.12
+
+
+- run qmake inside Sdk:
+
+QEMU_STRACE=1 flatpak run --filesystem=host --command=qmake org.kde.Sdk/arm/5.12 .
+
+
+You will get a host of messages with unknown syscall. In practice, qmake will fail to find .pro files if you have them in that folder and libraries in the system.
+
+As far as I understand, Flatpak images are built on AARCH64 hardware. 
+
+My config on Gentoo:
+
+kernel: 4.19.86-gentoo x86_64
+app-emulation/qemu: ~4.2.0-r1 , same with 4.0.0
\ No newline at end of file