similar to: resume from swap files

Hi, I''d be very interested to hear: does anyone have a stable working amd64 machine (in 64bit mode)? if so, which kernel do you use, and which version of xen / hg tree do you use? linux-2.6-xen.hg compiles fine over here, but reboots during boot. so fast I can''t see anything. (sorry, my laptop has no serial port. so I can''t capture a log file.) 2.6.16-rc4-git8 plus

At boot time, the system is looking for a resume signature on the default SWAP partition that was defined during the OS installation. On several systems, I changed the location of the SWAP partition. How do I change the location where the system looks at boot time for the resume signature? Thanks, -- Patrice Guay patrice.guay at nanotechnologies.qc.ca

Btrfs had some issues with fsync()''ing directories and fsync()''ing after renames. These three new tests cover the 3 different issues we were seeing. This breaks out the dmflakey stuff into a common helper to be shared between generic/311 and generic/320. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- V1->V2: moved this out into its own test instead of

Hello Andreas, On 10/11/05, Andreas Jellinghaus <aj at dungeon.inka.de> wrote: > Peter Koch pointed me to your posting on openssh-devel mailing list. I am very glad that he did. > I'm one of the opensc people, and from my point of view your idea > is a good one. The current openssh-opensc code has a number of issues, > for example the ssh-agent does not test the pin

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/lib/klibc/bin/resume it reduces busybox dependency of Debian initramfs-tools: if [ -e

On Thu, Sep 13, 2018 at 5:37 AM Daniel Drake <drake at endlessm.com> wrote: > > 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]

On Thu, Sep 13, 2018 at 11:37:45AM +0800, Daniel Drake wrote: > 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 >

Commit-ID: a2f9cd4abe2d5cb72e1e89089b132e866e3cea81 Gitweb: http://git.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

Hi, This is based on ext3 0.0.5e and latest LVM snapshot from Sistina CVS. I've been playing with LVM snapshotting in that I'd been getting system hangs and trying to help resolve that issue, but in the process today I stumbled upon an interesting side-effect. This is on my laptop, running 2.2.18 with loads of patches and above LVM and ext3. Basically, forewarning, all of this was done

Hi, After our big ext3 file server crashes, I notice the fsck spends some time replaying the journals (about 5-10 mins for all volumes on the server in question). I guess it must do this should you want to mount the volumes as ext2. My question--is it (theoretically) possible to tell fsck only to replay half-finished and to knock out incomplete transactions from the journals, leaving the kernel

On Wed, Sep 12, 2018 at 8:45 AM Daniel Drake <drake at endlessm.com> wrote: > > 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]

Am 27.09.18 um 22:52 schrieb Bjorn Helgaas: > [+cc LKML] > > On Tue, Sep 18, 2018 at 04:32:44PM -0500, Bjorn Helgaas wrote: >> On Thu, Sep 13, 2018 at 11:37:45AM +0800, Daniel Drake wrote: >>> On 38+ Intel-based Asus products, the nvidia GPU becomes unusable >>> after S3 suspend/resume. The affected products include multiple >>> generations of nvidia GPUs

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,

> -----Oorspronkelijk bericht----- > Van: libvirt-users-bounces@redhat.com [mailto:libvirt-users- > bounces@redhat.com] Namens Jérôme > Verzonden: woensdag 23 september 2015 15:03 > Aan: libvirt-users@redhat.com > Onderwerp: [libvirt-users] Time syncing after VM suspend/resume > > Hi all. > > When resuming guest after suspend, the time is wrong (because the guest

On Thu, Aug 24, 2017 at 12:54:26PM +0000, Naud, AntoineX wrote: >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

Hi, after my X froze i had a fs inconsistency after the journal replay [...] EXT3-fs: 03:06: 1 orphan inode deleted EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 64k freed INIT: version 2.78 booting Loading /etc/console-tools/default.kmap.gz Activating swap... Adding Swap: 264560k

That seems to be the indication given by this webpage http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html However, default install of Redhat 7.2 setsup fs_passno(6th field of /etc/fstab) as 2 which asks you if you want to run fsck after an unclean shutdown The question is, is fsck required after an unclean shutdown or should one just rely on journal replay. What does fsck do when it sees an

This is a note to let you know that I''ve just added the patch titled genirq: Add IRQF_RESUME_EARLY and resume such IRQs earlier to the 3.1-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: genirq-add-irqf_resume_early-and-resume-such-irqs-earlier.patch and it can be found in the

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

If either idling channels or suspending the fence were to fail, the display would never be resumed. Also if a client fails, resume the fence (not functionally important, but it would potentially leak memory). See https://bugs.freedesktop.org/show_bug.cgi?id=70213 Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Untested, but makes sense given that the bug report has cursor setting