On Sunday 29 July 2007 22:54, Danny ter Haar wrote:
quoted text
> Quoting Gabriel C (nix.or.die@googlemail.com):
> > Now while we think is ACPI this should be easy for you to bisect.
> > This commit http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=39804b20f6...
> > 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

Please attach the output from acpidump to 
http://bugzilla.kernel.org/show_bug.cgi?id=7880
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.

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.

quoted text
> 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.

Hmmm, okay, the "big hammer" works.  Please see
if any of these smaller hammers work:

pnpacpi=off
acpi=noirq
notsc

thanks,
-Len
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/