On 09/22/2014 07:00 AM, Riku Voipio wrote: > Since last week, we have been getting and Ooops when launching kvm on > mustang. This is with kvm-arm git with testing/mustang branch, but I > also reproduced it with 3.17-rc6 (as attached on the log). > > PC is at set_bit+0x14/0x30 > LR is at vgic_v2_sync_lr_elrsr+0x20/0x28 I've been seeing this same crash since rc3 (didn't test rc1,rc2) on my (arm64, 64K page, and gicv2) kernel. I wanted to be sure it wasn't specific to my setup before reporting it. I'm using upstream qemu and the same qemu version and command works fine on a 3.16 kernel. This has to be a kernel regression. > > This is with Qemu from git head, with the following command line: > > qemu-system-aarch64 -smp 2 -m 1024 -cpu host -M virt -kernel > ./Image -append 'root=/dev/vda2 rw rootwait mem=1024M > earlyprintk=pl011,0x9000000 console=ttyAMA0,38400n8' -netdev > user,id=user0 -device virtio-net-device,netdev=user0 -nographic > -enable-kvm > > I tried also with qemu 2.0 frim ubuntu trusty, and was not able to > reproduce it. It must be some recent changes in qemu that trigger the > Oops in kernel. > > > _______________________________________________ > kvmarm mailing list > kvmarm@xxxxxxxxxxxxxxxxxxxxx > https://lists.cs.columbia.edu/mailman/listinfo/kvmarm _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
