linux-kernel - Re: [linux-pm] Re: resume from ram much slower

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0708131620090.2553-100000@iolanthe.rowland.org>
Date:	Mon, 13 Aug 2007 16:21:07 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Pavel Machek <pavel@....cz>
cc:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Linux-pm mailing list <linux-pm@...ts.linux-foundation.org>,
	Arkadiusz Miskiewicz <arekm@...en.pl>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] Re: resume from ram much slower

On Mon, 13 Aug 2007, Pavel Machek wrote:

> Hi!
> 
> > [S-T-R wizards CC'ed]
> > 
> > On 10/08/07, Arkadiusz Miskiewicz <arekm@...en.pl> wrote:
> > > Hi,
> > >
> > > Starting 1-2 weeks ago I have very long resume from
> > > ram times. It takes more than 1 min to resume. Does anyone see such behaviour?
> > >
> > > Kernel from yesterday git, thinkpad z60m, suspend.sf.net tools 20070801
> > >
> > > "ACPI handle has no context!" are interesting btw.
> 
> 
> Usual way to debug it is to unload as many modules as possible, to
> find out if it is caused by one of them...
> 
> If that does not help, you can try playing with git to find out which
> commit caused the regression.

Another possibility: Compare the timestamps in your log with a log from 
an earlier kernel, to find out exactly where the extra delay occurred.

Alan Stern

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/