linux-kernel - Re: 2.6.29-rc1 does not boot

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: <496FC713.3040003@sgi.com>
Date:	Thu, 15 Jan 2009 15:30:27 -0800
From:	Mike Travis <travis@....com>
To:	Dieter Ries <clip3@....de>
CC:	Dieter Ries <clip2@....de>,
	Maciej Rutecki <maciej.rutecki@...il.com>,
	Ingo Molnar <mingo@...e.hu>, rusty@...tcorp.com.au,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.29-rc1 does not boot

Dieter Ries wrote:
> Mike Travis schrieb:
>> Dieter Ries wrote:
>>> I just tested it. The kernel does boot up, suspending to ram works
>>> perfectly, hibernating did also work, but I found an inconsistent lock
>>> state in dmesg afterwards. System is still fully functional
>>>
>>> May or may not be related, I don't know.
>> If it doesn't happen before my patch, then it's probably related.
>>
> 
> 
> I just tried it without your patches, and the inconsistent lock state
> message is also there after suspending to ram.
> 
> So they dont seem to be related.
> 
> cu
> Dieter

Thanks for the feedback!

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/