linux-kernel - Re: 2.6.29-rc1: thinkpad problems during resume

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: <49711EBC.5050101@sgi.com>
Date:	Fri, 16 Jan 2009 15:56:44 -0800
From:	Mike Travis <travis@....com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Pavel Machek <pavel@...e.cz>,
	Jeff Chua <jeff.chua.linux@...il.com>,
	kernel list <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: 2.6.29-rc1: thinkpad problems during resume

Rafael J. Wysocki wrote:
> On Friday 16 January 2009, Pavel Machek wrote:
>> On Tue 2009-01-13 23:21:17, Jeff Chua wrote:
>>> On Tue, Jan 13, 2009 at 10:36 PM, Pavel Machek <pavel@...e.cz> wrote:
>>>> resumes fine with CONFIG_SMP unset.
>>> On my X60s, I had problem with s2ram, and I switch to the following ...
>>>
>>> echo mem > /sys/power/state
>>>
>>> Try and see if it works for you.
>> I tried that; unlike s2ram, this actually produces some oopses that
>> can be viewed. Unfortunately, they scroll a bit too fast.
>>
>> cpu hotplug vs. cpufreq seems to be responsible in my case, looking at
>> the logs from "echo 1 > online".
> 
> There are three patches from Mike Travis that can help:
> http://lkml.org/lkml/2009/1/16/377
> 
> Thanks,
> Rafael

Note that these don't really fix anything, just replaces the current
method of using set_cpus_allowed with the work_on_cpu call.  If
the laptop worked before the [bad] patch, then it should work again
now with this one.

Thanks,
Mike


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