Re: Kernel 5.3.x, 5.2.2+: VMware player suspend on 64/32 bit guests

2019-08-30 Thread Woody Suwalski
On Wed, Aug 28, 2019 at 10:50 AM Thomas Gleixner wrote: > > Woody, > > On Wed, 28 Aug 2019, Woody Suwalski wrote: > > > I have tried to "bisect" the config changes, and builds working/not > > working between > > rc3-rc4-rc5, and come out with the same frustrating result, that > > building a

Re: Kernel 5.3.x, 5.2.2+: VMware player suspend on 64/32 bit guests

2019-08-28 Thread Thomas Gleixner
Woody, On Wed, 28 Aug 2019, Woody Suwalski wrote: > I have tried to "bisect" the config changes, and builds working/not > working between > rc3-rc4-rc5, and come out with the same frustrating result, that > building a "clean" kernel is not producing the same behavoir as > incremental building

Re: Kernel 5.3.x, 5.2.2+: VMware player suspend on 64/32 bit guests

2019-08-28 Thread Woody Suwalski
I have tried to "bisect" the config changes, and builds working/not working between rc3-rc4-rc5, and come out with the same frustrating result, that building a "clean" kernel is not producing the same behavoir as incremental building while bisecting. For some reason even after getting to the same

Re: Kernel 5.3.x, 5.2.2+: VMware player suspend on 64/32 bit guests

2019-08-21 Thread Thomas Gleixner
On Tue, 20 Aug 2019, Woody Suwalski wrote: > On Thu, Aug 15, 2019 at 2:37 AM Thomas Gleixner wrote: > > On Tue, 13 Aug 2019, Woody Suwalski wrote: > > > On Mon, Aug 12, 2019 at 1:24 PM Thomas Gleixner > > > wrote: > > > > The ACPI handler is not the culprit. This is either an emulation bug or >

Re: Kernel 5.3.x, 5.2.2+: VMware player suspend on 64/32 bit guests

2019-08-20 Thread Woody Suwalski
On Thu, Aug 15, 2019 at 2:37 AM Thomas Gleixner wrote: > > Woody, > > On Tue, 13 Aug 2019, Woody Suwalski wrote: > > On Mon, Aug 12, 2019 at 1:24 PM Thomas Gleixner wrote: > > > The ACPI handler is not the culprit. This is either an emulation bug or > > > something really strange. Can you please

Re: Kernel 5.3.x, 5.2.2+: VMware player suspend on 64/32 bit guests

2019-08-15 Thread Thomas Gleixner
Woody, On Tue, 13 Aug 2019, Woody Suwalski wrote: > On Mon, Aug 12, 2019 at 1:24 PM Thomas Gleixner wrote: > > The ACPI handler is not the culprit. This is either an emulation bug or > > something really strange. Can you please use a WARN_ON() if the loop is > > exited via the timeout so we can

Re: Kernel 5.3.x, 5.2.2+: VMware player suspend on 64/32 bit guests

2019-08-13 Thread Woody Suwalski
On Mon, Aug 12, 2019 at 1:24 PM Thomas Gleixner wrote: > On Mon, 12 Aug 2019, Woody Suwalski wrote: > > > I have added a timeout counter in __synchronize_hardirq(). > > At the bottom I have converted while(inprogress); to while(inprogress > > && timeout++ < 100); > > > > That is bypassing the

Re: Kernel 5.3.x, 5.2.2+: VMware player suspend on 64/32 bit guests

2019-08-12 Thread Thomas Gleixner
A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top Woody, On Mon, 12

Re: Kernel 5.3.x, 5.2.2+: VMware player suspend on 64/32 bit guests

2019-08-12 Thread Woody Suwalski
Thomas, Rafael, I have added a timeout counter in __synchronize_hardirq(). At the bottom I have converted while(inprogress); to while(inprogress && timeout++ < 100); That is bypassing the suspend lockup problem. On both 32-bit and 64-bit VMs the countdown is triggered by sync of irq9. Which

Kernel 5.3.x, 5.2.2+: VMware player suspend on 64/32 bit guests

2019-08-10 Thread Woody Suwalski
Moving the thread to LKML, as suggested by Thomas... -- Forwarded message - From: Woody Suwalski Date: Thu, Aug 1, 2019 at 3:45 PM Subject: Intermittent suspend on 5.3 / 5.2 To: Rafael J. Wysocki Hi RafaƂ, I know that you are investigating some issues between these 2