linux-kernel - Re: Regression 2.6.28-git: suspend/resume failure. git bisected to usb suspend/resume patch

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: <200901131244.49960.rjw@sisk.pl>
Date:	Tue, 13 Jan 2009 12:44:49 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"Jeff Chua" <jeff.chua.linux@...il.com>
Cc:	"Christian Borntraeger" <borntraeger@...ibm.com>,
	"Alan Stern" <stern@...land.harvard.edu>,
	lkml <linux-kernel@...r.kernel.org>,
	"Greg Kroah-Hartman" <gregkh@...e.de>, linux-usb@...r.kernel.org,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Ingo Molnar" <mingo@...e.hu>
Subject: Re: Regression 2.6.28-git: suspend/resume failure. git bisected to usb suspend/resume patch

On Tuesday 13 January 2009, Jeff Chua wrote:
> On Tue, Jan 13, 2009 at 1:25 AM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > Please see if reverting commit 7503bfbae89eba07b46441a5d1594647f6b8ab7d
> > (cpumask: use work_on_cpu in acpi-cpufreq.c for drv_read and drv_write) in
> > addition to a0d4922da2e4ccb0973095d8d29f36f6b1b5f703 helps.
> 
> I can confirm that with these two commits reverted, my X61 can resume from STD.
> 
> > Also, please check if the appended patch fixes the issue with
> > a0d4922da2e4ccb0973095d8d29f36f6b1b5f703 .
> 
> This patch does not apply cleanly to the latest git pull.

I've just sent you a version that should apply to it in another thread.

Thanks,
Rafael
--
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/