From: Matt Domsch <Matt_Domsch@dell.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Andrew Morton <akpm@osdl.org>,
Alessandro Suardi <alessandro.suardi@oracle.com>,
linux-kernel@vger.kernel.org, linux-acpi@intel.com
Subject: Re: 2.6.2-rc2-bk1 oopses on boot (ACPI patch)
Date: Wed, 28 Jan 2004 07:37:37 -0600 [thread overview]
Message-ID: <20040128073737.A29748@lists.us.dell.com> (raw)
In-Reply-To: <200401272337.55676.dtor_core@ameritech.net>; from dtor_core@ameritech.net on Tue, Jan 27, 2004 at 11:37:55PM -0500
On Tue, Jan 27, 2004 at 11:37:55PM -0500, Dmitry Torokhov wrote:
> > 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.
Please send me your DSDT and output of dmidecode, and ideally what a
proper DSDT should show in this case (I'm not familiar enough with
what all the various ACPI tables should contain), and I'll take it up
with the BIOS programmers for that platform.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2004-01-28 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 2:15 2.6.2-rc2-bk1 oopses on boot (ACPI patch) Alessandro Suardi
2004-01-28 2:42 ` Andrew Morton
2004-01-28 3:10 ` Linus Torvalds
2004-01-28 3:19 ` Alessandro Suardi
2004-01-28 4:37 ` Dmitry Torokhov
2004-01-28 13:37 ` Matt Domsch [this message]
2004-01-28 22:32 ` Alessandro Suardi
2004-01-28 3:06 ` Linus Torvalds
2004-01-28 3:40 ` Alessandro Suardi
2004-01-28 16:14 ` Dominik Brodowski
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020AE8AD@hdsmsx402.hd.intel.com>
2004-01-29 23:31 ` Len Brown
2004-01-30 0:37 ` Alessandro Suardi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040128073737.A29748@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=akpm@osdl.org \
--cc=alessandro.suardi@oracle.com \
--cc=dtor_core@ameritech.net \
--cc=linux-acpi@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox