From: Thomas Gleixner <tglx@linutronix.de>
To: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
Cc: kvm@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-mm@kvack.org, platform-driver-x86@vger.kernel.org,
x86@kernel.org, iommu@lists.linux-foundation.org,
"Guilherme G. Piccoli" <kernel@gpiccoli.net>,
gavin.guo@canonical.com, halves@canonical.com,
ioanna-maria.alifieraki@canonical.com,
jay.vosburgh@canonical.com, mfo@canonical.com
Subject: Re: Advice on oops - memory trap on non-memory access instruction (invalid CR2?)
Date: Mon, 14 Oct 2019 16:10:15 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1910141602270.2531@nanos.tec.linutronix.de> (raw)
In-Reply-To: <66eeae28-bfd3-c7a0-011c-801981b74243@canonical.com>
On Mon, 14 Oct 2019, Guilherme G. Piccoli wrote:
> Modules linked in: <...>
> CPU: 40 PID: 78274 Comm: qemu-system-x86 Tainted: P W OE
Tainted: P - Proprietary module loaded ...
Try again without that module
Tainted: W - Warning issued before
Are you sure that that warning is harmless and unrelated?
> 4.4.0-45-generic #66~14.04.1-Ubuntu
Does the same problem happen with a not so dead kernel? CR2 handling got
quite some updates/fixes since then.
Thanks,
tglx
next prev parent reply other threads:[~2019-10-14 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 3:32 Guilherme G. Piccoli
2019-10-14 14:10 ` Thomas Gleixner [this message]
2019-10-15 15:21 ` Guilherme G. Piccoli
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=alpine.DEB.2.21.1910141602270.2531@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=gavin.guo@canonical.com \
--cc=gpiccoli@canonical.com \
--cc=halves@canonical.com \
--cc=ioanna-maria.alifieraki@canonical.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jay.vosburgh@canonical.com \
--cc=kernel@gpiccoli.net \
--cc=kvm@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mfo@canonical.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=x86@kernel.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