blob: 9e7248add44adf6b3f5553771f4b89b67e4c0466 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
|
network: 0.838
device: 0.829
graphic: 0.827
performance: 0.708
socket: 0.706
PID: 0.664
debug: 0.516
files: 0.514
vnc: 0.496
boot: 0.427
semantic: 0.227
permissions: 0.220
KVM: 0.147
other: 0.050
hw/core/gpio.c:108: qdev_get_gpio_in_named: Assertion n >= 0 && n < gpio_list->num_in failed
Description of problem:
It's quite easy to trigger the assertion ``hw/core/gpio.c:108: qdev_get_gpio_in_named: Assertion n >= 0 && n < gpio_list->num_in failed``
Steps to reproduce:
Run one of the following command lines:
1. ``./qemu-system-aarch64 -display none -machine qcom-dc-scm-v1-bmc -device max1111``
2. ``./qemu-system-aarch64 -display none -machine fby35-bmc -device max1110``
3. ``./qemu-system-aarch64 -display none -machine yosemitev2-bmc -device corgi-ssp``
|