From: Joerg Roedel <joro@8bytes.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: Regression on todays tip/master (commit 16f70beccf43)
Date: Thu, 23 Jul 2020 16:52:20 +0200 [thread overview]
Message-ID: <20200723145219.GP27672@8bytes.org> (raw)
In-Reply-To: <871rl2xpar.fsf@nanos.tec.linutronix.de>
On Thu, Jul 23, 2020 at 04:46:04PM +0200, Thomas Gleixner wrote:
> Joerg Roedel <joro@8bytes.org> writes:
> > while testing the SEV-ES patches on todays tip/master I triggered the BUG
> > below:
> >
> > [ 137.629660] ------------[ cut here ]------------
> > [ 137.630769] kernel BUG at kernel/signal.c:1917!
> > [ 137.631796] invalid opcode: 0000 [#1] SMP NOPTI
> > [ 137.632822] CPU: 3 PID: 28596 Comm: test_syscall_vd Not tainted 5.8.0-rc6-tip+ #3
> > [ 137.634495] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
> > [ 137.636236] RIP: 0010:do_notify_parent+0x25c/0x290
> > The guest had 4 VCPUs and ran 4 instances of the in-kernel x86-selftests
> > in a loop, together with 'perf top -e cycles:k'. As you can see in the
> > time-stamps, the issue triggered pretty quickly.
> >
> > Please let me know if you need more information or testing from my side.
>
> Any chance to bisect this?
Yes, will try. I am currently testing plain -rc6, it seems to be fine.
Bisecting is next.
next prev parent reply other threads:[~2020-07-23 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 13:37 Regression on todays tip/master (commit 16f70beccf43) Joerg Roedel
2020-07-23 14:46 ` Thomas Gleixner
2020-07-23 14:52 ` Joerg Roedel [this message]
2020-07-24 13:28 ` Ingo Molnar
2020-07-24 14:50 ` Joerg Roedel
2020-07-24 15:35 ` Joerg Roedel
2020-07-25 10:38 ` Ingo Molnar
2020-07-25 18:56 ` Joerg Roedel
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=20200723145219.GP27672@8bytes.org \
--to=joro@8bytes.org \
--cc=acme@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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