add deepseek and gemma results

1 files changed, 26 insertions, 0 deletions

diff --git a/results/classifier/gemma3:12b/device/1640 b/results/classifier/gemma3:12b/device/1640
new file mode 100644
index 000000000..c13345f56
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1640
@@ -0,0 +1,26 @@
+
+aarch64: usb_mtp_get_data: Assertion `(s->dataset.size == 0xFFFFFFFF) || (s->dataset.size == d->offset)' failed
+Description of problem:
+When attempting to write to an MTP device in QEMU 8.0.0 on arm64, QEMU will crash at runtime with the following error:
+`qemu-system-aarch64: ../hw/usb/dev-mtp.c:1819: usb_mtp_get_data: Assertion '(s->dataset.size == 0xFFFFFFFF) || (s->dataset.size == d->offset)' failed.`
+
+This was observed in Nixpkgs where we use QEMU to provide automated testing of MTP devices for GVFS and jmtpfs, the full log for that test run that crashes due to this QEMU regression on arm64 is available here https://hydra.nixos.org/build/218858556/nixlog/1
+Steps to reproduce:
+1. Launch a QEMU virtual machine with `-usb -device usb-mtp,rootdir=/tmp,readonly=false` using any QEMU version above 6.0.0
+2. Mount the MTP device using something like:
+   ```
+   mkdir mtpDevice && jmtpfs mtpDevice
+   ```
+3. Try to write to the mtp device:
+   ```
+   dd if=/dev/urandom of=./mtpDevice/file
+   ```
+4. Observe that QEMU will crash when trying to write to the device, like this:
+   ```
+   client # 10+0 records in
+   client # 10+0 records out
+   client # 10485760 bytes (10 MB, 10 MiB) copied, 0.0318363 s, 329 MB/s
+   client # qemu-system-aarch64: ../hw/usb/dev-mtp.c:1819: usb_mtp_get_data: Assertion '(s->dataset.size == 0xFFFFFFFF) || (s->dataset.size == d->offset)' failed.error
+   ```
+Additional information:
+