summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/device/168
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--results/classifier/gemma3:12b/device/1682
-rw-r--r--results/classifier/gemma3:12b/device/168139811
-rw-r--r--results/classifier/gemma3:12b/device/16814049
-rw-r--r--results/classifier/gemma3:12b/device/168143936
-rw-r--r--results/classifier/gemma3:12b/device/168524221
-rw-r--r--results/classifier/gemma3:12b/device/16855264
-rw-r--r--results/classifier/gemma3:12b/device/1687309156
-rw-r--r--results/classifier/gemma3:12b/device/168900314
8 files changed, 253 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/device/168 b/results/classifier/gemma3:12b/device/168
new file mode 100644
index 00000000..0d89d65f
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/168
@@ -0,0 +1,2 @@
+
+ivshmem PCI device exposes wrong endianness on ppc64le
diff --git a/results/classifier/gemma3:12b/device/1681398 b/results/classifier/gemma3:12b/device/1681398
new file mode 100644
index 00000000..1f1a714c
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1681398
@@ -0,0 +1,11 @@
+
+hw/core: segmentation fault
+
+Reproducer:
+ $i386-softmmu/qemu-system-i386 -S -machine isapc,accel=tcg -device amd-iommu
+Segmentation fault (core dumped)
+
+Partial bt:
+#0  bus_add_child (child=0x555556d4e520, bus=0x0) at hw/core/qdev.c:88
+#1  qdev_set_parent_bus (dev=0x555556d4e520, bus=bus@entry=0x0)
+at hw/core/qdev.c:119
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/device/1681404 b/results/classifier/gemma3:12b/device/1681404
new file mode 100644
index 00000000..f03da661
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1681404
@@ -0,0 +1,9 @@
+
+hw/ppc: Aborted (core dumped)
+
+Reproducable:
+$ ./ppc64-softmmu/qemu-system-ppc64 -S -machine ppce500,accel=tcg -device spapr-pci-host-bridge
+
+
+qemu/hw/ppc/spapr_pci.c:1567:spapr_phb_realize: Object 0x55bda99744a0 is not an instance of type spapr-machine
+Aborted (core dumped)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/device/1681439 b/results/classifier/gemma3:12b/device/1681439
new file mode 100644
index 00000000..64123f5d
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1681439
@@ -0,0 +1,36 @@
+
+dma_blk_cb leaks memory map handles on misaligned IO
+
+Since upgrading to QEMU 2.8.0, my Windows 7 64-bit virtual machines
+started crashing due to the assertion quoted in the summary failing.
+The assertion in question was added by commit 9972354856 ("block: add
+BDS field to count in-flight requests").  My tests show that setting
+discard=unmap is needed to reproduce the issue.  Speaking of
+reproduction, it is a bit flaky, because I have been unable to come up
+with specific instructions that would allow the issue to be triggered
+outside of my environment, but I do have a semi-sane way of testing that
+appears to depend on a specific initial state of data on the underlying
+storage volume, actions taken within the VM and waiting for about 20
+minutes.
+
+Here is the shortest QEMU command line that I managed to reproduce the
+bug with:
+
+    qemu-system-x86_64 \
+        -machine pc-i440fx-2.7,accel=kvm \
+        -m 3072 \
+        -drive file=/dev/lvm/qemu,format=raw,if=ide,discard=unmap \
+	-netdev tap,id=hostnet0,ifname=tap0,script=no,downscript=no,vhost=on \
+        -device virtio-net-pci,netdev=hostnet0 \
+	-vnc :0
+
+The underlying storage (/dev/lvm/qemu) is a thin LVM snapshot.
+
+QEMU was compiled using:
+
+    ./configure --python=/usr/bin/python2.7 --target-list=x86_64-softmmu
+    make -j3
+
+My virtualization environment is not really a critical one and
+reproduction is not that much of a hassle, so if you need me to gather
+further diagnostic information or test patches, I will be happy to help.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/device/1685242 b/results/classifier/gemma3:12b/device/1685242
new file mode 100644
index 00000000..9c98bceb
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1685242
@@ -0,0 +1,21 @@
+
+ovmf hangs at efi with virtio-net memory hotplug
+
+with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled and it has a virtio-net devices
+
+the ovmf images where compiled from https://github.com/tianocore/edk2 (current master)
+
+reproducer:
+
+qemu-system-x86_64 -drive 'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive 'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std -netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet' -display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G'
+
+interestingly, it works when you do the following:
+
+- omit the virtio-net-pci device
+- use seabios
+- use less maxmem, e.g. 512G
+
+qemu was compiled from source (v2.9.0) with following options:
+
+./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls --enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi --disable-smartcard --audio-drv-list="alsa" --enable
+-spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk --enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs --disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/device/1685526 b/results/classifier/gemma3:12b/device/1685526
new file mode 100644
index 00000000..c7db2cb0
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1685526
@@ -0,0 +1,4 @@
+
+UEFI firmware can't write to "fake" FAT hard disk
+
+Using the Tianocore OVMF UEFI firmware, a UEFI application cannot write to the emulated fat disk (-hda fat:rw:path/here). A file will get created or written, but will be corrupted.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/device/1687309 b/results/classifier/gemma3:12b/device/1687309
new file mode 100644
index 00000000..aca171f7
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1687309
@@ -0,0 +1,156 @@
+
+Assertion !usb_packet_is_inflight(p) fails in OHCI
+
+I'm trying to get a USB web camera working in Qemu & Raspbian. USB works and V4L shows device info correctly and capturing frames from the camera works sometimes, but mostly it crashes with error message:
+
+qemu-system-arm: hw/usb/core.c:558: usb_packet_setup: Assertion `!usb_packet_is_inflight(p)' failed.
+
+This looks similar to the previous bug which also caused a crash on the same kind of assertion but the culprit was XHCI: https://bugs.launchpad.net/qemu/+bug/1653384
+
+
+== Versions ==
+
+QEMU emulator version 2.9.50 (v2.9.0-303-g81b2d5c-dirty),
+configured with
+./configure --target-list=arm-softmmu,arm-linux-user,armeb-linux-user --enable-libusb --enable-libssh2 --enable-debug
+
+libusb: 1.0.21
+
+Guest: 2017-04-10-raspbian-jessie-lite.img with kernel 4.4.34 for Raspbian on Qemu
+
+Command: /usr/local/bin/qemu-system-arm -kernel qemu-rpi-kernel/kernel-qemu-4.4.34-v4lm-jessie -cpu arm1176 -m 256 -M versatilepb -no-reboot -append "root=/dev/sda2 panic=1" -drive format=raw,file=2017-04-10-raspbian-jessie-lite.img -usb -usbdevice host:046d:0928 -net nic,model=virtio -net user,hostfwd=tcp::2222-:22
+
+Web camera is an old Logitech QuickCam Express Etch2 (046d:0928). It works otherwise without problems.
+
+
+== GDB Backtrace ==
+
+qemu-system-arm: hw/usb/core.c:558: usb_packet_setup: Assertion `!usb_packet_is_inflight(p)' failed.
+
+Thread 1 "qemu-system-arm" received signal SIGABRT, Aborted.
+0x00007fffdea6f428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
+54      ../sysdeps/unix/sysv/linux/raise.c: Tiedostoa tai hakemistoa ei ole.
+(gdb) bt full
+#0  0x00007fffdea6f428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
+        resultvar = 0
+        pid = 16526
+        selftid = 16526
+#1  0x00007fffdea7102a in __GI_abort () at abort.c:89
+        save_stage = 2
+        act = {__sigaction_handler = {sa_handler = 0x4, sa_sigaction = 0x4}, sa_mask = {__val = {140737488345776, 
+              140737488351076, 140737488345856, 48702688480, 140737352876032, 93825001457954, 558, 93825001458576, 0, 0, 
+              140736929192332, 140736930289240, 140736930302896, 260615966, 140736930289240, 93825001457954}}, 
+          sa_flags = -135479296, sa_restorer = 0x555555e20922}
+        sigs = {__val = {32, 0 <repeats 15 times>}}
+#2  0x00007fffdea67bd7 in __assert_fail_base (fmt=<optimized out>, 
+    assertion=assertion@entry=0x555555e20922 "!usb_packet_is_inflight(p)", 
+    file=file@entry=0x555555e20686 "hw/usb/core.c", line=line@entry=558, 
+    function=function@entry=0x555555e20b90 <__PRETTY_FUNCTION__.27044> "usb_packet_setup") at assert.c:92
+        str = 0x5555573e0800 ""
+        total = 4096
+#3  0x00007fffdea67c82 in __GI___assert_fail (assertion=0x555555e20922 "!usb_packet_is_inflight(p)", 
+    file=0x555555e20686 "hw/usb/core.c", line=558, 
+    function=0x555555e20b90 <__PRETTY_FUNCTION__.27044> "usb_packet_setup") at assert.c:101
+No locals.
+#4  0x0000555555b4015a in usb_packet_setup (p=0x555556e81bc8, pid=105, ep=0x55555733e180, stream=0, id=260615936, 
+    short_not_ok=false, int_req=false) at hw/usb/core.c:558
+        __PRETTY_FUNCTION__ = "usb_packet_setup"
+#5  0x0000555555b4f2ee in ohci_service_iso_td (ohci=0x555556e814c0, ed=0x7fffffffdda0, completion=0)
+    at hw/usb/hcd-ohci.c:852
+        int_req = false
+        dir = 2
+        len = 1023
+        str = 0x555555e233cf "in"
+        pid = 105
+        ret = -8788
+        i = -8912
+        dev = 0x55555733d070
+        ep = 0x55555733e180
+        iso_td = {flags = 4039218540, bp = 251170816, next = 260615872, be = 251173880, offset = {59386, 0, 6, 0, 53328, 
+            53376, 0, 0}}
+        addr = 260615936
+        starting_frame = 38252
+        relative_frame_number = 0
+        frame_count = 0
+        start_offset = 59386
+        next_offset = 0
+        end_offset = 0
+        start_addr = 251172858
+        end_addr = 251173880
+#6  0x0000555555b5055c in ohci_service_ed_list (ohci=0x555556e814c0, head=260608080, completion=0)
+    at hw/usb/hcd-ohci.c:1239
+        ed = {flags = 67080322, tail = 260614272, head = 260615936, next = 0}
+        next_ed = 0
+        cur = 260608080
+        active = 1
+        link_cnt = 1
+#7  0x0000555555b50857 in ohci_frame_boundary (opaque=0x555556e814c0) at hw/usb/hcd-ohci.c:1304
+        n = 12
+        ohci = 0x555556e814c0
+        hcca = {intr = {260608080 <repeats 32 times>}, frame = 38252, pad = 0, done = 0}
+#8  0x0000555555d12050 in timerlist_run_timers (timer_list=0x555556939600) at util/qemu-timer.c:536
+        ts = 0x555556ebc9b0
+        current_time = 224991592167
+        progress = false
+        cb = 0x555555b50778 <ohci_frame_boundary>
+        opaque = 0x555556e814c0
+#9  0x0000555555d1209c in qemu_clock_run_timers (type=QEMU_CLOCK_VIRTUAL) at util/qemu-timer.c:547
+No locals.
+#10 0x0000555555d1244e in qemu_clock_run_all_timers () at util/qemu-timer.c:662
+        progress = false
+        type = QEMU_CLOCK_VIRTUAL
+#11 0x0000555555d12bf9 in main_loop_wait (nonblocking=0) at util/main-loop.c:525
+        ret = 0
+        timeout = 499
+        timeout_ns = 977642
+#12 0x0000555555969440 in main_loop () at vl.c:1899
+No locals.
+#13 0x0000555555971229 in main (argc=21, argv=0x7fffffffe358, envp=0x7fffffffe408) at vl.c:4717
+        i = 0
+        snapshot = 0
+        linux_boot = 1
+        initrd_filename = 0x0
+        kernel_filename = 0x5555568d78c0 "qemu-rpi-kernel/kernel-qemu-4.4.34-v4lm-jessie"
+        kernel_cmdline = 0x5555568d8c80 "root=/dev/sda2 panic=1 "
+        boot_order = 0x0
+        boot_once = 0x0
+        ds = 0x55555718f750
+        cyls = 0
+        heads = 0
+        secs = 0
+        translation = 0
+        opts = 0x0
+        machine_opts = 0x5555568d8b20
+        hda_opts = 0x0
+        icount_opts = 0x0
+        accel_opts = 0x0
+        olist = 0x55555629fc80 <qemu_machine_opts>
+        optind = 21
+        optarg = 0x7fffffffe780 "user,hostfwd=tcp::2222-:22"
+        loadvm = 0x0
+        machine_class = 0x5555568eff50
+        cpu_model = 0x7fffffffe6c2 "arm1176"
+        vga_model = 0x555555d8d8c4 "std"
+        qtest_chrdev = 0x0
+        qtest_log = 0x0
+        pid_file = 0x0
+        incoming = 0x0
+        defconfig = true
+        userconfig = true
+        nographic = false
+        display_type = DT_GTK
+        display_remote = 0
+        log_mask = 0x0
+        log_file = 0x0
+        trace_file = 0x0
+        maxram_size = 268435456
+        ram_slots = 0
+        vmstate_dump_file = 0x0
+        main_loop_err = 0x0
+        err = 0x0
+        list_data_dirs = false
+        bdo_queue = {sqh_first = 0x0, sqh_last = 0x7fffffffe140}
+        __func__ = "main"
+
+
+(P.S. Tiedostoa tai hakemistoa ei ole = file or directory doesn't exist.)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/device/1689003 b/results/classifier/gemma3:12b/device/1689003
new file mode 100644
index 00000000..87b4d3e3
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1689003
@@ -0,0 +1,14 @@
+
+USB passthrough should not fail if SET CONFIGURATION fails
+
+QEMU's USB passthrough was not working for my new smartphone.
+
+While analyzing the problem, I found out that a SET CONFIGURATION Request was NACKed by the USB device (probably because a SET CONFIGURATION request was already sent from the host to the device).
+
+So I wrote a simple program to fake a successful call to libusb_set_configuration and did an LD_PRELOAD on this program before starting qemu, and it worked.
+
+Looking at QEMU's code in host-libusb.c, I can see that QEMU does not try to claim the interface if its call to libusb_set_configuration fails.
+
+I think QEMU should try to claim the device anyway even if libusb_set_configuration fails.
+
+I did my tests against QEMU 2.6.2, but as I can see from the source code, this problem should happen on all versions.
\ No newline at end of file