summaryrefslogtreecommitdiffstats
path: root/test/run_mambo_boot_test.sh
diff options
context:
space:
mode:
authorJoel Stanley <joel@jms.id.au>2018-12-12 15:32:57 +1030
committerStewart Smith <stewart@linux.ibm.com>2018-12-13 10:23:17 +1100
commit8da47e00d153617cdde28182f7e22f85a097cf8f (patch)
treeef7709f4d69443d77af2fd78b20bbed90ed20e4f /test/run_mambo_boot_test.sh
parent1a07f8b147b7e3bff392441651fded5e93055a00 (diff)
downloadtalos-skiboot-8da47e00d153617cdde28182f7e22f85a097cf8f.tar.gz
talos-skiboot-8da47e00d153617cdde28182f7e22f85a097cf8f.zip
test: Update qemu arguments to use bmc simulator
THe qemu skiboot platform as of 8340a9642bba ("plat/qemu: use the common OpenPOWER routines to initialize") uses the common aspeed BMC setup routines. This means a BT interface is always set up, and if the corresponding Qemu model is not present the timeout is 30 seconds. It looks like this every time an IPMI message is sent: BT: seq 0x9e netfn 0x06 cmd 0x31: Maximum queue length exceeded BT: seq 0x9d netfn 0x06 cmd 0x31: Removed from queue BT: seq 0x9f netfn 0x06 cmd 0x31: Maximum queue length exceeded BT: seq 0x9e netfn 0x06 cmd 0x31: Removed from queue BT: seq 0xa0 netfn 0x06 cmd 0x31: Maximum queue length exceeded BT: seq 0x9f netfn 0x06 cmd 0x31: Removed from queue Avoid this by adding the bmc simulator model to the Qemu powernv machine. Signed-off-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
Diffstat (limited to 'test/run_mambo_boot_test.sh')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud