On Sat, Jul 25, 2020 at 12:38:50PM +0200, Ingo Molnar wrote:
> On a second thought, I think this recent bug might have been the
> culprit:
>
> d136122f5845: ("sched: Fix race against ptrace_freeze_trace()")
>
> Fixed in tip:sched/urgent - this is why it went away in your testing
> perhaps?
I
* Ingo Molnar wrote:
>
> * Joerg Roedel wrote:
>
> > On Thu, Jul 23, 2020 at 04:46:04PM +0200, Thomas Gleixner wrote:
> > > Joerg Roedel writes:
> > > > while testing the SEV-ES patches on todays tip/master I triggered the
> > > > BUG
> > > > below:
> > > >
> > > > [ 137.629660] -
On Fri, Jul 24, 2020 at 04:50:53PM +0200, Joerg Roedel wrote:
> Next thing is, I can reliable reproduce it with yesterdays tip/master
> (commit 16f70beccf43), but did not see it with tip/master pulled today
> (commit c02699cd25e8) yet.
Next bisection try ended with this log:
# bad: [16f70beccf43f
On Fri, Jul 24, 2020 at 03:28:02PM +0200, Ingo Molnar wrote:
> Given that you are perf stress-testing the box, some recent perf
> commit would be the primary suspect - before doing a full bisect you
> might want to try current perf/core (2ac5413e5edc) and its upstream
> base: v5.8-rc3, to narrow
* Joerg Roedel wrote:
> On Thu, Jul 23, 2020 at 04:46:04PM +0200, Thomas Gleixner wrote:
> > Joerg Roedel writes:
> > > while testing the SEV-ES patches on todays tip/master I triggered the BUG
> > > below:
> > >
> > > [ 137.629660] [ cut here ]
> > > [ 137.630769] ke
On Thu, Jul 23, 2020 at 04:46:04PM +0200, Thomas Gleixner wrote:
> Joerg Roedel 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!
> > [
Joerg Roedel 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: [#1] SMP NOPTI
> [ 137.632822] CPU: 3 PID: 2
7 matches
Mail list logo
