linux-kernel - Re: [GIT PATCH] Driver Core patches for 2.6.18

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: <200609271342.57083.rjw@sisk.pl>
Date:	Wed, 27 Sep 2006 13:42:56 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Mike Galbraith <efault@....de>
Cc:	Greg KH <gregkh@...e.de>, Linus Torvalds <torvalds@...l.org>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	Dave Jones <davej@...hat.com>
Subject: Re: [GIT PATCH] Driver Core patches for 2.6.18

On Wednesday, 27 September 2006 15:03, Mike Galbraith wrote:
> On Wed, 2006-09-27 at 10:48 +0000, Mike Galbraith wrote:
> > On Wed, 2006-09-27 at 08:58 +0200, Rafael J. Wysocki wrote:
> > 
> > > Please try to remove the acpi_cpufreq driver before the suspend.
> > 
> > Yeah, that's what's causing the suspend failure.  Thanks.
> 
> Followup:
> 
> Without the P-States driver (CONFIG_X86_ACPI_CPUFREQ) enabled, both
> virgin 2.6.18 and 2.6.18 with this patchset suspend/resume just fine,
> and cpufreq (p4_clockmod) works fine.
> 
> Why CONFIG_X86_ACPI_CPUFREQ blows my box out of the water with the
> patchset applied, I have no idea.

I think DaveJ is looking into it.

> Enabling suspend tracing didn't do 
> anything for me except cause fsck to check my drive, me to reset my
> clock, only to have fsck then check my drive yet again :)

Well, I've never used it. ;-)

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller
-
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/