From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
Andrew Morton <akpm@osdl.org>,
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 23:32:00 +0100 [thread overview]
Message-ID: <40183860.7040503@oracle.com> (raw)
In-Reply-To: <20040128073737.A29748@lists.us.dell.com>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
Matt Domsch wrote:
> 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.
While appreciating your offer, I'd like to remind that this works
perfectly prior to the 20031203 ACPI patch. Indeed, this is what
2.6.1 vanilla says in that area:
cpufreq: CPU0 - ACPI performance management activated.
cpufreq: *P0: 1800 MHz, 0 mW, 250 uS
cpufreq: P1: 1200 MHz, 0 mW, 250 uS
Attaching the gzipped dmesg for my 2.6.1 boot - let me know if
you want anyway dmidecode output and DSDT; for this latter I'll
have to ask for instructions (or is the output of a simple
'cat /proc/acpi/dsdt' enough ?).
--alessandro
"Two rivers run too deep
The seasons change and so do I"
(U2, "Indian Summer Sky")
[-- Attachment #2: dmesg.out.gz --]
[-- Type: application/x-gzip, Size: 4489 bytes --]
next prev parent reply other threads:[~2004-01-28 22: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
2004-01-28 22:32 ` Alessandro Suardi [this message]
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=40183860.7040503@oracle.com \
--to=alessandro.suardi@oracle.com \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--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