linux-kernel - Re: [patch 00/69] -stable review

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-next>] [day] [month] [year] [list]

Date:	Tue, 22 May 2007 15:07:01 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Romano Giannetti <romanol@...omillas.es>
cc:	Chris Wright <chrisw@...s-sol.org>,
	Chuck Ebbert <cebbert@...hat.com>,
	linux-kernel@...r.kernel.org, stable@...nel.org,
	Justin Forbes <jmforbes@...uxtx.org>,
	Zwane Mwaikambo <zwane@....linux.org.uk>,
	"Theodore Ts'o" <tytso@....edu>,
	Randy Dunlap <rdunlap@...otime.net>,
	Dave Jones <davej@...hat.com>,
	Chuck Wolber <chuckw@...ntumlinux.com>,
	Chris Wedgwood <reviews@...cw.f00f.org>,
	Michael Krufky <mkrufky@...uxtv.org>,
	akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk
Subject: Re: [patch 00/69] -stable review



On Tue, 22 May 2007, Romano Giannetti wrote:
> 
> It's an useful patch for me. Without it, my sony vaio pcg-fx701 was very
> erratic in resume (kernel 2.6.21.1; it works well with the .17 ubuntu
> kernel). With this patch, I have done 7 cycles flawlessly. Even the
> out-of-tree rtl8180 wireless driver [1] works ok across resumes. 

Ok, good to hear.

> The only problem is that there is an gaping delay of 60 seconds (more or
> less) on resume. I have the syslog trace copied below; could be a timer
> problem? Is it known? (It is scaring because the laptop seems dead
> during this time. I'm not and expert, but it seems here:

It's not known, no, and yeah, that's scary (and 60 seconds is long enough 
that most people would have grown bored and pushed the power button for 
five seconds, having considered the resume a failure).

> [    1.617972] pcmcia: registering new device pcmcia1.0 
> [   61.612517] PM: Writing back config space on device 0000:00:[...]
> 
> ...and time do not advance.

Do you mean that doing "date" twice does not increase the seconds? If so, 
that's almost certainly related to the gaping delay. Which timer do you 
end up using (what does "dmesg | grep clocksource" say)? Does adding 
"clocksource=acpi_pm" to the kernel command line change things?

Also, what does your lspci look like?

		Linus
-
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/