Re: [BUG] 2.6.28 hates my RTC clock - with PM_TRACE set

["Jike Song" <albcamus@gmail.com>]

On Mon, Jan 5, 2009 at 10:33 PM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Mon, Jan 05, 2009 at 10:19:22PM +0800, Jike Song wrote:
>
>> As usually, it suspended to RAM successfully.  But after I press the
>> power button, it won't come back, giving me nothing but a black
>> screen.  So I hold the power button done for about 5 seconds, then the
>> computer halted(it's only a hardware feature of the southbridge,
>> right? ;-), silently, without any output on the always-black screen.
>>
>> So the PM_TRACE code was broken, right?
>
> Why do you say that?
>
>> After rebooting the computer, I found I was in the year 1988!  And I
>> do the suspend-hold_power_button-reboot once again, now it is 2040
>> years A.D.
>
> PM_TRACE uses the clock registers to store information about which
> device the kernel was attempting to resume when it hung. It's expected
> that your clock will be wrong afterwards.
>
Thanks for you information! I took it for granted that the RTC clock
will be restored after resume/reboot.

So it's only an ordinary S2R bug with a black screen?  I can't see
anything with PM_TRACE.

> --
> Matthew Garrett | mjg59@srcf.ucam.org
>

-- 
Thanks,
Jike