diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/gemma3:12b/device/1794 | 28 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/device/1794187 | 15 | ||||
| -rw-r--r-- | results/classifier/gemma3:12b/device/1794939 | 18 |
3 files changed, 61 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/device/1794 b/results/classifier/gemma3:12b/device/1794 new file mode 100644 index 00000000..4e5d2e0f --- /dev/null +++ b/results/classifier/gemma3:12b/device/1794 @@ -0,0 +1,28 @@ + +Virtio-GPU doesn't fill Response data for cursor queue +Description of problem: +Implementation of virtio-gpu in Qemu is likely not fill Response header in cursor commands. + +Inside the virtio 1.2 specification, document said: +``` +VIRTIO_GPU_CMD_UPDATE_CURSOR + Update cursor. Request data is struct virtio_gpu_update_cursor. Response type is VIRTIO_GPU_RESP_OK_NODATA. + Full cursor update. Cursor will be loaded from the specified resource_id and will be moved to pos. The driver must + transfer the cursor into the resource beforehand (using control queue commands) and make sure the commands to fill + the resource are actually processed (using fencing). + +VIRTIO_GPU_CMD_MOVE_CURSOR + Move cursor. Request data is struct virtio_gpu_update_cursor. Response type is VIRTIO_GPU_RESP_OK_NODATA. + Move cursor to the place specified in pos. The other fields are not used and will be ignored by the device. +``` +The cursor commands do have a response like control commands. + +But in [hw/display/virtio-gpu.c#L1136](https://gitlab.com/qemu-project/qemu/-/blob/master/hw/display/virtio-gpu.c#L1136), QEMU doesn't care anything about response, just fetching command and execute. + +It this a Implementation compromise or I missing something in the specification? +Steps to reproduce: +1. Write any kernel that using virtio-gpu. +2. Run on qemu. +3. No response on cursor command. +Additional information: +Specification: [virtio-v1.2-cs01.html](https://docs.oasis-open.org/virtio/virtio/v1.2/cs01/virtio-v1.2-cs01.html#x1-3650007) diff --git a/results/classifier/gemma3:12b/device/1794187 b/results/classifier/gemma3:12b/device/1794187 new file mode 100644 index 00000000..4c0097fe --- /dev/null +++ b/results/classifier/gemma3:12b/device/1794187 @@ -0,0 +1,15 @@ + +improve error message, when using raspi3 and RAM>4G + +Running `qemu-system-aarch64 image-aarch64.iso --machine raspi3 -m 8G` prints this error message: + +``` +Unexpected error in visit_type_uintN() at /builddir/build/BUILD/qemu-3.0.0/qapi/qapi-visit-core.c:164: +qemu-system-aarch64: Parameter 'vcram-base' expects uint32_t +``` + +The problem is, that you musn't use more than 4 GB RAM for machine raspi3. As it took me some time to figure that out, I'd be glad, if you can print better error message, like you do, when using more than 4 CPU cores with machine raspi3: + +``` +Invalid SMP CPUs 8. The max CPUs supported by machine 'raspi3' is 4 +``` \ No newline at end of file diff --git a/results/classifier/gemma3:12b/device/1794939 b/results/classifier/gemma3:12b/device/1794939 new file mode 100644 index 00000000..a8b15db6 --- /dev/null +++ b/results/classifier/gemma3:12b/device/1794939 @@ -0,0 +1,18 @@ + +QEMU does not build with vte v2.91 + +when I build qemu with vte support and vte-2.91 installed I get the following deprecation warning: + +error: ‘vte_terminal_set_encoding’ is deprecated [-Werror=deprecated-declarations] + vte_terminal_set_encoding(VTE_TERMINAL(vc->vte.terminal), "UTF-8", NULL); + ^~~~~~~~~~~~~~~~~~~~~~~~~ +In file included from /usr/include/vte-2.91/vte/vte.h:35 + +I looked for the commit in vte that deprecated the offending function (a17e714d), which led me to the thread: + +https://gitlab.gnome.org/GNOME/vte/issues/3 + +It looks like from this version forward vte forces us to use utf-8, such that this function call becomes unnecessary in QEMU. + +Cheers, +Bastian \ No newline at end of file |