[lkml]   [2007]   [Jul]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    SubjectRe: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
    Quoting Gabriel C (
    > Now while we think is ACPI this should be easy for you to bisect.
    > This commit;a=commit;h=39804b20f62532fa05c2a8c3e2d1ae551fd0327b
    > merged ACPI so this one should be your first bad one.
    > Maybe Len has some idea and you don't need to bisect :)

    Thanks to personal coaching of Gabriel i bisected the last few days.

    It looked like this was the cullprit:

    22aadf8a07067644e101267ed5003043f2ad05bf is first bad commit

    2.6.23-rc1-git[1-6] all lockup solid after either direct or
    within a couple of minutes (less than 2) after reboot.

    They all run fine with "acpi=off" as boot argument.

    However, i'm currently running 2.6.23-rc1-git6 with this reverted:

    diff --git a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
    index 18c8b67..6f846be 100644 (file)
    --- a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
    +++ b/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
    @@ -665,8 +665,8 @@ static int acpi_cpufreq_cpu_init(struct cpufreq_policy *policy)
    data->max_freq = perf->states[0].core_frequency * 1000;
    /* table init */
    for (i=0; i<perf->state_count; i++) {
    - if (i>0 && perf->states[i].core_frequency ==
    - perf->states[i-1].core_frequency)
    + if (i>0 && perf->states[i].core_frequency >=
    + data->freq_table[valid_states-1].frequency / 1000)

    I could hardly believe this could be the cause.
    And indeed after about 16 minutes the kernel froze again, though longer
    uptime than other kernels :-(

    This hardware is a via epia 5000 with latest bios available (2.07)

    It's remarkable that with acpi=off the machine is rocksolid.
    As is with 2.6.22* kernels _with_ acpi enabled!
    weeks of uptime before i wanted to upgrade to a new kernel ;-)

    I'm thinking of redoing the git disect but this time really powercycle
    the unit between kernels since it "seems/feels" like a timer which
    really counts to 0 and then locks the machine.
    After a lockup/freeze i cant boot the kernel another time with acpi
    enabled: it will simply hang after booting init.
    And again nobody home: no keyboard activity whatsoever.

    I've put the dmesg of 2.6.23-rc1-git6 with and without acpi=off online:

    I would like to hear if someone has an idea how to tackle this problem.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-07-30 04:57    [W:0.037 / U:117.304 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site