blob: 52f0e465b627053ccdff4757eaa0045f238a12f0 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I need to classify the given bug report into one of the provided categories. Let me start by understanding the problem described.
The bug report mentions an assertion failure in hw/usb/core.c:727. The specific error is that the process ID (pid) doesn't match either USB_TOKEN_IN or USB_TOKEN_OUT. This indicates a problem with how USB endpoints are being handled, specifically during token processing.
Looking at the backtrace, the issue occurs in usb_ep_get, which is part of the QEMU's USB core handling. The function ohci_service_td and related functions in hcd-ohci.c suggest that this relates to OHCI (Open Host Controller Interface) implementation for USB devices.
Since the failure is within the USB core code and involves token processing during device communication, it falls under the category of USB-related issues. In the provided categories, 'device' seems appropriate as it refers to hardware device handling in QEMU.
Other possible categories like 'network', 'graphic', or 'kernel' don't seem relevant here since the issue is specifically with USB functionality.
</think>
The bug report indicates a problem within the USB core implementation of QEMU. The assertion failure occurs during USB token processing, pointing to an issue with device handling.
**device**
|