On Fri, Jan 13, 2023 at 03:20:37PM +0100, Juergen Gross wrote:
> On 13.01.23 14:44, Marek Marczykowski-Górecki wrote:
> > But, unrelated to this bug, it did get message like in
> > https://www.mail-archive.com/xen-devel@lists.xenproject.org/msg107609.html
> > (WARNING: CPU: 1 PID: 0 at
On 13.01.23 14:44, Marek Marczykowski-Górecki wrote:
But, unrelated to this bug, it did get message like in
https://www.mail-archive.com/xen-devel@lists.xenproject.org/msg107609.html
(WARNING: CPU: 1 PID: 0 at arch/x86/mm/tlb.c:523 switch_mm_irqs_off+0x230/0x4a0)
Hmm, is applying the
On Fri, Jan 13, 2023 at 09:08:35AM +0100, Juergen Gross wrote:
> On 13.01.23 03:57, Marek Marczykowski-Górecki wrote:
> > Hi,
> >
> > 6.1.3 as PV dom0 crashes when attempting to suspend. 6.1.1 works. The
> > crash:
> >
> > [ 348.284004] PM: suspend entry (deep)
> > [ 348.289532]
On 13.01.23 03:57, Marek Marczykowski-Górecki wrote:
Hi,
6.1.3 as PV dom0 crashes when attempting to suspend. 6.1.1 works. The
crash:
[ 348.284004] PM: suspend entry (deep)
[ 348.289532] Filesystems sync: 0.005 seconds
[ 348.291545] Freezing user space processes ... (elapsed
Hi,
6.1.3 as PV dom0 crashes when attempting to suspend. 6.1.1 works. The
crash:
[ 348.284004] PM: suspend entry (deep)
[ 348.289532] Filesystems sync: 0.005 seconds
[ 348.291545] Freezing user space processes ... (elapsed 0.000 seconds)
done.
[ 348.292457] OOM killer