From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: [PATCH] doc: Provide solution for qemuarm-stretch boot in QEMU
Date: Fri, 3 Nov 2017 17:32:34 +0300 [thread overview]
Message-ID: <20171103143234.11754-1-asmirnov@ilbers.de> (raw)
The QEMU 2.8+ should be used to run qemuarm-stretch image locally. Otherwise
there will be the following boot issue:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 69 at /build/linux-twocCo/linux-4.9.51/drivers/irqchip/irq-gic-common.c:80 gic_configure_irq+0xb4/0xb8
Modules linked in: virtio_blk(+) virtio_mmio virtio_ring virtio
CPU: 0 PID: 69 Comm: systemd-udevd Not tainted 4.9.0-4-armmp #1 Debian 4.9.51-1
Hardware name: Generic DT based system
[<c0114db8>] (unwind_backtrace) from [<c010ef30>] (show_stack+0x20/0x24)
[<c010ef30>] (show_stack) from [<c040debc>] (dump_stack+0x90/0xa4)
[<c040debc>] (dump_stack) from [<c014c368>] (__warn+0xf8/0x110)
[<c014c368>] (__warn) from [<c014c498>] (warn_slowpath_null+0x30/0x38)
[<c014c498>] (warn_slowpath_null) from [<c0440be4>] (gic_configure_irq+0xb4/0xb8)
[<c0440be4>] (gic_configure_irq) from [<c043fcbc>] (gic_set_type+0x6c/0x78)
[<c043fcbc>] (gic_set_type) from [<c01b5c68>] (__irq_set_trigger+0x6c/0x1b0)
[<c01b5c68>] (__irq_set_trigger) from [<c01b6328>] (__setup_irq+0x57c/0x644)
[<c01b6328>] (__setup_irq) from [<c01b65c0>] (request_threaded_irq+0xfc/0x19c)
[<c01b65c0>] (request_threaded_irq) from [<bf015af8>] (vm_find_vqs+0x58/0x388 [virtio_mmio])
[<bf015af8>] (vm_find_vqs [virtio_mmio]) from [<bf034498>] (init_vq+0x184/0x294 [virtio_blk])
[<bf034498>] (init_vq [virtio_blk]) from [<bf0350e0>] (virtblk_probe+0xdc/0x73c [virtio_blk])
[<bf0350e0>] (virtblk_probe [virtio_blk]) from [<bf003950>] (virtio_dev_probe+0x230/0x30c [virtio])
[<bf003950>] (virtio_dev_probe [virtio]) from [<c0587f2c>] (driver_probe_device+0x230/0x42c)
[<c0587f2c>] (driver_probe_device) from [<c0588228>] (__driver_attach+0x100/0x10c)
[<c0588228>] (__driver_attach) from [<c0585950>] (bus_for_each_dev+0x8c/0xd0)
[<c0585950>] (bus_for_each_dev) from [<c058761c>] (driver_attach+0x2c/0x30)
[<c058761c>] (driver_attach) from [<c058704c>] (bus_add_driver+0x16c/0x26c)
[<c058704c>] (bus_add_driver) from [<c0588d60>] (driver_register+0x88/0x104)
[<c0588d60>] (driver_register) from [<bf003668>] (register_virtio_driver+0x38/0x4c [virtio])
[<bf003668>] (register_virtio_driver [virtio]) from [<bf038074>] (init+0x74/0xa4 [virtio_blk])
[<bf038074>] (init [virtio_blk]) from [<c0102108>] (do_one_initcall+0x64/0x1a0)
[<c0102108>] (do_one_initcall) from [<c026dbcc>] (do_init_module+0x74/0x3d0)
[<c026dbcc>] (do_init_module) from [<c01e9a54>] (load_module+0x1f08/0x2570)
[<c01e9a54>] (load_module) from [<c01ea378>] (SyS_finit_module+0xdc/0x110)
[<c01ea378>] (SyS_finit_module) from [<c0109e60>] (ret_fast_syscall+0x0/0x3c)
---[ end trace abde4ea52e9f6bd2 ]---
genirq: Setting trigger mode 1 for irq 51 failed (gic_set_type+0x0/0x78)
virtio_blk: probe of virtio0 failed with error -22
Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
---
README.md | 3 ++-
doc/user_manual.md | 2 ++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 15a2a60..78c0332 100644
--- a/README.md
+++ b/README.md
@@ -42,9 +42,10 @@ Commercial support: info@ilbers.de
Built on:
* Debian 8.2
+* Debian 8.7
Tested on:
-* QEMU 1.1.2+dfsg-6a+deb7u12
+* QEMU 1:2.8+dfsg-3~bpo8+1
* Raspberry Pi 1 Model B rev 2
# Credits
diff --git a/doc/user_manual.md b/doc/user_manual.md
index bbcc007..14657e3 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -70,6 +70,8 @@ Notes:
* BitBake requires Python 3.4+.
* The python3 package is required for the correct `alternatives` setting.
+* QEMU 2.8+ is required to run Stretch images locally in QEMU. This version is available in Stretch and Jessie backports apts.
+* e2fsprogs v1.42- required for building Wheezy images.
### Setup Sudo
--
2.1.4
reply other threads:[~2017-11-03 14:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171103143234.11754-1-asmirnov@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox