linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM64 KVM crash
Date: Sat, 13 Oct 2018 10:22:17 +0100	[thread overview]
Message-ID: <86h8hqtd4m.wl-marc.zyngier@arm.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1810121453380.14664@file01.intranet.prod.int.rdu2.redhat.com>

On Fri, 12 Oct 2018 19:59:16 +0100,
Mikulas Patocka <mpatocka@redhat.com> wrote:
> 
> 
> 
> On Fri, 12 Oct 2018, Marc Zyngier wrote:
> 
> > Right. But how is that related to KVM? See below:
> > 
> > > [75476.680725]  find_next_and_bit+0xc/0x70
> > > [75476.680728]  find_busiest_group+0x128/0x938
> > > [75476.680730]  load_balance+0x148/0x848
> > > [75476.680732]  pick_next_task_fair+0x1d4/0x568
> > > [75476.680734]  __schedule+0xe8/0x4b0
> > > [75476.680736]  schedule+0x38/0xa0
> > > [75476.680739]  kvm_vcpu_block+0x88/0x180
> > > [75476.680742]  kvm_handle_wfx+0x80/0xb8
> > > [75476.680744]  handle_exit+0x138/0x1b8
> > 
> > The guest is exiting because it has executed a blocking WFI, so KVM's
> > job is done and we're calling schedule(). The scheduler then starts
> > doing its job of picking the next victim.
> > 
> > At this stage, the kernel indeed blows up. But this doesn't immediately
> > seem to be KVM's fault. It is far more likely that the scheduler has
> > messed something up in its own data structure, which is even worse :-(.
> > 
> > I'd suggest you get in touch with the scheduler guys to see if they have
> > any insight. Also, trying to come up with a reproducer would be
> > extremely useful.
> > 
> > Thanks,
> > 
> > 	M.
> 
> I use this machine most of the time without KVM - and it crashed when I 
> started KVM - so I assume that KVM had something to do with it. Perhaps it 
> corrupts random memory? I may try to run some KVM stress for many days to 
> test if I reproduce it.

One thing I know for sure is that if you use a tap (such as macvtap)
to give networking to your VMs, the Ethernet driver on the 8040 (such
as on your MacchiatoBin) will happily corrupt memory (you can witness
that without running KVM at all). Something to do with the sbk being
freed early.

I've reported this issue several times, only to hear the wind
blowing. At this stage, I've shelved it. There is enough decent and
maintained platforms around not to worry about the unmaintained stuff.

Now, if you can give me a reproducer, I'll happily investigate.

Thanks,

	M.

-- 
Jazz is not dead, it just smell funny.

  reply	other threads:[~2018-10-13  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12 16:20 ARM64 KVM crash Mikulas Patocka
2018-10-12 16:51 ` Marc Zyngier
2018-10-12 18:59   ` Mikulas Patocka
2018-10-13  9:22     ` Marc Zyngier [this message]
2018-10-24 21:40       ` Mikulas Patocka

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=86h8hqtd4m.wl-marc.zyngier@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).