summaryrefslogtreecommitdiffstats
path: root/results/classifier/zero-shot/105/device/1863441
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 19:39:53 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 19:39:53 +0200
commitdee4dcba78baf712cab403d47d9db319ab7f95d6 (patch)
tree418478faf06786701a56268672f73d6b0b4eb239 /results/classifier/zero-shot/105/device/1863441
parent4d9e26c0333abd39bdbd039dcdb30ed429c475ba (diff)
downloademulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.tar.gz
emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.zip
restructure results
Diffstat (limited to 'results/classifier/zero-shot/105/device/1863441')
-rw-r--r--results/classifier/zero-shot/105/device/186344144
1 files changed, 44 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/105/device/1863441 b/results/classifier/zero-shot/105/device/1863441
new file mode 100644
index 00000000..b6349716
--- /dev/null
+++ b/results/classifier/zero-shot/105/device/1863441
@@ -0,0 +1,44 @@
+device: 0.729
+instruction: 0.706
+semantic: 0.705
+mistranslation: 0.688
+other: 0.677
+graphic: 0.652
+vnc: 0.607
+socket: 0.601
+network: 0.548
+boot: 0.478
+assembly: 0.452
+KVM: 0.330
+
+cmd_mode_sense always reports 0x70, no CDROM present
+
+cmd_mode_sense
+ https://git.qemu.org/?p=qemu.git;a=blob;f=hw/ide/atapi.c;hb=refs/heads/master#l852
+always reports 0x70 in byte 2 returned, indicating no CD-ROM present.
+
+If CD-ROM is present, should report 0x01 (or 0x11).
+If CD-ROM absent, should report 0x70.
+
+Hi, if you can quote the relevant spec, would you like to include that in a commit message and send a patch?
+
+Also, does this result in a bug anywhere visible that we can test against?
+
+Since I posted this bug report, I have done a little more research and this specific part of this command is actually quite obsolete. It use to be documented (MMC v1.2 Draft), but later versions have actually removed this part of the command, even stating "obsolete" in some of the documentation.
+
+If you want to still allow it, it actually does state 0x70 is an empty drive. However, being it is so obsolete, you may wish to change this status to closed.
+
+Thanks for asking. I don't mind if you close this bug report.
+
+Ben
+
+Roger that, thanks!
+
+I don't think we're very careful about which version we try to emulate. In practice it's "Whatever seems to work across the largest swatch of guest operating systems simultaneously".
+
+If this comes up again, feel free to file against a specific guest OS that appears to be non-functioning.
+
+Thanks!
+
+--js
+