Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: marc.zyngier@arm.com, christoffer.dall@linaro.org
Cc: kvmarm@lists.cs.columbia.edu
Subject: KVM on ARM crashes with new VGIC v4.7-rc7
Date: Thu, 21 Jul 2016 22:57:07 -0700	[thread overview]
Message-ID: <e2f7196ca6c70c55463a45b490f6731a@agner.ch> (raw)

Hi,

I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
this stack trace immediately after invoking qemu-system-arm:

Unable to handle kernel paging request at virtual address ffffffe4
pgd = 8ca52740
[ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
Internal error: Oops: 207 [#1] SMP ARM
Modules linked in:  
CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
4.7.0-rc7-00094-gea3ed2c #109
Hardware name: Freescale i.MX7 Dual (Device Tree)
task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
PC is at do_raw_spin_lock+0x8/0x1dc
LR is at kvm_vgic_flush_hwstate+0x8c/0x224
pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
fec 30be0000.ethernet eth0: MDIO read timeout
r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
Stack: (0x8d2b1e38 to 0x8d2b2000)
1e20:                                                       ffffffe0
00000000
1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
810074f8
1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
8ca5f800
1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
7ffbfeff
1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
ffffe000
1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
8023f248
1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
00000000
1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
00000000
1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
80bc2ec4
1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
007c1e70
1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
00000000
1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
00000036
1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
755feac0
1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
755fec6c
1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
00000000
[<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
(kvm_vgic_flush_hwstate+0x8c/0x224)
[<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
(kvm_arch_vcpu_ioctl_run+0x110/0x478)
[<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
(kvm_vcpu_ioctl+0x2e0/0x6d4)
[<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
(do_vfs_ioctl+0xa0/0x8b8)
[<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
[<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
---[ end trace cb88537fdc8fa206 ]---

I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
-nographic -serial stdio -kernel zImage).

Using a bit older Qemu version 2.4.0.

Is there something missing on my platform or is this a general KVM ARM
issue?

--
Stefan

             reply	other threads:[~2016-07-22  5:55 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22  5:57 Stefan Agner [this message]
2016-07-22  7:47 ` KVM on ARM crashes with new VGIC v4.7-rc7 Marc Zyngier
2016-07-22  7:52   ` Auger Eric
2016-07-22  7:59     ` Marc Zyngier
2016-07-22  8:10   ` Stefan Agner
2016-07-22  9:15 ` Marc Zyngier
2016-07-22 10:42 ` Andre Przywara
2016-07-22 14:35   ` Andrew Jones
2016-07-22 15:40     ` Marc Zyngier
2016-07-22 15:42       ` Auger Eric
2016-07-22 17:38       ` Andrew Jones
2016-07-22 17:47         ` Stefan Agner
2016-07-22 17:49         ` Marc Zyngier
2016-07-22 17:56           ` Stefan Agner
2016-07-22 18:11             ` Marc Zyngier
2016-07-23  7:45               ` Stefan Agner
2016-07-23 10:20                 ` Marc Zyngier
2016-07-23 16:33                   ` Stefan Agner
2016-07-24  9:30                     ` Marc Zyngier
2016-07-25  6:28                       ` Stefan Agner
2016-07-24 12:22             ` Marc Zyngier
2016-07-24 12:36               ` Marc Zyngier
2016-07-25  6:14                 ` Stefan Agner
2016-07-25  8:11                   ` Marc Zyngier
2016-07-25  8:17                     ` Marc Zyngier
2016-07-25 13:50                       ` Andre Przywara
2016-07-25 14:05                         ` Marc Zyngier
2016-07-25 14:28                           ` Andrew Jones
2016-07-25 14:39                             ` Marc Zyngier
2016-07-25 15:07                             ` Marc Zyngier
2016-07-25 15:25                               ` Andre Przywara
2016-07-25 15:29                               ` Andrew Jones
2016-07-25 15:38                                 ` Marc Zyngier
2016-07-25 16:52                     ` Stefan Agner
2016-07-25 17:06                       ` Marc Zyngier
2016-07-25  8:42                   ` Marc Zyngier
2016-07-25  6:36                 ` Stefan Agner
2016-07-25 13:33                   ` Andre Przywara
2016-07-25 16:18                     ` Stefan Agner
2016-07-22 18:06         ` Marc Zyngier
2016-07-22 19:45           ` Andrew Jones
2016-07-22 19:54             ` Marc Zyngier
2016-07-25  9:00               ` Andrew Jones
2016-07-25  9:05                 ` Marc Zyngier
2016-07-25  9:18                   ` Andrew Jones

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=e2f7196ca6c70c55463a45b490f6731a@agner.ch \
    --to=stefan@agner.ch \
    --cc=christoffer.dall@linaro.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=marc.zyngier@arm.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