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: <20080915091925.GB1787@elf.ucw.cz>
Date:	Mon, 15 Sep 2008 11:19:25 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	kernel list <linux-kernel@...r.kernel.org>,
	Linux-pm mailing list <linux-pm@...ts.osdl.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: 2.6.27-rc6: nohz + s2ram = need to press keys to get progress

On Sun 2008-09-14 12:15:04, Thomas Gleixner wrote:
> On Sun, 14 Sep 2008, Pavel Machek wrote:
> > On Sun 2008-09-14 10:51:04, Thomas Gleixner wrote:
> > > On Sun, 14 Sep 2008, Pavel Machek wrote:
> > > > > It _does_ happen with mainline 2.6.27-rc6.
> > > > 
> > > > s2ram hs problem in mainline 2.6.26, too. (Different problem: no
> > > > ammount pressing shift helps there.) nohz=off cures it, too.
> > > 
> > > Ok, so it's not a regression.
> > > 
> > > Is the problem in the suspend path or in the resume ?
> > 
> > During resume, on both 2.6.26 and 2.6.27-rc6. (27-rc6 actually resumes
> > if I keep hitting shift, and I get "sleepy" system after that --
> > cursor does not blink, but machine can be used -- as long as I keep
> > hitting keys).
> 
> Hmm. Can you please provide the output of /proc/timer_list when the
> system is in that "sleepy" state.

-rc5 seems to work ok... is there some patch I should try to revert
first?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ