Re: TSC not updating after resume: Bug or Feature?

[Fabio Comolli]

OK, it seems that you got it.

The system survived two hibernation / resume cycles without triggering
the warning and, probably the most important part, the dmesg does not
have any "jumps" before the "Force enable HPET on resume" line as
before:

[  275.647704] PM: Creating hibernation image:
[  275.648005] PM: Need to copy 177844 pages
[  275.648005] Intel machine check architecture supported.
[  275.648005] Intel machine check reporting enabled on CPU#0.
[  275.648005] Force enabled HPET at resume
[  275.648005] ACPI: Waking up from system sleep state S4
[  275.669038] ACPI: EC: non-query interrupt received, switching to
interrupt mode
[  275.740697] pcieport-driver 0000:00:01.0: setting latency timer to 64
[  275.740781] pcieport-driver 0000:00:1c.0: setting latency timer to 64
[  275.740786] pciehp 0000:00:1c.0:pcie02: pciehp_resume ENTRY

...and so on.

As i mentioned in the bug report, to be sure that the bug doesn't
trigger I have to wait at least on day and > 10 hibernation / resumee
cycles.

But with your first patch the bug triggered at the second cycle, so
I'm optimist :-)

I'll keep you informed. Many thanks in advance,
Fabio




On Mon, Dec 22, 2008 at 11:16 PM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
>
> On Mon, 22 Dec 2008, Fabio Comolli wrote:
>
>> Won't apply:
>>
>> fcomolli@hawking:~/software/GIT-TREES/linux-2.6> patch -p1 --dry-run <
>> /home/fcomolli/0009c-tglx-debug.patch
>> patching file kernel/sched_clock.c
>> patching file kernel/time/timekeeping.c
>> Hunk #1 succeeded at 49 with fuzz 2 (offset 3 lines).
>> Hunk #2 succeeded at 100 with fuzz 2 (offset 5 lines).
>> Hunk #3 FAILED at 309.
>> 1 out of 3 hunks FAILED -- saving rejects to file kernel/time/timekeeping.c.rej
>>
>> Should I revert you previous one?
>
> Oops, yes.
>
> Thanks,
>
>        tglx
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/