On Tuesday 27 January 2004 09:42 pm, Andrew Morton wrote: > Alessandro Suardi <alessandro.suardi _at_ oracle.com> wrote: > > Already reported, but I'll do so once again, since it looks like > > in a short while I won't be able to boot official kernels in my > > current config... > > > > Original report here: > > > > http://www.ussg.iu.edu/hypermail/linux/kernel/0312.3/0442.html > > Divide by zero. Looks like ACPI is now passing bad values into the > frequency change notifier. It is a common problem with Dell's DSDT implementation which does not follow ACPI spec and it's been going on for ages. From the original report: cpufreq: CPU0 - ACPI performance management activated cpufreq: *P0: 1Mhz, 0 mW, 0 uS cpufreq: P1: 0Mhz, 0 mW, 0 uS divide error: 0000 [#1] As you can see all data is bogus... Patching DSDT cures it for sure, sometimes CONFIG_ACPI_RELAXED_AML helps as well. I suppose ACPI P-states driver could check frequencies/latencies and refuse to activate if the are bogus. -- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups: References:
- 2.6.2-rc2-bk1 oopses on boot (ACPI patch)Alessandro Suardi
- Re: 2.6.2-rc2-bk1 oopses on boot (ACPI patch)Andrew Morton
- Prev by Date: Re: RFC: Trailing blanks in source files
- Next by Date: Re: [RFC/PATCH, 2/4] readX_check() performance evaluation
- Previous by thread: Re: 2.6.2-rc2-bk1 oopses on boot (ACPI patch)
- Next by thread: Re: 2.6.2-rc2-bk1 oopses on boot (ACPI patch)
- Indexes:[Main][Thread]