diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-17 09:10:43 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-17 09:10:43 +0200 |
| commit | f2ec263023649e596c5076df32c2d328bc9393d2 (patch) | |
| tree | 5dd86caab46e552bd2e62bf9c4fb1a7504a44db4 /results/scraper/fex/847 | |
| parent | 63d2e9d409831aa8582787234cae4741847504b7 (diff) | |
| download | qemu-analysis-main.tar.gz qemu-analysis-main.zip | |
Diffstat (limited to 'results/scraper/fex/847')
| -rw-r--r-- | results/scraper/fex/847 | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/results/scraper/fex/847 b/results/scraper/fex/847 new file mode 100644 index 000000000..dd6dab908 --- /dev/null +++ b/results/scraper/fex/847 @@ -0,0 +1,14 @@ +Geekbench 4 Camera max-threads rare deadlock +This is rare, semi-reproducible you need to loop with -T the same as host + +```bash +count=0; while : +do +let "count+=1"; Bin/FEXLoader -T 24 -s --aotir-load -- ../../Geekbench-4.4.4-Linux/geekbench_x86_64 --section 2 --workload 213 && echo worked $count +sleep 1 +done +``` + +When you hit a deadlock, you can gdb attach and see all threads are in a futex syscall, and they are all waiting on the same futex: + +in gdb you can use `thread apply all print/x $rdi` to print out which futex each thread is on |