Re: VIA C3 'Ezra-T' [C5M] - longhaul - do nothing

["Rafał Bilski" <rafalbilski@interia.pl>]

> [...]
> longhaul: Using northbridge support.
Can You uncomment ACPI C3 support and check if it is working too?
Restore these lines to original state below:
    /* Check ACPI support for C3 state */
    if (pr != NULL && longhaul_version == TYPE_POWERSAVER) {
        cx = &pr->power.states[ACPI_STATE_C3];
        if (cx->address > 0 && cx->latency <= 1000)
            longhaul_flags |= USE_ACPI_C3;
    } 

> After changing governor to powersave:
> [...]
> longhaul: Setting to FSB:133MHz Mult:3.0x (399MHz)
> cpufreq-core: notification 1 of frequency transition to 399000 kHz
> cpufreq-core: scaling loops_per_jiffy to 1601526for frequency 399000 kHz
> userspace: saving cpu_cur_freq of cpu 0 to be 399000 kHz
> cpufreq-core: governor: change or update limits
> cpufreq-core: __cpufreq_governor for CPU 0, event 3
> powersave: setting to 399000 kHz because of event 3
> cpufreq-core: target for CPU 0: 399000 kHz, relation 0
> freq-table: request for target 399000 kHz (relation: 0) for cpu 0
> freq-table: target is 0 (399000 kHz, 1)
Yes. It is working. Longhaul ver. 2 wasn't working probably because of the 
same reason. Now I have to think how to deal with this situation. I have 
Nehemiah with RevID = 0. Good. I have Ezra with RevID = 1 and voltage 
scaling. Bad. I have to check if it is working with RevID = 0. Probably 
not because VIA documentation advise to poke RevKey with RevID. But 
I will read it again to refresh my memory.
> Clocksource tsc unstable (delta = -208657423 ns)
> 
> [...]
> 
> The "Clocksource tsc unstable (delta = -208657423 ns)" is something to 
> worry about?
No. It isn't used anyway because of "Marking TSC unstable due to: possible 
TSC halt in C2."

Do You agree to test patch(es) that I will write (probably) tommorow?

Thanks


----------------------------------------------------------------------
Sprawdz co sie dzieje w Twojej okolicy!
Kliknij >>> http://link.interia.pl/f1b7e