mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Alessandro Suardi <alessandro.suardi@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@intel.com
Subject: Re: 2.6.2-rc2-bk1 oopses on boot (ACPI patch)
Date: Tue, 27 Jan 2004 18:42:28 -0800	[thread overview]
Message-ID: <20040127184228.3a0b8a86.akpm@osdl.org> (raw)
In-Reply-To: <40171B5B.4020601@oracle.com>

Alessandro Suardi <alessandro.suardi@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.

Does this make the oops go away?

diff -puN drivers/cpufreq/cpufreq.c~cpufreq-workaround drivers/cpufreq/cpufreq.c
--- 25/drivers/cpufreq/cpufreq.c~cpufreq-workaround	2004-01-27 18:36:05.000000000 -0800
+++ 25-akpm/drivers/cpufreq/cpufreq.c	2004-01-27 18:36:42.000000000 -0800
@@ -928,6 +928,11 @@ void cpufreq_notify_transition(struct cp
 		return;   /* Only valid if we're in the resume process where
 			   * everyone knows what CPU frequency we are at */
 
+	if (freqs->new == 0) {
+		printk("%s: avoiding div-by-zero\n", __FUNCTION__);
+		return;
+	}
+
 	down_read(&cpufreq_notifier_rwsem);
 	switch (state) {
 	case CPUFREQ_PRECHANGE:

_


  reply	other threads:[~2004-01-28  2:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28  2:15 Alessandro Suardi
2004-01-28  2:42 ` Andrew Morton [this message]
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
     [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=20040127184228.3a0b8a86.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=alessandro.suardi@oracle.com \
    --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

Powered by JetHome