All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1795148] Re: address_space_stw_le_cached: Assertion `addr < cache->len && 2 <= cache ->len - addr' failed
Date: Mon, 15 Oct 2018 09:39:18 -0000	[thread overview]
Message-ID: <153959635885.15830.14259272628561611229.malone@gac.canonical.com> (raw)
In-Reply-To: 153823442833.30132.5797682134380809612.malonedeb@soybean.canonical.com

I suspect this is a known bug, fixed in master in commit db812c4073c77.
You could test that by cherry-picking it to 3.0 or just testing against
master.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1795148

Title:
  address_space_stw_le_cached: Assertion `addr < cache->len && 2 <=
  cache ->len - addr' failed

Status in QEMU:
  New

Bug description:
  When running OpenBSD-current as a guest, the following assertion is
  hit after a few seconds, resulting in the virtual machine to crash:

  ```
  qemu-system-x86_64: /build/qemu/src/qemu-3.0.0/include/exec/memory_ldst_cached.inc.h:85: address_space_stw_le_cached: Assertion `addr < cache->len && 2 <= cache->len - addr' failed.
  ```

  Host is Arch Linux stable, running on x86_64.

  Qemu version is 3.0.0, installed via the standard Arch Linux package.

  Version 2.12.1 didn't exhibit this behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1795148/+subscriptions

  parent reply	other threads:[~2018-10-15  9:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <153823442833.30132.5797682134380809612.malonedeb@soybean.canonical.com>
2018-10-15  6:46 ` [Qemu-devel] [Bug 1795148] Re: address_space_stw_le_cached: Assertion `addr < cache->len && 2 <= cache ->len - addr' failed Thomas Huth
2018-10-15  9:39 ` Peter Maydell [this message]
2019-01-18 17:20 ` Peter Maydell

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=153959635885.15830.14259272628561611229.malone@gac.canonical.com \
    --to=peter.maydell@linaro.org \
    --cc=1795148@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.