linux-kernel - Re: [2.6.25-rc1 regression] Suspend to RAM (bisected)

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

Message-ID: <47AFE671.9040200@gmail.com>
Date:	Mon, 11 Feb 2008 04:08:49 -0200
From:	"Carlos R. Mafra" <crmafra@...il.com>
To:	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [2.6.25-rc1 regression] Suspend to RAM (bisected)

Arjan van de Ven wrote:
> On Mon, 11 Feb 2008 03:25:33 -0200
> "Carlos R. Mafra" <crmafra@...il.com> wrote:
> 
>> The problem with suspend to RAM is that right after typing (from
>> inside X) 'echo mem > /sys/power/state' the screen becomes black and
>> the laptop freezes. I have to use SysRq+b to reboot.
>>
>> I tried to revert the above commit (bc71bec) on top of 2.6.25-rc1, but
>> the compilation fails. It turns out that I have to revert also
>> 9a0b8415 and 9b12e18c to be able to compile without errors. 
>>
>> After reverting the 3 commits mentioned above, the resulting
>> 2.6.25-rc1 kernel can suspend to RAM again (and I must say that it is
>> better that 2.6.24, because now it resumes directly into X and I
>> don't need to use Crtl-Alt-F1 and Alt-F7 to go back to X as I used to
>> do before).
>>
>> The laptop is a Core 2 Duo T7250 2.0 GHz, running Mandriva 2008.0 in
>> 64-bit mode, with the following graphics card:
>> VGA compatible controller: Intel Corporation Mobile GM965/GL960
>> Integrated Graphics Controller (rev 0c) (prog-if 00 [VGA])
>>
>> If there is anything else I can do to help please let me know.
> 
> 
> this may be a BIOS bug; I'll let Venki dig into this ... but can you send the output of
> the dmidecode program to the list? If we need to start blacklisting bioses that information
> is going to be needed ;(

I am sending the dmidecode output attached (I erased the UUID).

Thanks for the prompt answer!






View attachment "dmidecode.txt" of type "text/plain" (5302 bytes)