Quoting Len Brown (lenb@xxxxxxxxxx): > Please attach the output from acpidump to > http://bugzilla.kernel.org/show_bug.cgi?id=7880 done also on : http://www.dth.net/kernel/acpidump_output_via_c3_5000 > We'll likely be able to tell from it if that patch > has any real effect on your system, or if you test > result was from some unrelated event. Reverting the patch didn't make a real difference, it only took longer (eg 16 minutes before lockup in stead of 2-3 minutes) > Also, please test with CONFIG_X86_ACPI_CPUFREQ=n > to remove the acpi-cpufreq driver (and thus this patch) > from your kernel. If it still fails, then we know > that this driver (and this patch) are not related > to the failure. Will do. This machine(firewall) is solar powered so i tried to let it consume as less power as possible This is in my startup script at the moment: echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor > Hmmm, okay, the "big hammer" works. Please see > if any of these smaller hammers work: > > pnpacpi=off > acpi=noirq > notsc More testing to do, however, sunday i'm going abroad for a while, all stuff will be in storage. If i cant find in the next few days (packing everything in moving boxes) it might take a while before i can test again. Sorry for that. Danny -- - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
