linux-kernel - [BISECTED] Regression: First hibernation attempt fails

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 10 Apr 2009 15:04:06 +0100
From:	Alan Jenkins <alan-jenkins@...fmail.co.uk>
To:	Jens Axboe <jens.axboe@...cle.com>
CC:	Pavel Machek <pavel@....cz>, linux-pm@...ts.linux-foundation.org,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: [BISECTED] Regression: First hibernation attempt fails

Alan Jenkins wrote:
> Pavel Machek wrote:
>   
>> On Fri 2009-04-10 12:08:13, Alan Jenkins wrote:
>>   
>>     
>>> Pavel Machek wrote:
>>>     
>>>       
>>>> On Thu 2009-04-09 12:13:03, Alan Jenkins wrote:
>>>>   
>>>>       
>>>>         
>>>>> Yet another issue in 2.6.30-rc1 which was not present in 2.6.29 :-).  I
>>>>> wonder if it rings any bells?
>>>>>
>>>>> On my laptop (EEE 4G), the first attempt at hibernation fails. 
>>>>> Subsequent attempts succeed.
>>>>>
>>>>> If I use s2disk as normal, I see "snapshotting system", then before it
>>>>> gets to write out the image, it aborts and switches back to X.   I can't
>>>>> see any error message, even if I check the log with "dmesg".
>>>>>
>>>>> If I use "echo disk > /sys/power/state", echo reports the error "Cannot
>>>>> allocate memory".
>>>>>
>>>>> This only happens if I've logged in to X first.  In fact, I narrowed it
>>>>> down to gnome-power-manager.  If I kill gnome-power-manager beforehand,
>>>>> then it doesn't happen.
>>>>>         
>>>>>           
>>>> Anything interesting in dmesg?      
>>>>         

>>> Nothing obvious. I've attached my latest at
>>> <http://bugzilla.kernel.org/show_bug.cgi?id=13058>.
>>>       

Bisection succeeded:

1faa16d22877f4839bd433547d770c676d1d964c
"block: change the request allocation/congestion logic to be sync/async
based"

If I revert the commit, it fixes my bug.

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