add gemma accelerator classification results

5 files changed, 115 insertions, 0 deletions

diff --git a/results/classifier/accel-gemma3:12b/manual-review/1586229 b/results/classifier/accel-gemma3:12b/manual-review/1586229
new file mode 100644
index 000000000..42bfb0dc2
--- /dev/null
+++ b/results/classifier/accel-gemma3:12b/manual-review/1586229
@@ -0,0 +1,28 @@
+
+seabios hell
+
+getting weird annoying seabios hell and not sure how to fix it.
+
+ok.
+
+there IS a SEA-BIOS. There IS a way in.
+
+-I found it by mistake.(and yall need to move the BIOS key...its in the wrong place)
+
+I was tryng to boot Yosemite to re-install. I mashed the key too early and it wanted to boot the hard drive.
+
+Apparently the bios loads AFTER the hard drive wants to boot, not BEFORE it.And it will ONLY load when booting a hard disk.
+
+..Booting hard disk...[mash F8 here but let go and wait]
+eventually will want to load the OS and clear the screen[mash F8 again]
+
+--Youre in!
+
+Its tiny, like a mini award bios but youre in! 
+-Change anything HERE, though...and kiss booting a cd goodbye!
+
+Im trying to diagnose a black screen, seems related to seabios, not the vga driver.
+
+-mayhaps wants to boot hard disk but in fact its not bootable as the installer hung(and often unices install bootloader late in process)?
+
+I cant boot the disc to reinstall to tell. But I have a few dos iso lying around...hmmm.
\ No newline at end of file
diff --git a/results/classifier/accel-gemma3:12b/manual-review/1811 b/results/classifier/accel-gemma3:12b/manual-review/1811
new file mode 100644
index 000000000..9252b50f8
--- /dev/null
+++ b/results/classifier/accel-gemma3:12b/manual-review/1811
@@ -0,0 +1,37 @@
+
+ppc serial appears to have a maximum ratio of output to input, hides output and only writes it on subsequent input(?!)
+Description of problem:
+When pasting in large chunks of text, the echo is partial, but completes with subsequent writes (and is drained when the writes are small). Sorry this is really stupid, see video.
+
+(also, when booting, the console stops at
+```
+Building dt strings...
+Building dt structure...
+Device tree strings 0x00000000062c0000 -> 0x00000000062c0b90
+Device tree struct  0x00000000062d0000 -> 0x00000000062e0000
+Quiescing Open Firmware ...
+Booting Linux via __start() @ 0x0000000002000000 ...
+Linux ppc64le
+#1 SMP Debian 6.
+```
+and then continues with more messages from just after the dot:
+```
+Linux ppc64le
+#1 SMP Debian 6.[   15.683156] vio vio: uevent: failed to send synthetic uevent: -19
+vio: Failed to write 'add' to '/sys/devices/vio/uevent', ignoring: No such device
+/dev/vda2: clean, 17371/987360 files, 345018/3942144 blocks
+```
+)
+Steps to reproduce:
+1. `cat > /dev/null`
+2. paste in a couple solid lines
+3. observe that the echo completed mid-line
+4. paste in a couple more solid lines
+5. observe that the echo includes the end of the first few lines, and the start of the second set
+6. ^D
+7. observe that with every key input into the shell, you get a few bytes back, and those bytes are the tail-end of the second set of lines
+8. when the echo buffer is drained, it's drained
+Additional information:
+Demo video: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1041707;filename=2023-07-21+17-59-25.mp4;msg=5
+
+Downstream bug: https://bugs.debian.org/1041707
diff --git a/results/classifier/accel-gemma3:12b/manual-review/1876568 b/results/classifier/accel-gemma3:12b/manual-review/1876568
new file mode 100644
index 000000000..452a26340
--- /dev/null
+++ b/results/classifier/accel-gemma3:12b/manual-review/1876568
@@ -0,0 +1,18 @@
+
+"semtimedop" implementation missing in qemu?
+
+I was trying to do an ARMv6 cross compile with qemu-user-static when I ran into this:
+
+https://travis-ci.com/github/VDR4Arch/vdr4arch/jobs/326884620#L1596
+
+I was close to giving up when I found the following:
+
+https://github.com/osrf/multiarch-docker-image-generation/issues/36
+
+Most important comment may be this one:
+
+https://github.com/osrf/multiarch-docker-image-generation/issues/36#issuecomment-610626796
+
+> The "correct" way to fix this does seem to be to implement semtimedop in qemu.
+
+I don't know how much involved the people, discussing there, are in the qemu development but I thought it may be a good idea to bring this to your attention. If this is already fixed (I haven't found any bug about "semtimedop"), then please just close this one and tell me in which version the fix will be included.
\ No newline at end of file
diff --git a/results/classifier/accel-gemma3:12b/manual-review/2893 b/results/classifier/accel-gemma3:12b/manual-review/2893
new file mode 100644
index 000000000..405e9aa66
--- /dev/null
+++ b/results/classifier/accel-gemma3:12b/manual-review/2893
@@ -0,0 +1,13 @@
+
+with m4 mac mini windows 11 arm 64 iso not booting for installation
+Description of problem:
+Trying to run win11 arm 64 version in m4 mac mini and the ios failed to boot 
+
+i went to the efi shell and tried to boot from there and it just hangs no problem reported 
+
+when i attach the serial to stdio i get the error convertprogress failed to find range errors
+Steps to reproduce:
+1. In m4 mac mini download win11 arm 64 iso from microsoft site
+2. run the above mentioned command and you will see that it does not boot
+
+/label ~"kind::Bug"
diff --git a/results/classifier/accel-gemma3:12b/manual-review/2909 b/results/classifier/accel-gemma3:12b/manual-review/2909
new file mode 100644
index 000000000..c16186dfd
--- /dev/null
+++ b/results/classifier/accel-gemma3:12b/manual-review/2909
@@ -0,0 +1,19 @@
+
+Corrupt qcow2 images with broken bitmap unfixable
+Description of problem:
+During a backup of a VM (via bitmaps), the disk of the VM/Snapshot went out of space.
+The VM was stopped, leaving the image in a bad state.
+
+But now when trying to repair it, it was stuck:
+```
+# qemu-img check -r all /dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9
+qemu-img: Could not open '/dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9': Bitmap '' doesn't satisfy the constraints
+```
+
+But if you want to remove the bitmap:
+```
+# qemu-img bitmap --remove /dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9 ''
+qemu-img: Could not open '/dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9': qcow2: Image is corrupt; cannot be opened read/write
+```
+
+It seems like qemu-img check needs some option to clear invalid bitmaps. So the image can be repaired including dropping the invalid bitmap.