From: Len Brown <len.brown@intel.com>
To: Alessandro Suardi <alessandro.suardi@oracle.com>
Cc: Matt Domsch <Matt_Domsch@dell.com>,
Dmitry Torokhov <dtor_core@ameritech.net>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-acpi <linux-acpi@intel.com>
Subject: Re: 2.6.2-rc2-bk1 oopses on boot (ACPI patch)
Date: 29 Jan 2004 18:31:14 -0500 [thread overview]
Message-ID: <1075419074.2497.203.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0020AE8AD@hdsmsx402.hd.intel.com>
Alessandro,
Looks like you've identifed a regression, probably in ACPI.
Please test the 1st patch attached to this bug report
http://bugzilla.kernel.org/show_bug.cgi?id=1766
If it doesn't address the problem, please file an additional bug report
per below.
thanks,
-Len
ps.
The divide-by zero symptom should be addressed by Dominik's update, now
in the ACPI tree and thus the next -mm patch.
pps.
How to file a bug against ACPI:
http://bugzilla.kernel.org/ Category: Power Management, Component: ACPI
Please attach dmesg -s40000 output (or serial console log if dmesg
unavailable)
Please attach the output from acpidmp, available in /usr/sbin/, or in
pmtools:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
On Wed, 2004-01-28 at 17:32, Alessandro Suardi wrote:
> 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.
...
> , 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")
>
>
next parent reply other threads:[~2004-01-29 23:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020AE8AD@hdsmsx402.hd.intel.com>
2004-01-29 23:31 ` Len Brown [this message]
2004-01-30 0:37 ` 2.6.2-rc2-bk1 oopses on boot (ACPI patch) Alessandro Suardi
2004-01-28 2:15 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
2004-01-28 3:06 ` Linus Torvalds
2004-01-28 3:40 ` Alessandro Suardi
2004-01-28 16:14 ` Dominik Brodowski
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=1075419074.2497.203.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=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