From: Vitaly Chikunov <1913315@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1913315] [NEW] qemu-system-x86_64 crash: in memory_region_access_valid+0x13
Date: Tue, 26 Jan 2021 15:29:33 -0000 [thread overview]
Message-ID: <161167497358.4863.17291791719671024899.malonedeb@soybean.canonical.com> (raw)
Public bug reported:
Recently we started to get intermittent qemu crashes. There is catchsegv
report:
```
+ qemu-system-x86_64 -m 77766M -smp 8 -nodefaults -nographic -no-reboot -fsdev local,id=root,path=/,security_model=none,multidevs=remap -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root -device virtio-rng-pci -serial mon:stdio -kernel /usr/src/tmp/kernel-image-rt-buildroot/boot/vmlinuz-4.19.165-rt-alt1.rt70 -initrd /usr/src/tmp/initramfs-4.19.165-rt-alt1.rt70.img -bios bios.bin -append 'console=ttyS0 mitigations=off nokaslr quiet panic=-1 no_timer_check'
*** signal 11
Register dump:
RAX: 0000000000000000 RBX: 0000034000000340 RCX: 0000000000000001
RDX: 0000000000000004 RSI: 0000000000000300 RDI: 0000034000000340
RBP: 0000000000000300 R8 : 0000000000000000 R9 : 0000034000000340
R10: 0000000000000370 R11: 0000000000000002 R12: 0000000000000004
R13: 0000000000000004 R14: 000055b473fef5e0 R15: 0000000000000002
RSP: 00007fd7edffae90
RIP: 000055b4717ef653 EFLAGS: 00010206
CS: 0033 FS: 0000 GS: 0000
Trap: 0000000e Error: 00000004 OldMask: 7ffbfa77 CR2: 00000388
FPUCW: 0000037f FPUSW: 00000000 TAG: 00000000
RIP: 00000000 RDP: 00000000
ST(0) 0000 0000000000000000 ST(1) 0000 0000000000000000
ST(2) 0000 0000000000000000 ST(3) 0000 0000000000000000
ST(4) 0000 0000000000000000 ST(5) 0000 0000000000000000
ST(6) 0000 0000000000000000 ST(7) 0000 0000000000000000
mxcsr: 1fa0
XMM0: 00000000000000000000000000000000 XMM1: 00000000000000000000000000000000
XMM2: 00000000000000000000000000000000 XMM3: 00000000000000000000000000000000
XMM4: 00000000000000000000000000000000 XMM5: 00000000000000000000000000000000
XMM6: 00000000000000000000000000000000 XMM7: 00000000000000000000000000000000
XMM8: 00000000000000000000000000000000 XMM9: 00000000000000000000000000000000
XMM10: 00000000000000000000000000000000 XMM11: 00000000000000000000000000000000
XMM12: 00000000000000000000000000000000 XMM13: 00000000000000000000000000000000
XMM14: 00000000000000000000000000000000 XMM15: 00000000000000000000000000000000
Backtrace:
qemu-system-x86_64(memory_region_access_valid+0x13)[0x55b4717ef653]
qemu-system-x86_64(memory_region_dispatch_write+0x48)[0x55b4717ef8c8]
qemu-system-x86_64(+0x69fdfc)[0x55b471851dfc]
qemu-system-x86_64(helper_le_stl_mmu+0x2c5)[0x55b471858995]
[0x7feaed070925]
```
QEMU release 5.2.0.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1913315
Title:
qemu-system-x86_64 crash: in memory_region_access_valid+0x13
Status in QEMU:
New
Bug description:
Recently we started to get intermittent qemu crashes. There is
catchsegv report:
```
+ qemu-system-x86_64 -m 77766M -smp 8 -nodefaults -nographic -no-reboot -fsdev local,id=root,path=/,security_model=none,multidevs=remap -device virtio-9p-pci,fsdev=root,mount_tag=/dev/root -device virtio-rng-pci -serial mon:stdio -kernel /usr/src/tmp/kernel-image-rt-buildroot/boot/vmlinuz-4.19.165-rt-alt1.rt70 -initrd /usr/src/tmp/initramfs-4.19.165-rt-alt1.rt70.img -bios bios.bin -append 'console=ttyS0 mitigations=off nokaslr quiet panic=-1 no_timer_check'
*** signal 11
Register dump:
RAX: 0000000000000000 RBX: 0000034000000340 RCX: 0000000000000001
RDX: 0000000000000004 RSI: 0000000000000300 RDI: 0000034000000340
RBP: 0000000000000300 R8 : 0000000000000000 R9 : 0000034000000340
R10: 0000000000000370 R11: 0000000000000002 R12: 0000000000000004
R13: 0000000000000004 R14: 000055b473fef5e0 R15: 0000000000000002
RSP: 00007fd7edffae90
RIP: 000055b4717ef653 EFLAGS: 00010206
CS: 0033 FS: 0000 GS: 0000
Trap: 0000000e Error: 00000004 OldMask: 7ffbfa77 CR2: 00000388
FPUCW: 0000037f FPUSW: 00000000 TAG: 00000000
RIP: 00000000 RDP: 00000000
ST(0) 0000 0000000000000000 ST(1) 0000 0000000000000000
ST(2) 0000 0000000000000000 ST(3) 0000 0000000000000000
ST(4) 0000 0000000000000000 ST(5) 0000 0000000000000000
ST(6) 0000 0000000000000000 ST(7) 0000 0000000000000000
mxcsr: 1fa0
XMM0: 00000000000000000000000000000000 XMM1: 00000000000000000000000000000000
XMM2: 00000000000000000000000000000000 XMM3: 00000000000000000000000000000000
XMM4: 00000000000000000000000000000000 XMM5: 00000000000000000000000000000000
XMM6: 00000000000000000000000000000000 XMM7: 00000000000000000000000000000000
XMM8: 00000000000000000000000000000000 XMM9: 00000000000000000000000000000000
XMM10: 00000000000000000000000000000000 XMM11: 00000000000000000000000000000000
XMM12: 00000000000000000000000000000000 XMM13: 00000000000000000000000000000000
XMM14: 00000000000000000000000000000000 XMM15: 00000000000000000000000000000000
Backtrace:
qemu-system-x86_64(memory_region_access_valid+0x13)[0x55b4717ef653]
qemu-system-x86_64(memory_region_dispatch_write+0x48)[0x55b4717ef8c8]
qemu-system-x86_64(+0x69fdfc)[0x55b471851dfc]
qemu-system-x86_64(helper_le_stl_mmu+0x2c5)[0x55b471858995]
[0x7feaed070925]
```
QEMU release 5.2.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1913315/+subscriptions
next reply other threads:[~2021-01-26 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 15:29 Vitaly Chikunov [this message]
2021-05-12 18:09 ` [Bug 1913315] Re: qemu-system-x86_64 crash: in memory_region_access_valid+0x13 Thomas Huth
2021-07-12 4:18 ` Launchpad Bug Tracker
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=161167497358.4863.17291791719671024899.malonedeb@soybean.canonical.com \
--to=1913315@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 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).