summary refs log tree commit diff stats
path: root/results/classifier/108/other/1900919
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/108/other/1900919')
-rw-r--r--results/classifier/108/other/190091962
1 files changed, 62 insertions, 0 deletions
diff --git a/results/classifier/108/other/1900919 b/results/classifier/108/other/1900919
new file mode 100644
index 000000000..1c3e88567
--- /dev/null
+++ b/results/classifier/108/other/1900919
@@ -0,0 +1,62 @@
+other: 0.884
+graphic: 0.874
+device: 0.853
+semantic: 0.843
+PID: 0.811
+permissions: 0.801
+performance: 0.783
+debug: 0.753
+network: 0.729
+files: 0.635
+socket: 0.541
+vnc: 0.536
+boot: 0.447
+KVM: 0.408
+
+PXB selected as root bus incorrectly
+
+release: 4c41341af76cfc85b5a6c0f87de4838672ab9f89
+
+qdev_device_add() will search for the "closest" bus possible, and bail out early if that bus is a root bus. pxb devices are considered root buses and so if you either
+1. Add a PCI device on the QEMU command line *after* a pxb device, or
+2. Add an integrated PCI device (like a watchdog)
+
+#1: -device pxb-pcie,id=cxl.0,bus=pcie.0,bus_nr=52 -device ahci,id=sata0,addr=0x8
+#2: -watchdog i6300esb -device pxb-pcie,id=cxl.0,bus=pcie.0,bus_nr=52
+
+The PXB will get selected as the bus (instead of the real root bus) and this will cause an assertion failure with the message like "qemu-system-x86_64: -device ahci,id=sata0,addr=0x8: PCI: Only PCI/PCIe bridges can be plugged into pxb-pcie"
+
+I think this is relatively solvable in the code base by determining if a bus is an expander, and skipping it if so. However, I wonder if it makes more sense to just allow expanders to have endpoint devices.
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+