search for: resume

git mv resume.c resumelib.c and the addition of a minimal resume.c, which calls resume() from resumelib produces a small standalone resume. happy to hear feedback on the needed kinit/Kbuild changes. resulting resume bin is small: ls -l /usr/lib/klibc/bin/resume -rwxr-xr-x 1 root root 2904 2006-07-11 02:11 /usr/...

...(username = '%u' AND domain = '') \ ) \ AND IF('pop3' = '%s', allow_pop3, true) = true \ AND IF('imap' = '%s', allow_imap, true) = true \ AND active = true \ LIMIT 1 $ strace -f dovecot -F [pid 6771] <... epoll_wait resumed> {{EPOLLIN, {u32=6613264, u64=6613264}}}, 6, 180000) = 1 [pid 6771] gettimeofday({1235491268, 481726}, {0, 0}) = 0 [pid 6771] read(10, "PASS Yast7310\r\n"..., 4075) = 15 [pid 6771] gettimeofday({1235491268, 482089}, NULL) = 0 [pid 6771] write(11, "AUTH\t1\tPLAIN\tservice=pop3...

I have the following models: class Resume belongs_to :resume_assignments end class User belongs_to :resume_assignments end class ResumeAssignment has_one :resume has_one :user end When I delete a resume, I want to make sure that its associated ResumeAssignment gets deleted also. Calling destroy_all to delete some resumes doesn&...

https://bugzilla.samba.org/show_bug.cgi?id=9813 Summary: --resume parameter to improve speed of dropped/partial transfers Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo:...

...ut branches, RAUW-ing > coro.suspend with an appropriate constant takes care of it all. > > Here is an updated version. > 1) coro.fork is gone, gone gone!!!! > 2) coro.suspend is changed as follows: > > declare i8 coro.suspend([...]) > > returns: > 0 - in resume clone > 1 - in destroy clone > -1 - in the original function > > Usage: > > [...] > %0 = call i8 @llvm.coro.suspend([...]) > switch i8 %0, label %return [ i32 0, label %resume, > i32 1, label %cleanup] > > Lo...

...port a\nspecialied printer like a Dymo l"..., 262144 <unfinished ...> [pid 9977] SYS_write(3, "se a serial interface.\n\n\nThe one thing I'm not sure about is whether or not they will support a\nspecialied printer like a Dymo l"..., 262144) = -5 [pid 9977] <... write resumed> ) = -1 [pid 9977] __errno_location() = 0x40030b00 [pid 9977] __errno_location() = 0x40030b00 [pid 9977] strerror(5)...

...t.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=a2f9cd4abe2d5cb72e1e89089b132e866e3cea81 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Thu, 19 Jul 2018 20:09:28 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sun, 20 Jan 2019 00:22:24 +0000 [klibc] resume: Write resume_offset attribute Support for a device offset as part of the string written to /sys/power/resume never got into a mainline kernel. However, since Linux 4.17 there is a separate resume_offset attribute that we can use to set the offset before attempting to resume. Change resume() to...

Hi, I'm toying with the SMP/i386 ACPI suspend/resume patches in -9. Thanks so much for this! I've noticed though that the video backlight stays off after resume. A common problem on -9, so I set hw.acpi.reset_video=1. That restores the backlight. However, the video mode isn't restored. I have my console set to VGA_80x60 and the resume seems...

The previous API for setting resume offset didn't actually work in the kernel. It silently ignored this part of the string. A new API was introduced under /sys/power/resume_offset specifically for setting this value. https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=648464076160ee7a...

...ees... >> nouveau [ DRM] resuming display... >> nouveau 0000:02:00.0: no hotplug settings from platform >> nouveau 0000:02:00.0: no hotplug settings from platform >> >> Logs(dmesg) are literally identical. >> >> 3.15.10-201.fc20.x86_64 - nouveau(fb) resume & thaw PASSED, and that's all what works. >> Kernels >= 3.16 - nouveau(fb) resume & thaw BROKEN >> ALL Kernels - vesa(fb) resume & thaw BROKEN. >> >> > > Excusez-moi, > BROKEN == The display remains OFF. > More precis...

Hello, I am using domain event notifications from libvirt-event API in my application and it seems to work fine, except for 'suspend' and 'resume' events where I keep receiving duplicated notifications. Similarly, the example provided with libvirt (in examples/object-events/event-test) also produces twice as much notifications for 'suspend' and 'resume' than for other events. Here is the sequence of virsh commands and th...

Hi, I am using libvirt with qemu/kvm with qemu-guest-agent and suspend/save/resume linux and windows vm's. Time in Windows gets handled fine with ntp but I can get neither ntp or chrony to sync after resume without manually setting the time close to correct first. Searching has gotten me to the point where I can manually set the time using qemu-guest-agent but I cant figure...

[Patch 4/4]: Xend interface for HVM S3 - extend "xm resume <domid>" to be able to S3 resume HVM domain. - when user issue "xm resume" command for HVM domain, xend will use xc lib API to call HVMOP_s3_resume hypercall. Note: it may not appropriate use xm resume for HVM s3, since xm resume is originally designed for save/rest...

On 38+ Intel-based Asus products, the nvidia GPU becomes unusable after S3 suspend/resume. The affected products include multiple generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs many errors such as: fifo: fault 00 [READ] at 0000005555555000 engine 00 [GR] client 04 [HUB/FE] reason 4a [] on channel -1 [007fa91000 unknown] DRM: failed to idle chann...

Hi, FreeBSD-9 works fine on this Lenovo T400 - except that suspending with no USB devices plugged in result in no ports working after resume. If I have a device plugged in during suspend - on any port - then all the ports work fine after resume. I've attached usbconfig and acpidump output. here's what is logged in the kernel buffer during suspend and resume: Her'es the suspend: Jun 20 14:03:34 lucy acpi: suspend at 201...

...I'd appreciate a link to an explanation, but I understand it is out of scope for this list. The HW clock is correct and the guest agent is setup to use kvm-clock. Using the guest-set-time command does set the clock on the guest according to the host. But this is not triggered automatically on resume. I found discussions about this, even a patch proposal to call guest-set-time on resume, but all of this is one year old and I can't find any newer information. http://serverfault.com/questions/334698/how-to-keep-time-on-resumed-kvm-guest-with-libvirt https://www.redhat.com/archives/libvirt-u...

...Gor Nishanov <gornishanov at gmail.com> wrote: > Hi Eli: > > >> Naively, you would expect that it would be legal to hoist the store... > >> but that breaks your coroutine semantics because the global could be > mutated > >> between the first return and the resume. > > Hmmm... I don't see the problem. I think hoisting the store is perfectly > legal > transformation with all semantics preserved. > > Let's look at your example: > > >> block1: > >> suspend > >> switch (resume, destroy, return) > &gt...

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. > > > > The deadlock in the stack trace you've posted could be resolved using > > the technique I used in d61a5c106351 by adding the following to >...

On 09/29/2014 02:28 AM, Martin Kletzander wrote: > On Fri, Sep 26, 2014 at 08:16:25AM +0800, Bill Kenworthy wrote: >> Hi, >> I am using libvirt with qemu/kvm with qemu-guest-agent and >> suspend/save/resume linux and windows vm's. Time in Windows gets >> handled fine with ntp but I can get neither ntp or chrony to sync after >> resume without manually setting the time close to correct first. >> >> Searching has gotten me to the point where I can manually set the time >&...

Hi, all, When working on adding PM support to xen, we realized that some enhancements are required to suspend/resume domU. Following is some background and thoughts, and welcome on comments. :-) Currently we use a simple approach (pause/unpause) for domU when ready to pull whole platform into a power save state, saying a S3. Because pause/unpause is out of domU''s knowledge, domU observes soft locku...