summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/files/1289898
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/files/1289898
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloademulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/files/1289898')
-rw-r--r--results/classifier/gemma3:12b/files/12898988
1 files changed, 8 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/files/1289898 b/results/classifier/gemma3:12b/files/1289898
new file mode 100644
index 00000000..b005995c
--- /dev/null
+++ b/results/classifier/gemma3:12b/files/1289898
@@ -0,0 +1,8 @@
+
+qemu-system-ppc64 easily cause file corruption
+
+the qemu-system-ppc64 is used to run Fedora-19 on RHEL 5.3.
+Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms:
+
+* using scp to transfer a tar.bz file from the RHEL 5.3 host to the Fedora-19 PPC VM, found the size is correct, but the content is corrupted from the middle of the 80+ MB file.  re-transfer again, got a correct file. But after untar, found some extracted files corrupted.
+The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover.
\ No newline at end of file