On Sunday 06 September 2015 11:44:11, Stefan Fritsch wrote:
> the diff below is necessary to make suspend/resume work when x2apic
> is enabled (i.e. on qemu/kvm/...). While I don't expect problems,
> it would be nice if I could get some reports that this doesn't
> break suspend/resume on real machi
> (dmesg attached anyway).
Eh, or not? But now.
OpenBSD 5.8-current (GENERIC.MP) #2: Mon Sep 7 03:09:58 CEST 2015
fstd@flap.localdomain:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3472392192 (3311MB)
avail mem = 3363315712 (3207MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
main
> get some reports that this doesn't break suspend/resume on real machines,
> especially older ones (like core 2 duo and older) and ones with an amd cpu.
Suspend (and more importantly, resume) still works on my 2011-ish amd64 laptop
with your patch (dmesg attached anyway).
Cheers
--
Timo Buhrmes
On Monday 07 September 2015 13:23:03, Alexander Bluhm wrote:
> Suspend OpenBSD in a fully emulated qemu running on OpenBSD works.
> After resume, typing in the shell of the virtualized machine works.
> But at disk access, all processes hang in biowait.
>
> It is the same behavior with and without
On Sun, Sep 06, 2015 at 11:44:11AM +0200, Stefan Fritsch wrote:
> Hi,
>
> the diff below is necessary to make suspend/resume work when x2apic is
> enabled (i.e. on qemu/kvm/...). While I don't expect problems, it would be
> nice if I could get some reports that this doesn't break suspend/resume o
On Sun, Sep 06, 2015 at 11:44:11AM +0200, Stefan Fritsch wrote:
> the diff below is necessary to make suspend/resume work when x2apic is
> enabled (i.e. on qemu/kvm/...). While I don't expect problems, it would be
> nice if I could get some reports that this doesn't break suspend/resume on
> real
Stefan Fritsch (2015-09-06 11:44 +0200):
> the diff below is necessary to make suspend/resume work when x2apic is
> enabled (i.e. on qemu/kvm/...). While I don't expect problems, it would be
> nice if I could get some reports that this doesn't break suspend/resume on
> real machines, especially o
On Sun, Sep 06, 2015 at 11:44:11AM +0200, Stefan Fritsch wrote:
> Hi,
>
> the diff below is necessary to make suspend/resume work when x2apic is
> enabled (i.e. on qemu/kvm/...). While I don't expect problems, it would be
> nice if I could get some reports that this doesn't break suspend/resume o
Hi,
the diff below is necessary to make suspend/resume work when x2apic is
enabled (i.e. on qemu/kvm/...). While I don't expect problems, it would be
nice if I could get some reports that this doesn't break suspend/resume on
real machines, especially older ones (like core 2 duo and older) and on