On Sun, Jan 05, 2020 at 09:25:42AM +0100, Jürgen Groß wrote:
> On 05.01.20 08:39, Marek Marczykowski-Górecki wrote:
> > On Sun, Jan 05, 2020 at 12:42:30AM +, Andrew Cooper wrote:
> > > On 04/01/2020 15:30, Marek Marczykowski-Górecki wrote:
> > > > Hi,
> > > >
> > > > I have a reliable crash
On 05.01.20 08:39, Marek Marczykowski-Górecki wrote:
On Sun, Jan 05, 2020 at 12:42:30AM +, Andrew Cooper wrote:
On 04/01/2020 15:30, Marek Marczykowski-Górecki wrote:
Hi,
I have a reliable crash on resume from S3. I can reproduce it on both
real hardware and nested within KVM, although
On Sun, Jan 05, 2020 at 12:42:30AM +, Andrew Cooper wrote:
> On 04/01/2020 15:30, Marek Marczykowski-Górecki wrote:
> > Hi,
> >
> > I have a reliable crash on resume from S3. I can reproduce it on both
> > real hardware and nested within KVM, although call traces are different
> > between
On 04/01/2020 15:30, Marek Marczykowski-Górecki wrote:
> Hi,
>
> I have a reliable crash on resume from S3. I can reproduce it on both
> real hardware and nested within KVM, although call traces are different
> between those platforms. In any case, it happens only if some CPU is to
> be
Hi,
I have a reliable crash on resume from S3. I can reproduce it on both
real hardware and nested within KVM, although call traces are different
between those platforms. In any case, it happens only if some CPU is to
be re-offlined after resume (smt=off and/or maxcpus=... options).
I think the
