public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: 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 04:19:13 +0100	[thread overview]
Message-ID: <40172A31.6060901@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401271907070.10794@home.osdl.org>

Linus Torvalds wrote:
> 
> On Tue, 27 Jan 2004, Andrew Morton wrote:
> 
>>Divide by zero.  Looks like ACPI is now passing bad values into the
>>frequency change notifier.
>>
>>Does this make the oops go away?
> 
> 
> Other values will still cause divide-by-zero (any divisor in 0..9 will do 
> it). Besides, we're dividing with _old_, not new, so that's the one we 
> should likely check.
> 
> 		Linus

Indeed... I get two of the debug printks from the patch, but in the
  end I still oops due to a div-by-zero with EIP in time_cpufreq_notifier.

I'll try and look into Linus' suggestion about printing out stuff from
  adjust_jiffies() in cpufreq.c and will report later.


Thanks,

--alessandro

  "Two rivers run too deep
   The seasons change and so do I"
       (U2, "Indian Summer Sky")


  reply	other threads:[~2004-01-28  3:20 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 [this message]
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=40172A31.6060901@oracle.com \
    --to=alessandro.suardi@oracle.com \
    --cc=akpm@osdl.org \
    --cc=linux-acpi@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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