diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2-tmp/reasoning/device/1689003 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/reasoning/device/1689003')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/reasoning/device/1689003 | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/results/classifier/deepseek-2-tmp/reasoning/device/1689003 b/results/classifier/deepseek-2-tmp/reasoning/device/1689003 deleted file mode 100644 index 4694ffbb..00000000 --- a/results/classifier/deepseek-2-tmp/reasoning/device/1689003 +++ /dev/null @@ -1,13 +0,0 @@ -<think> -Alright, let's tackle this bug report classification step by step. The user is reporting an issue with USB passthrough in QEMU not working for their new smartphone. They found that a SET CONFIGURATION request was NACKed by the device, possibly because another host had already sent it. - -They mention they wrote a program to fake a successful libusb_set_configuration call and used LD_PRELOAD, which worked. So, the problem lies in how QEMU handles failed libusb_set_configuration calls. - -Looking at the provided code in host-libusb.c, QEMU doesn't attempt to claim the interface if libusb_set_configuration fails. The user suggests that QEMU should try claiming the device even on failure. - -The possible categories include 'device', which seems relevant here because it's about USB devices and their interaction with QEMU. Other options like 'network' or 'graphic' don't fit as this is specifically about USB functionality. - -Therefore, the most appropriate category for this bug report is 'device'. -</think> - -device
\ No newline at end of file |