5 files changed, 117 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/device/119 b/results/classifier/gemma3:12b/device/119
new file mode 100644
index 00000000..fea0d951
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/119
@@ -0,0 +1,2 @@
+
+USB assert failure on hcd-uhci.c
diff --git a/results/classifier/gemma3:12b/device/1190525 b/results/classifier/gemma3:12b/device/1190525
new file mode 100644
index 00000000..c557976a
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1190525
@@ -0,0 +1,37 @@
+
+fdisk still shows the "/dev/sdb" partitions even after the removal of scsi disk
+
+RHEL guest shows the partittions even after the removal of scsi disk:
+fdisk still shows the "/dev/sdb" partitions even after the removal of scsi disk.
+
+Guest details:
+-------------------
+Kernel : 2.6.32-358
+
+
+Host Details :
+
+Upstream Kernel, Qemu, Libvirt and virt-manager
+---------------------------------------------------------------------
+
+kernel version : 3.9.0+
+qemu version : QEMU emulator version 1.5.0
+libvirt version : 1.0.5
+virt-install : 0.600.3
+
+
+Steps to reproduce the issue:
+
+I. Add the SCSI disk through the virt-manager.
+2. Create the partition using fdisk  (eg: /dev/sbb) 
+3. Create a filesystem and format using mkfs.ext3 or mkfs.ext4 
+4. Remove the scsi disk  through the virt-manager. 
+5. Again run the fdisk /dev/sdb, the guests still shows the partition even after the removal of the disk.
+
+This issue is not seen with virt-io disk.
+
+This issue is also reproducible without even creating the partitions.
+
+Expected Result:
+
+The output of fdisk /dev/sd*  should not show the enties after the removal of scsi disks
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/device/1196 b/results/classifier/gemma3:12b/device/1196
new file mode 100644
index 00000000..2e6ca527
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1196
@@ -0,0 +1,13 @@
+
+Guest could not enable pci AtomicOp requests for passthrough device
+Description of problem:
+Guest could not enable pci AtomicOp requests for passthrough device. 
+
+sudo setpci -v -d *:706t 8c.b=40 // enable pci AtomicOp requests bit in the guest os.
+
+Host could not see the bit by command "sudo lspci -vvv -s 03:00.0".
+Steps to reproduce:
+1. sudo setpci -v -d *:706t 8c.b=40 // in the guest os
+2. sudo lspci -vvv -s 03:00.0 // in the host os
+Additional information:
+
diff --git a/results/classifier/gemma3:12b/device/1196145 b/results/classifier/gemma3:12b/device/1196145
new file mode 100644
index 00000000..45db9129
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1196145
@@ -0,0 +1,19 @@
+
+usb-host: hostaddr=0XX is parsed as octal number
+
+when doing
+
+device_add usb-host,hostaddr=010
+
+taking 010 in the format of both lsusb or udev, qemu parses an octal number and assumes hostaddr=8.
+(i used a 2.0 device on the ehci.0 bus)
+at least to me that is confusing.
+
+also:
+
+when adding a non-existent usb device (bogus hostaddr), the following is created according to 'usb info':
+
+  Device 1.0, Port 1, Speed 1.5 Mb/s, Product USB Host Device
+
+in usb_qdev_init():
+usb_claim_port is called but usb_device_init does not report an error and thus usb_release_port is not called.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/device/1198350 b/results/classifier/gemma3:12b/device/1198350
new file mode 100644
index 00000000..3a0bbd63
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1198350
@@ -0,0 +1,46 @@
+
+USB pass-through fails with USBDEVFS_DISCONNECT: Invalid argument
+
+Host Gentoo linux 32bit
+Guest Windows XP SP3
+qemu 1.4.2 and
+qemu fresh get clone and build 2013-07-04 (version1.5.50)
+qemu command line
+
+qemu-system-i386 -enable-kvm localtime -m 2047 -boot d /archive3/qemu/WindowsXP.img -net nic,model=rtl8139 -net user -usb -device usb-ehci,id=ehci -usbdevice host:1493:19
+
+The device I am trying to use with the guest is an interface for the Suunto Ambit 2 GPS watch which has no linux support.
+
+When the USB device is plugged in qemu reports to the command line:
+
+USBDEVFS_DISCONNECT: Invalid argument
+Invalid argument
+
+dmesg shows
+
+[237755.495968] usb 2-1.5: new full-speed USB device number 34 using ehci-pci
+[237755.582778] usb 2-1.5: config 1 has an invalid interface number: 1 but max is 0
+[237755.582781] usb 2-1.5: config 1 has no interface number 0
+[237755.583628] usb 2-1.5: New USB device found, idVendor=1493, idProduct=0019
+[237755.583631] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
+[237755.583633] usb 2-1.5: Product: Ambit
+[237755.583634] usb 2-1.5: Manufacturer: Suunto
+[237755.583636] usb 2-1.5: SerialNumber: CE83095110000700
+[237756.584937] usb 2-1.5: reset full-speed USB device number 34 using ehci-pci
+[237756.832658] usb 2-1.5: reset full-speed USB device number 34 using ehci-pci
+[237757.143585] usb 2-1.5: usbfs: process 12684 (qemu-system-i38) did not claim interface 1 before use
+
+In the windows guest Device Manager a HID device is listed but nothing else happens, no found new hardware dialog or the Suunto software (which is sitting there waiting) is not triggered as it should be.
+
+I have tried successfully with several other devices (flash drive, mouse, printer and video capture device). Because this device pretends to be an HID device my kernel's hid-generic driver was picking it up first until I modified hid-core.c to ignore this vendorid/productid. But still no joy.
+
+I'm guessing it has something to do with the the dmesg lines:
+
+[237755.582778] usb 2-1.5: config 1 has an invalid interface number: 1 but max is 0
+[237755.582781] usb 2-1.5: config 1 has no interface number 0
+
+But read that these warnings are not important though I don't get them for other devices. Nor do I get:
+
+[237757.143585] usb 2-1.5: usbfs: process 12684 (qemu-system-i38) did not claim interface 1 before use
+
+I've done alot of searching and I've run out of ideas. Any help would be great.
\ No newline at end of file