Bug 2234340
Summary: | Hit 'watchdog: BUG: soft lockup - CPU# stuck for ...' messages when dd on 32 xhci usb devices concurrent in guest | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Yiqian Wei <yiwei> |
Component: | qemu-kvm | Assignee: | Virtualization Maintenance <virt-maint> |
qemu-kvm sub component: | USB | QA Contact: | yduan |
Status: | CLOSED MIGRATED | Docs Contact: | |
Severity: | low | ||
Priority: | unspecified | CC: | coli, jinzhao, nilal, virt-maint, vkuznets, xuwei, yduan |
Version: | 9.3 | Keywords: | MigratedToJIRA |
Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-22 17:43:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yiqian Wei
2023-08-24 02:13:34 UTC
This looks like a slow xhci emulation in QEMU, reassigning. Apologies first - I asked a question in the Jira/RHELPLAN issue which of course isn't recorded here, so even though this will be repeated by the mirroring bot before we convert to Jira only issues... I asked Gerd "can you provide some thoughts/context for this issue. Thanks!" His response - " xhci runs with the BQL, so this could simply be lock contention in qemu. Could also be a guest kernel bug. Is this a regression? I'm wondering where this test case comes from. If you are looking for storage options with good performance and support for many disks you wouldn't pick usb but virtio-scsi or maybe virtio-blk. Testing parallel access to 32 usb disks looks a bit pointless to me ... " So I've added the needinfo here (although the answer may end up in RHEL / Jira only) Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |