similar to: virtio-blk + suspend to disk

On 03/13/2018 01:41 PM, Christian Borntraeger wrote: > Gerd, > > another thing with virtio-gpu. > > I can successfully do suspend/resume (echo disk > /sys/power/state) on my system. As soon as I have a > virtio-gpu the system hangs on reboot/shutdown: > > e.g. > > crash> bt 1 > PID: 1 TASK: 6bef0000 CPU: 4 COMMAND: "systemd" >

On Wed, 2018-07-18 at 10:36 +0200, Lukas Wunner wrote: > On Wed, Jul 18, 2018 at 10:25:05AM +0200, Lukas Wunner wrote: > > The GPU contains an i2c subdevice for each connector with DDC lines. > > I believe those are modelled as children of the GPU's PCI device as > > they're accessed via mmio of the PCI device. > > > > The problem here is that when the

On Wed, Jul 18, 2018 at 10:25:05AM +0200, Lukas Wunner wrote: > The GPU contains an i2c subdevice for each connector with DDC lines. > I believe those are modelled as children of the GPU's PCI device as > they're accessed via mmio of the PCI device. > > The problem here is that when the GPU's PCI device runtime suspends, > its i2c child device needs to be runtime

On Wed, Jul 18, 2018 at 09:38:41AM +0200, Rafael J. Wysocki wrote: > On Tue, Jul 17, 2018 at 8:20 PM, Lukas Wunner <lukas at wunner.de> wrote: > > Okay, the PCI device is suspending and the nvkm_i2c_aux_acquire() > > wants it in resumed state, so is waiting forever for the device to > > runtime suspend in order to resume it again immediately afterwards. > > >

Hi all, I've installed CentOS 5.2 i386 (with all updates) on notebook Fujutsu Siemens Esprimo U9200 Suspending works normal, but after resuming my system crashes. There are no messages about that in /var/log/messages, only after reboot system I see in gnome: " Resume Problem Your system did not appear to resume correctly from Suspend/Hibernate. This may be a driver problem or a

On Tue, Jun 11, 2013 at 11:22:37AM +0300, Gleb Natapov wrote: > On Tue, Jun 11, 2013 at 11:19:46AM +0300, Michael S. Tsirkin wrote: > > On Tue, Jun 11, 2013 at 11:03:50AM +0300, Gleb Natapov wrote: > > > On Tue, Jun 11, 2013 at 11:02:26AM +0300, Michael S. Tsirkin wrote: > > > > On Tue, Jun 11, 2013 at 10:53:48AM +0300, Gleb Natapov wrote: > > > > > On

This patch series makes suspend support in qemu alot more useful. Right now the guest can put itself into s3, but qemu will wakeup the guest instantly. With this patch series applied the guest will stay suspended instead and there are a few events which can kick the guest out of suspend state: A monitor command, ps/2 input, serial input, rtc. Not much yet, but it''s a start with the

On Tue, Jun 11, 2013 at 11:03:50AM +0300, Gleb Natapov wrote: > On Tue, Jun 11, 2013 at 11:02:26AM +0300, Michael S. Tsirkin wrote: > > On Tue, Jun 11, 2013 at 10:53:48AM +0300, Gleb Natapov wrote: > > > On Tue, Jun 11, 2013 at 10:10:47AM +0300, Michael S. Tsirkin wrote: > > > > On Thu, Jun 06, 2013 at 10:02:14AM -0500, Anthony Liguori wrote: > > > > >

On Tue, Jun 11, 2013 at 11:19:46AM +0300, Michael S. Tsirkin wrote: > On Tue, Jun 11, 2013 at 11:03:50AM +0300, Gleb Natapov wrote: > > On Tue, Jun 11, 2013 at 11:02:26AM +0300, Michael S. Tsirkin wrote: > > > On Tue, Jun 11, 2013 at 10:53:48AM +0300, Gleb Natapov wrote: > > > > On Tue, Jun 11, 2013 at 10:10:47AM +0300, Michael S. Tsirkin wrote: > > > >

On Tue, Jun 11, 2013 at 11:19:46AM +0300, Michael S. Tsirkin wrote: > On Tue, Jun 11, 2013 at 11:03:50AM +0300, Gleb Natapov wrote: > > On Tue, Jun 11, 2013 at 11:02:26AM +0300, Michael S. Tsirkin wrote: > > > On Tue, Jun 11, 2013 at 10:53:48AM +0300, Gleb Natapov wrote: > > > > On Tue, Jun 11, 2013 at 10:10:47AM +0300, Michael S. Tsirkin wrote: > > > >

On 2018/10/15 ??6:08, ake wrote: > > On 2018?10?12? 18:18, ake wrote: >> >> On 2018?10?12? 17:23, Jason Wang wrote: >>> >>> On 2018?10?12? 12:30, ake wrote: >>>> On 2018?10?11? 22:06, Jason Wang wrote: >>>>> On 2018?10?11? 18:22, ake wrote: >>>>>> On 2018?10?11? 18:44, Jason Wang wrote: >>>>>>> On

On Tue, Jun 11, 2013 at 11:02:26AM +0300, Michael S. Tsirkin wrote: > On Tue, Jun 11, 2013 at 10:53:48AM +0300, Gleb Natapov wrote: > > On Tue, Jun 11, 2013 at 10:10:47AM +0300, Michael S. Tsirkin wrote: > > > On Thu, Jun 06, 2013 at 10:02:14AM -0500, Anthony Liguori wrote: > > > > Gleb Natapov <gleb at redhat.com> writes: > > > > > > >

On Tue, Jun 11, 2013 at 11:02:26AM +0300, Michael S. Tsirkin wrote: > On Tue, Jun 11, 2013 at 10:53:48AM +0300, Gleb Natapov wrote: > > On Tue, Jun 11, 2013 at 10:10:47AM +0300, Michael S. Tsirkin wrote: > > > On Thu, Jun 06, 2013 at 10:02:14AM -0500, Anthony Liguori wrote: > > > > Gleb Natapov <gleb at redhat.com> writes: > > > > > > >

On Tue, Jul 17, 2018 at 8:20 PM, Lukas Wunner <lukas at wunner.de> wrote: > On Tue, Jul 17, 2018 at 12:53:11PM -0400, Lyude Paul wrote: >> On Tue, 2018-07-17 at 09:16 +0200, Lukas Wunner wrote: >> > On Mon, Jul 16, 2018 at 07:59:25PM -0400, Lyude Paul wrote: >> > > In order to fix all of the spots that need to have runtime PM get/puts() >> > > added,

On 06/06/13 08:34, Gleb Natapov wrote: > On Wed, Jun 05, 2013 at 07:41:17PM -0500, Anthony Liguori wrote: >> >> Oh, you mean in real mode. >> >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. >> There are loads of ASSERT32FLAT()s in the code to make sure of this. >> > Well, not exactly. Initialization is done in 32bit, but disk >

On 06/06/13 08:34, Gleb Natapov wrote: > On Wed, Jun 05, 2013 at 07:41:17PM -0500, Anthony Liguori wrote: >> >> Oh, you mean in real mode. >> >> SeaBIOS runs the virtio code in 32-bit mode with a flat memory layout. >> There are loads of ASSERT32FLAT()s in the code to make sure of this. >> > Well, not exactly. Initialization is done in 32bit, but disk >

Hey, Sorry for dropping in like this, couldn't find any information on this and I guess I'm too lazy to read all the relevant bits and pieces of the kernel sources to find out: I'm currently running encrypted root and swap, but would still like to use suspend to disk. Would early userspace be capable of inserting the crypto-loop module into the kernel, load the keys off my

On Tue, 2018-07-17 at 20:20 +0200, Lukas Wunner wrote: > On Tue, Jul 17, 2018 at 12:53:11PM -0400, Lyude Paul wrote: > > On Tue, 2018-07-17 at 09:16 +0200, Lukas Wunner wrote: > > > On Mon, Jul 16, 2018 at 07:59:25PM -0400, Lyude Paul wrote: > > > > In order to fix all of the spots that need to have runtime PM get/puts() > > > > added, we need to ensure

On Tue, Jun 11, 2013 at 10:53:48AM +0300, Gleb Natapov wrote: > On Tue, Jun 11, 2013 at 10:10:47AM +0300, Michael S. Tsirkin wrote: > > On Thu, Jun 06, 2013 at 10:02:14AM -0500, Anthony Liguori wrote: > > > Gleb Natapov <gleb at redhat.com> writes: > > > > > > > On Wed, Jun 05, 2013 at 07:41:17PM -0500, Anthony Liguori wrote: > > > >>

Let host know of our state (partial yet) so that the host PCI device is up to where we were when we were suspended. This is still an RFC as this doesn't completely work: an unused device at the time of suspend will work fine after resume, but a device that has seen some activity doesn't behave well after resume. Especially, host->guest communication doesn't go through. This could